javascript modules packages are always named package.tgz

[romain-pm]

Environment and versions used

latest javascript-modules-engine / vite plugin

Steps to reproduce

create a new js module with npm init @jahia/module hydrogen
install with yarn install
build with yarn build
go to dist folder

Current Behavior

package.tgz

Desired Behavior

the package should have the name of the module: hydrogen-0.0.1.tgz

[GauBen]

Is this grave? Having a consistent name makes it easier to reference, especially since JSM versions are not very meaningful

[baptistegrimaud]

That's also the default name used by yarn pack so it can be considered as standard within the Yarn ecosystem.

[romain-pm]

I thought that on npmjs or nexus, the artifacts have a meaningful name, isn't it the case? If yes, why is it not the same when we build locally?

When working on 2 different modules, it feels a bit weird to upload 2 files names "package.tgz" while they have different content inside. At the end, the content isn't conflicting but as a user it's a bit disturbing.

What am I missing?

[Fgerthoffert]

This was closed by mistake, reopening