CommandCodeAI / CommandCodeAI/command-code
Feature Production Lockfile on NPM
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Feature Description
I just packaged command code for nixpkgs : NixOS/nixpkgs#548781
However, there is only a package.json without any full production lockfile package.lock in the NPM registry : https://www.npmjs.com/package/command-code?activeTab=code
It is needed to ensure reproducible builds, and without the full production lockfile (matching the published package.json, containing only dependencies available from the npm registry), it is needed to replicate it using immediate pinning, which might differ from the one you tested the software with
Would it be possible to include the full production lockfile as well on NPM?
Thanks!
Use Case
Reproducible Packaging
Additional Context
Would be fixed by #618
How important is this to you?
Important for my workflow
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json and issue #618, then inspect how the NPM package is published. Verify the production lockfile is generated from the published package.json and included in the NPM registry package; done means downstream packagers can use it for reproducible builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100