foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-22 07:14:47 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/ext/node_resolver
History
Nathan Whitaker f1ba266613
fix(node): Don't error out if we fail to statically analyze CJS re-export (#25748) 
Fixes rsbuild running in deno.

You can look at the test to see what was failing, the gist is that we
were trying to statically analyze the re-exports of a CJS script, and if
we couldn't find the source for the re-exported file we would fail.

Instead, we should just treat these as if they were too dynamic to
analyze, and let it fail (or succeed) at runtime. This aligns with
node's behavior.
2024-09-19 18:37:36 -07:00
..
analyze.rs fix(node): Don't error out if we fail to statically analyze CJS re-export (#25748) 2024-09-19 18:37:36 -07:00
Cargo.toml chore: forward v1.46.3 release commit to main (#25425) 2024-09-04 17:16:24 +00:00
clippy.toml refactor: decouple node resolution from deno_core (#24724) 2024-07-25 19:08:14 -04:00
env.rs refactor: decouple node resolution from deno_core (#24724) 2024-07-25 19:08:14 -04:00
errors.rs refactor: decouple node resolution from deno_core (#24724) 2024-07-25 19:08:14 -04:00
lib.rs fix(byonm): resolve npm deps of jsr deps (#25399) 2024-09-04 14:00:44 +00:00
npm.rs refactor: decouple node resolution from deno_core (#24724) 2024-07-25 19:08:14 -04:00
package_json.rs refactor: decouple node resolution from deno_core (#24724) 2024-07-25 19:08:14 -04:00
path.rs fix(compile/windows): handle cjs re-export of relative path with parent component (#24795) 2024-07-30 16:46:15 -04:00
README.md refactor: decouple node resolution from deno_core (#24724) 2024-07-25 19:08:14 -04:00
resolution.rs fix(task): correct name for scoped npm package binaries (#25390) 2024-09-03 13:56:39 +00:00
sync.rs feat: upgrade V8 to 12.8 (#24693) 2024-07-31 23:22:34 +00:00

README.md

Node Resolver

crates docs

Provides Node.js compatible resolution for the Deno project.