foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-30 11:16:38 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/cli/npm/mod.rs

24 lines
645 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;
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(lock): Additive lock file (#16500) This commit changes lockfile to be "additive" - ie. integrity check only fails if file/package is already specified in the lockfile, but its integrity doesn't match. If file/package is not present in the lockfile, it will be added to the lockfile and the lockfile will be written to disk.
2022-10-31 19:07:36 -04:00
#[cfg(test)]
pub use registry::NpmPackageVersionDistInfo;
refactor(npm): create general use `NpmPackageResolver` (#15882)
2022-09-13 11:59:01 -04:00
pub use registry::NpmRegistryApi;
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
#[cfg(test)]
pub use registry::TestNpmRegistryApiInner;
fix(npm): improve peer dependency resolution (#17835) This PR fixes peer dependency resolution to only resolve peers based on the current graph traversal path. Previously, it would resolve a peers by looking at a graph node's ancestors, which is not correct because graph nodes are shared by different resolutions. It also stores more information about peer dependency resolution in the lockfile.
2023-02-21 12:03:48 -05:00
pub use resolution::NpmPackageId;
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;
feat: add initial internal npm client and dependency resolver (#15446)
2022-08-10 15:23:58 -04:00
pub use resolution::NpmResolutionPackage;
feat(unstable/npm): initial type checking of npm specifiers (#16332)
2022-10-21 11:20:18 -04:00
pub use resolution::NpmResolutionSnapshot;
refactor(npm): create general use `NpmPackageResolver` (#15882)
2022-09-13 11:59:01 -04:00
pub use resolvers::NpmPackageResolver;
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