make it easier to maintain package.json
See original GitHub issueDescription
atm there is no way to check if a package is used in the mono repo or not. the node_module and its install get longer and longer and no way to confirm if a package is used in one of the hundred lib and app other than checking them manually.
depcheck
lib doesn’t support nx, so there should be a contribution from nx to that repo or nx independant lib.
Motivation
to clean the package.json and decrease install time
Suggested Implementation
contribute to depcheck lib or come up with a built in solution
Alternate Implementations
there is none that I am aware of
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Guide to managing npm packages in your package.json
It might be a relatively easy way to keep some core packages more up-to-date with smaller risk of running into breaking changes unexpectedly....
Read more >package.json - npm Docs
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >Best practices for creating a modern npm package - Snyk
Run npm init -y to create a package.json file. Note: If you cloned the example repository, you won't need to do this step....
Read more >Keeping your dependencies in order when using NPM.
Today we will cover how to maintain a proper package.json file and ... Following this tips will make the work easier not only...
Read more >How to keep node_modules in sync with package.json
We can make use git hooks to trigger npm install command if a package.json file has been modified. Script to run inside git...
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 Free
Top 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
You can do it with by using the project graph, though, as @FrozenPandaz mentioned above, we can’t know for sure but that will be something in the right direction, at least to have a list of packages to manually test.
Here is an example of how it could look like:
That would be a Typescript script in your
/tools
directory that you can execute with:still it’s a valid requirement for publishable lib. we have to manually maintain the contain of package and it’s list
On Wed, Mar 23, 2022 at 8:21 AM github-actions[bot] < @.***> wrote: