mirror of
https://github.com/denoland/deno.git
synced 2025-09-25 03:42:30 +00:00
c064b6d594
Some checks are pending
ci / test debug windows-x86_64 (push) Blocked by required conditions
ci / build libs (push) Blocked by required conditions
ci / pre-build (push) Waiting to run
ci / test debug linux-aarch64 (push) Blocked by required conditions
ci / test release linux-aarch64 (push) Blocked by required conditions
ci / publish canary (push) Blocked by required conditions
ci / test debug macos-aarch64 (push) Blocked by required conditions
ci / test release macos-aarch64 (push) Blocked by required conditions
ci / bench release linux-x86_64 (push) Blocked by required conditions
ci / lint debug linux-x86_64 (push) Blocked by required conditions
ci / lint debug macos-x86_64 (push) Blocked by required conditions
ci / lint debug windows-x86_64 (push) Blocked by required conditions
ci / test debug linux-x86_64 (push) Blocked by required conditions
ci / test release linux-x86_64 (push) Blocked by required conditions
ci / test debug macos-x86_64 (push) Blocked by required conditions
ci / test release macos-x86_64 (push) Blocked by required conditions
ci / test release windows-x86_64 (push) Blocked by required conditions
This further improves `import.meta.resolve` to not error in many more scenarios (better alignment with Node). 1. Non-existent files in npm packages 1. Non-existent built-in node modules (ex. `node:non-existent`) 1. Many things that were previously errors with byonm. 1. No longer surfaces some deno_graph resolution errors Additionally, this defers resolving npm specifiers until loading for dynamic imports in order to have `prepare_load` properly install them loading. Before it could potentially error when loading the same npm specifier on multiple workers (reason for flaky `specs::npm::worker_shutdown_during_npm_import`). |
||
|---|---|---|
| .. | ||
| managed | ||
| byonm.rs | ||
| local.rs | ||
| mod.rs | ||