Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/v7.18.0 #3434

Merged
merged 20 commits into from
Jun 17, 2021
Merged

Release/v7.18.0 #3434

merged 20 commits into from
Jun 17, 2021

Conversation

lukekarrys
Copy link
Contributor

v7.18.0 (2021-06-17)

FEATURES

BUG FIXES

DEPENDENCIES

  • 6b951c042 libnpmversion@1.2.1:
    • fix(retrieve-tag): pass match in a way git accepts
  • de820a021 npm-package-arg@8.1.5:
    • fix: Make file: URLs (mostly) RFC 8909 compliant
  • 16a95c647 @npmcli/arborist@2.6.3:
    • fix(inventory) handle old and british forms of 'license'
    • fix: removes [_complete] check to apply correct metadata
    • ensure node.fsParent is not set to node itself
    • fix extraneous deps on load-actual
  • d341bd86c make-fetch-happen@9.0.3:
    • fix: implement cache modes correctly
  • c90612cf5 libnpmexec@2.0.0:
    • use new npxCache option

ruyadorno and others added 18 commits June 11, 2021 09:14
`npm link <pkg>` is meant to be used as a way to link a local package to
an install tree and it's very surprising to users that it may prune
extraneous deps from the project.

This change switches the default behavior to avoid pruning deps when
reifying the dependencies in npm link.

Fixes: #2554

PR-URL: #3399
Credit: @ruyadorno
Close: #3399
Reviewed-by: @ljharb, @nlf
- Setup ./packages/* as workspaces
- Moved source from: https://github.com/npm/libnpmdiff to
./packages/libnpmdiff
- Added CI target for workspaces

Relates to: npm/statusboard#362

PR-URL: #3386
Credit: @ruyadorno
Close: #3386
Reviewed-by: @wraithgar
No more requiring npm as a singleton.  This will now allow us to move
forward with the other refactoring we need to always use the npm object
itself in tests, not a mocked one.

PR-URL: #3388
Credit: @wraithgar
Close: #3388
Reviewed-by: @ruyadorno
Also includes a preliminary refactor to consolidate workspace logic now
that every command that supports workspaces has it implemented.

PR-URL: #3417
Credit: @wraithgar
Close: #3417
Reviewed-by: @ruyadorno
  * fix(retrieve-tag): pass match in a way git accepts
This enables using the virtual tree instead of node_modules.

PR-URL: #3408
Credit: @G-Rath
Close: #3408
Reviewed-by: @isaacs
  * fix: Make file: URLs (mostly) RFC 8909 compliant
npm-package-arg is doing things more properly now so the tests should
reflect that

PR-URL: #3426
Credit: @wraithgar
Close: #3426
Reviewed-by: @ruyadorno
  * fix(inventory) handle old and british forms of 'license'
  * fix: removes [_complete] check to apply correct metadata
  * ensure node.fsParent is not set to node itself
  * fix extraneous deps on load-actual
The behavior for installing global versions if found has never been part
of npm@7.

PR-URL: #3418
Credit: @wraithgar
Close: #3418
Reviewed-by: @lukekarrys
  * fix: implement cache modes correctly
`npm ls --prod` is currently not omitting devDependencies for configured
workspaces, this changes it by properly checking for the tweaked
`currentDepth` value instead of root check that was in place.

Fixes: #3382

PR-URL: #3429
Credit: @ruyadorno
Close: #3429
Reviewed-by: @wraithgar
This adds a new `npxCache` flatOption for libnpmexec to look for to put
its `_npx` content.  libnpmexec will have to be patched to use that
value, and continue to pass `flatOptions.cache` to pacote et al.

The `flatOptions.cache` is the one that is intended to be passed down
into other modules, as it has the `_cacache` suffix attached.  What was
happening before was that `npx` was creating a new alternate cache one
directory up from where everything else was, and also putting the `_npx`
content there.  It is possible this is the source of at least some of
our "npx doesn't find the right versions" bugs.

PR-URL: #3430
Credit: @wraithgar
Close: #3430
Reviewed-by: @ruyadorno
  * use new npxCache option
This will allow users to specify a folder in which to save their
tarballs.

PR-URL: #3420
Credit: @wraithgar
Close: #3420
Reviewed-by: @ruyadorno
@lukekarrys lukekarrys requested a review from a team as a code owner June 17, 2021 17:43
@lukekarrys lukekarrys merged commit 699c2d7 into latest Jun 17, 2021
@nlf nlf deleted the release/v7.18.0 branch March 28, 2022 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants