-
Notifications
You must be signed in to change notification settings - Fork 3k
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] npm pack
incorrect filename for scoped package
#3405
Comments
Perhaps it is just a matter of adding the string replacement, Line 105 in 3f202cd
Instead of at individual sites like here. Lines 83 to 86 in 3f202cd
|
Verifying this is still an issue on $ ls
$ npm pack "@wordpress/data-controls"
npm notice
npm notice 📦 @wordpress/data-controls@2.2.6
...
npm notice filename: @wordpress/data-controls-2.2.6.tgz
...
wordpress-data-controls-2.2.6.tgz
$ ls
wordpress-data-controls-2.2.6.tgz |
A workaround is to use an older npm version, such as v6.14.15. |
Just encountered this same issue in some workflows. |
Is there any update on this? |
Is there an existing issue for this?
Current Behavior
npm pack
andnpm pack --json
show the incorrect filename when packing a package with a scoped name.Notice
npm notice filename: @my-scope/my-package-1.0.0.tgz
is not the correct filename.Expected Behavior
The correct filename to be displayed, in the above example
my-scope-my-package-1.0.0.tgz
.Steps To Reproduce
@my-scope/my-package
npm pack
ornpm pack --json
Environment
The text was updated successfully, but these errors were encountered: