-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
enhancementNew feature or requestNew feature or request
Description
- I'd be willing to implement this feature (contributing guide)
- This feature is important to have in this repository; a contrib plugin wouldn't do
Describe the user story
Currently when publishing a package by using yarn npm publish is very unclear which version got published.
This is basically the output of a yarn npm publish:
➤ YN0000: package.json
➤ YN0000: readme/roadmap.md
➤ YN0000: Package archive published
➤ YN0000: Done in 1s 832ms
Describe the solution you'd like
This is how the same file contents looked with only npm publish:
npm notice 3.6kB package.json
npm notice 5.3kB readme/roadmap.md
npm notice === Tarball Details ===
npm notice name: @scope/package-name
npm notice version: 1.33.0-beta2376675.0
npm notice filename: @scope/package-name-1.33.0-beta2376675.0.tgz
npm notice package size: 92.3 kB
npm notice unpacked size: 435.5 kB
npm notice shasum: 108cb5fd34eb83096aea56d36f6cf4ba1208a134
npm notice integrity: sha512-sdMJO9hsu7Z+J[...]XGwdWPzXgrZ8g==
npm notice total files: 227
npm notice
npm notice Publishing to https://artifactory.domain/artifactory/api/npm/scope/
+ @scope/[email protected]
Describe the drawbacks of your solution
It may be slower to gather the archive or package details. But nothing else
Describe alternatives you've considered
Why not making it a plugin?
- This info is already in the publish command. Forcing consumers to install a plugin for such a trivial but vital info is kinda ugly
7rulnik and rsoberano-ld
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request