foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-25 15:29:32 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/cli/npm/mod.rs

20 lines
523 B
Rust
Raw Normal View History

chore: update copyright year to 2023 (#17247) Yearly tradition of creating extra noise in git.
2023-01-02 16:00:42 -05:00
// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license.
feat: add initial internal npm client and dependency resolver (#15446)
2022-08-10 15:23:58 -04:00
mod cache;
fix(npm): lazily install package.json dependencies only when necessary (#17931) This lazily does an "npm install" when any package name matches what's found in the package.json or when running a script from package.json with deno task. Part of #17916 Closes #17928
2023-02-24 19:35:43 -05:00
mod installer;
feat: add initial internal npm client and dependency resolver (#15446)
2022-08-10 15:23:58 -04:00
mod registry;
mod resolution;
refactor(npm): create general use `NpmPackageResolver` (#15882)
2022-09-13 11:59:01 -04:00
mod resolvers;
feat: add initial internal npm client and dependency resolver (#15446)
2022-08-10 15:23:58 -04:00
mod tarball;
refactor: use deno_graph for npm specifiers (#17858) This changes npm specifiers to be handled by deno_graph and resolved to an npm package name and version when the specifier is encountered. It also slightly changes how npm specifier resolution occurs—previously it would collect all the npm specifiers and resolve them all at once, but now it resolves them on the fly as they are encountered in the module graph. https://github.com/denoland/deno_graph/pull/232 --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
2023-02-22 14:15:25 -05:00
pub use cache::should_sync_download;
refactor(npm): create general use `NpmPackageResolver` (#15882)
2022-09-13 11:59:01 -04:00
pub use cache::NpmCache;
refactor(compile): store the npm snapshot in the eszip (#19343)
2023-06-08 11:48:29 -04:00
pub use cache::NpmCacheDir;
fix(npm): lazily install package.json dependencies only when necessary (#17931) This lazily does an "npm install" when any package name matches what's found in the package.json or when running a script from package.json with deno task. Part of #17916 Closes #17928
2023-02-24 19:35:43 -05:00
pub use installer::PackageJsonDepsInstaller;
fix(npm): cache bust npm specifiers more aggressively (#18636) Part 1: #18622 Part 2: This PR Closes #16901 --------- Co-authored-by: Luca Casonato <hello@lcas.dev>
2023-04-12 08:36:11 -04:00
pub use registry::CliNpmRegistryApi;
refactor: use deno_graph for npm specifiers (#17858) This changes npm specifiers to be handled by deno_graph and resolved to an npm package name and version when the specifier is encountered. It also slightly changes how npm specifier resolution occurs—previously it would collect all the npm specifiers and resolve them all at once, but now it resolves them on the fly as they are encountered in the module graph. https://github.com/denoland/deno_graph/pull/232 --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
2023-02-22 14:15:25 -05:00
pub use resolution::NpmResolution;
refactor(npm): push npm struct creation to a higher level (#18139) This has been bothering me for a while and it became more painful while working on #18136 because injecting the shared progress bar became very verbose. Basically we should move the creation of all these npm structs up to a higher level. This is a stepping stone for a future refactor where we can improve how we create all our structs.
2023-03-12 23:32:59 -04:00
pub use resolvers::create_npm_fs_resolver;
refactor(node): move most of cli/node to ext/node (#18797) This is just a straight refactor and I didn't do any cleanup in ext/node. After this PR we can start to clean it up and make things private that don't need to be public anymore.
2023-04-21 21:02:46 -04:00
pub use resolvers::CliNpmResolver;
feat(vendor): support for npm specifiers (#19186) We never properly added support for this. This fixes vendoring when it has npm or node specifiers. Vendoring occurs by adding a `"nodeModulesDir": true` property to deno.json then it uses a local node_modules directory. This can be opted out by setting `"nodeModulesDir": false` or running with `--node-modules-dir=false`. Closes #18090 Closes #17210 Closes #17619 Closes #16778
2023-05-19 18:39:27 -04:00
pub use resolvers::NpmPackageFsResolver;
feat: auto-discover package.json for npm dependencies (#17272) This commits adds auto-discovery of "package.json" file when running "deno run" and "deno task" subcommands. In case of "deno run" the "package.json" is being looked up starting from the directory of the script that is being run, stopping early if "deno.json(c)" file is found (ie. FS tree won't be traversed "up" from "deno.json"). When "package.json" is discovered the "--node-modules-dir" flag is implied, leading to creation of local "node_modules/" directory - we did that, because most tools relying on "package.json" will expect "node_modules/" directory to be present (eg. Vite). Additionally "dependencies" and "devDependencies" specified in the "package.json" are downloaded on startup. This is a stepping stone to supporting bare specifier imports, but the actual integration will be done in a follow up commit. --------- Co-authored-by: David Sherret <dsherret@gmail.com>
2023-02-20 13:14:06 -05:00
pub use resolvers::NpmProcessState;
Copy permalink