Closed
Conversation
Contributor
|
6.8.0 was published 8 days ago, as such we can land this in 6 days on Wed the 27th |
Contributor
|
So today is the 27th, but I'm seeing https://npm.community/t/npm-pack-leaving-out-files-6-8-0-only/5382 is this something to be concerned about? |
Contributor
|
ping @zkat |
Contributor
Contributor
|
Closing in lieu of #26244 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesWhere this should land
Notable Changes
The npm@6.8.0 release includes an implementation of RFC #10, documenting an optional field that can be used to specify the directory path for a package within a monorepo.
3663cdef2#140 Update package.json docs to include repository.directory details. (@greysteil)25573e9b9npm.community#4770 Show installed but unmet peer deps. (@larsgw)Changelog