[Feature]: Provide a package-lock.json file in release

[arunoruto]

Problem Description

I wanted to package context7 into nixpkgs using buildNpmPackage. As the name suggests, the package is being built using npm and it needs the lock file to do so, which isn't provided here (only the bun.lock file is in the repo).

Nix and nixpkgs is all about reproducibility, so a lock file is needed before the building is started, so everyone can have the same version. If it would be fetched ad-hoc, we can't guarantee reproducibility anymore.

Proposed Solution

While having a package-lock.json file in the repo isn't probably needed, providing it in the final release file would be beneficial to packaging into nix! I was wondering if it would be possible to put the file in the final zip file too.

Alternatives Considered

Currenlty I am checking out the repo, manually resetting it to the commit corresponding to the tag I am building and running npm install in the folder to create the package-lock.json file.

Priority

Nice to have

Additional Context

No response

[enesgules]

We are migrating to pnpm at #1058 and will have a new lock file afterwards, would that solve your issue?