FEATURE(arborist) log warning when saving lockfile lacking resolved/integrity for non-bundled dependencies
Open
Nobody has claimed this yet.
Enhancement
ws:arborist
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
From https://github.com/npm/arborist/pull/270
Reproduction case:
# reify to build package tree in node_modules
arborist reify
# remove all metadata about resolved/integrity
rm package-lock.json node_modules/.package-lock.json
# reify again to create a lockfile without full metadata
arborist reify # <-- this should warn
Contributor guide
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 the arborist reify command and run the reproduction steps: remove package-lock.json and node_modules/.package-lock.json, then reify again. Trace the lockfile-saving path and make the specified case emit a warning for non-bundled dependencies lacking resolved or integrity metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100