node-gradle / node-gradle/gradle-node-plugin
Improve inputs/outputs on NpmInstall tasks
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 677
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
From the npm docs:
https://docs.npmjs.com/cli/v7/commands/npm-install#description
This command installs a package and any packages that it depends on. If the package has a package-lock, or an npm shrinkwrap file, or a yarn lock file, the installation of dependencies will be driven by that, respecting the following order of precedence:
npm-shrinkwrap.json
package-lock.json
yarn.lock
In practice, this means that when running npm install and, for example, a package-lock.json is present, that package lock file will serve as an input and not as an output.
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 the NpmInstall task handling and compare its declared inputs and outputs with the npm documentation linked in the issue. Check the precedence of npm-shrinkwrap.json, package-lock.json, and yarn.lock. Done means an existing lock file is treated as an input rather than an output when running npm install.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100