Require Resolved field, and Check package versions
See original GitHub issueI’ve run into timeout issues with npm because my packages don’t have 'resolved'
fields in the package-lock file. This seems simple enough to add: https://github.com/lirantal/lockfile-lint/blob/9b0b16715e4cfb77c7ec6ec180d9c1f1c8bcb8e6/packages/lockfile-lint-api/src/validators/ValidatePackageNames.js#L21-L23
I am also curious about ensuring versions; squelched here: https://github.com/lirantal/lockfile-lint/blob/9b0b16715e4cfb77c7ec6ec180d9c1f1c8bcb8e6/packages/lockfile-lint-api/src/validators/ValidatePackageNames.js#L46
Wondering if you are accepting PR’s for this, and if you have any insight/preferences for how this is accomplished.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Is there a way to check the version of a node module after ...
You can use require.resolve , to get the directory of your module. Then simply join the path from this with package.json , from...
Read more >Selective dependency resolutions - Yarn
Yarn supports selective version resolutions, which lets you define custom package versions or ranges inside your dependencies through the resolutions field ...
Read more >Add an option to get rid of resolved field in package-lock.json
I'm opening this issue because: npm is crashing. npm is producing an incorrect install. npm is doing something I don't understand.
Read more >resolve-package - npm
resolve -package NPM version NPM downloads npm total downloads. Resolves a given package if it is installed locally, then tries to resolve it ......
Read more >Dependency Resolution - The Cargo Book
One of Cargo's primary tasks is to determine the versions of dependencies to use based on the version requirements specified in each package....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@lirantal Yes I can split this into separate issues and start on the
resolved
fields issue. Stay tuned! 😄Just to follow up, I cannot seem to reproduce the ‘resolved’ fields missing anymore, even on the npm version I mentioned before. I’ve seen this happen in 3 different (work) projects, and even to myself (personal project), but just tried a few times now and can’t figure out what situation causes it.