-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[BUG] Files directive breaks the "files" directive #5918
Labels
Bug
thing that needs fixing
Priority 0
will get attention right away
regression:9.x
Release 9.x
work is associated with a specific npm 9 release
Comments
MarshallOfSound
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
labels
Dec 5, 2022
Looks like this was broken in npm/npm-packlist#88 maybe unintentionally? Shout-out @JasonEtco for diving into npm internals to find that PR with me cc @nlf |
lukekarrys
added
regression:9.x
Priority 0
will get attention right away
and removed
Needs Triage
needs review for next steps
labels
Dec 7, 2022
Thanks for the report @MarshallOfSound (and the help @JasonEtco). Just dropping one note here while triaging, that both of the following work the same across npm 8 and 9: |
lukekarrys
added a commit
to npm/npm-packlist
that referenced
this issue
Dec 7, 2022
This makes `directory/*` work the same as `directory/**` to maintain backwards compatibility with previous versions of `npm pack`. Ref: npm/cli#5918
hanazuki
added a commit
to hanazuki/node-jsonnet
that referenced
this issue
Feb 25, 2023
npm/cli#5918 suggets that glob was not necessary here.
hanazuki
added a commit
to hanazuki/node-jsonnet
that referenced
this issue
Feb 25, 2023
npm@9 has an incompatibility around glob in files directive. npm/cli#5918 suggets that glob was not necessary here.
hanazuki
added a commit
to hanazuki/node-jsonnet
that referenced
this issue
Feb 25, 2023
npm@9 has an incompatibility around glob in files directive. npm/cli#5918 suggets that glob was not necessary here.
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Priority 0
will get attention right away
regression:9.x
Release 9.x
work is associated with a specific npm 9 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
An entry in the
files
array in yourpackage.json
in the formatfoo/*
does not include deeper files in nested directoriesExpected Behavior
An entry in the
files
array in yourpackage.json
in the formatfoo/*
includes all files inside thefoo
folder and its childrenSteps To Reproduce
git clone https://github.com/MarshallOfSound/npm-files-bug.git cd npm-files-bug npx npm@8 pack npx npm@9 pack
npm 8 output
npm 9 output
Environment
The text was updated successfully, but these errors were encountered: