Option to store tarballs using "npm pack" naming convention

[Chardrazle]

We've recently switched to Verdaccio to have a local npmjs server - it's working great; thanks for the good work.

As part of our build system, we interrogate package tarballs (for licence information).
Previously, these would be acquired using npm pack, which appears to have the filename convention:
[scope-]<package-name>-<version>.tgz
However, looking in the Verdaccio storage location, the tarballs do not have the scope prefix.

It would be useful if there was an option to follow the format of npm pack.

Example:
npm pack @emnapi/runtime@latest
-> emnapi-runtime-1.7.1.tgz

Verdaccio storage location: @emnapi/runtime/runtime-1.7.1.tgz

[mbtools]

It's an interesting use case, but quite rare that users are accessing Verdaccio storage directly (for security reasons, such access must be restricted). I don't think it's worth changing how we store files just for this special case.

However, there's a relatively easy plugin solution: Clone the @verdaccio/local-storage plugin package and adjust the tarball name to your liking.

[Chardrazle]

Yeah, it was only because we were already acquiring the tarballs for the process and then I noticed that Verdaccio was also storing - so thought about removing duplication.
Having taken a closer look, it seems that npm pack is the one that decorates with the scope - probably to avoid clashes when acquiring.
Using npm view ... seems to show that Verdaccio is aligned with that.

For example:

$ npm view @emnapi/runtime dist.tarball
https://registry.npmjs.org/@emnapi/runtime/-/runtime-1.7.1.tgz

I'll probably revisit our process. Thanks for the follow up.