Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-01-02 | chore: update copyright year to 2023 (#17247) | David Sherret | |
Yearly tradition of creating extra noise in git. | |||
2022-12-13 | fix(npm): support loose node semver ranges like `>= ^x.x.x` (#17037) | David Sherret | |
2022-11-15 | fix(npm): support dist tags specified in npm package dependencies (#16652) | David Sherret | |
Closes #16321 | |||
2022-11-08 | feat(unstable/npm): support peer dependencies (#16561) | David Sherret | |
This adds support for peer dependencies in npm packages. 1. If not found higher in the tree (ancestor and ancestor siblings), peer dependencies are resolved like a dependency similar to npm 7. 2. Optional peer dependencies are only resolved if found higher in the tree. 3. This creates "copy packages" or duplicates of a package when a package has different resolution due to peer dependency resolution—see https://pnpm.io/how-peers-are-resolved. Unlike pnpm though, duplicates of packages will have `_1`, `_2`, etc. added to the end of the package version in the directory in order to minimize the chance of hitting the max file path limit on Windows. This is done for both the local "node_modules" directory and also the global npm cache. The files are hard linked in this case to reduce hard drive space. This is a first pass and the code is definitely more inefficient than it could be. Closes #15823 | |||
2022-10-17 | feat(unstable/npm): support providing npm dist-tag in npm package specifier ↵ | David Sherret | |
(#16293) | |||
2022-09-28 | feat(npm): functionality to support child_process.fork (#15891) | David Sherret | |
2022-09-02 | fix(npm): respect `latest` dist tag for getting current version (#15746) | David Sherret | |
2022-09-02 | fix(npm): correct exact matching of pre-release versions (#15745) | David Sherret | |
2022-09-01 | fix(npm): better node version and version requirement compatibility (#15714) | David Sherret | |