Deno Import Resolution: URL vs. Relative Paths

URL-Based vs. Relative Import Resolution in Deno

0 reputation · 09 Dec 2021, 23:17 UTC

21.9K views0

Deno Module Resolution Trade-off

The goal is to ensure consistent module loading behavior across a project utilizing both remote and local dependencies.

Constraint Uncertainty

The exact behavior when mixing URL-based imports with relative path imports within the same module set remains subject to version nuances.

Does Deno prioritize URL resolution precedence over local relative path resolution?
What is the documented behavior for resolving a relative path when a corresponding URL import exists?

888 following

Keep exploring this topic

Should path restrictions use --allow-read= prefix or runtime permission queries for file access?

Deno's file system permission model offers two distinct approaches for restricting read access: command-line flags like --allow-read=/path or runtime permission queries via Deno.permissions.query(). The constraint involves balancing security posture with application flexibility.

Deno Runtime and V8 FinalizationRegistry: External Resource Cleanup Timing

An exploration of the timing and determinism of FinalizationRegistry when cleaning up external native resources within the Deno runtime and V8 engine.

Granular flags vs prompt mode for Deno permissions with untrusted imports

Trade-off between startup granular permission flags and Deno’s prompt-based permission mode for a script that imports third-party modules, with process-wide grants as the key constraint.

Global certificate bypass flag versus per-request trust policy in Deno

Explore Deno's global certificate bypass flag and the missing per-request trust configuration for HTTPS calls.

URL-Based vs. Relative Import Resolution in Deno

Deno Module Resolution Trade-off

Constraint Uncertainty

0 answers

Your perspective belongs here.

0 question comments