David Sherret be97170a19 feat(unstable): ability to npm install then deno run main.ts (#20967) ... This PR adds a new unstable "bring your own node_modules" (BYONM) functionality currently behind a `--unstable-byonm` flag (`"unstable": ["byonm"]` in a deno.json). This enables users to run a separate install command (ex. `npm install`, `pnpm install`) then run `deno run main.ts` and Deno will respect the layout of the node_modules directory as setup by the separate install command. It also works with npm/yarn/pnpm workspaces. For this PR, the behaviour is opted into by specifying `--unstable-byonm`/`"unstable": ["byonm"]`, but in the future we may make this the default behaviour as outlined in https://github.com/denoland/deno/issues/18967#issuecomment-1761248941 This is an extremely rough initial implementation. Errors are terrible in this and the LSP requires frequent restarts. Improvements will be done in follow up PRs.		2023-10-25 14:39:00 -04:00
..
resolvers	feat(unstable): ability to npm install then deno run main.ts (#20967)	2023-10-25 14:39:00 -04:00
cache.rs	refactor(npm): make NpmCache, CliNpmRegistryApi, and NpmResolution internal to npm::managed (#20764)	2023-10-02 17:53:55 -04:00
installer.rs	refactor(npm): make NpmCache, CliNpmRegistryApi, and NpmResolution internal to npm::managed (#20764)	2023-10-02 17:53:55 -04:00
mod.rs	feat(unstable): ability to npm install then deno run main.ts (#20967)	2023-10-25 14:39:00 -04:00
registry.rs	refactor(npm): make NpmCache, CliNpmRegistryApi, and NpmResolution internal to npm::managed (#20764)	2023-10-02 17:53:55 -04:00
resolution.rs	refactor(npm): make NpmCache, CliNpmRegistryApi, and NpmResolution internal to npm::managed (#20764)	2023-10-02 17:53:55 -04:00
tarball.rs	feat(unstable): ability to npm install then deno run main.ts (#20967)	2023-10-25 14:39:00 -04:00