feat: debloat package-lock.json #36
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Does this PR close an existing issue?
It solves the issue 35.
Summary
Thanks for developing this good project, which provides high-coverage tests.
I'm doing dynamic analysis on npm packages, and your project is one of my samples.
Through our dynamic analysis by running the test suites, we find that 25% of the indirect runtime dependencies are installed, however, they are not used during the test runtime. We removed this dependency from package-lock.json, and installed the remaining dependencies using the new package-lock.json, the tests all passed.
Would you consider creating a slim version of the package-lock.json, which can help reduce the corresponding maintenance costs and security risks in production?
Issue Number(s)