-
Notifications
You must be signed in to change notification settings - Fork 4k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 2secondary priority issuesecondary priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release
Description
Current Behavior:
If you try to run npm pack --dry-run on a package that has no name property in its package.json file, the output shows undefined@undefined for the package name and undefined-undefined.tgz for the filename.
Expected Behavior:
I think there should be a guard for when the name property, and even version and description properties are not set whenever running npm pack.
Steps To Reproduce:
steps to reproduce the behavior:
- Create an empty folder
- Change directory into the created folder
- Run
npm pack --dry-run - See that the notice says
undefined@undefinedwithout warnings
Environment:
- OS:
Linux archlinux 5.11.15-arch1-2 #1 SMP PREEMPT Sat, 17 Apr 2021 00:22:30 +0000 x86_64 GNU/Linux - Node: 15.14.0
- npm: 7.7.6
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 2secondary priority issuesecondary priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release