node-modules-analyzer
node-modules-analyzer copied to clipboard
matheus1lva
Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.9.6 to 7.23.2. Release notes Sourced from @babel/traverse's releases. v7.23.2 (2023-10-11) NOTE: This release also re-publishes @babel/core, even if it does not appear in the linked release...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Not hoisted packages can be detected in monorepo sub packages and in nested node_modules. They are usually the result of conflicting versions. Partially can be fixed by yarn-deduplicate tool.
add amount of packages processed and number of packages that don't have problem vs how many have
add cli flag to sort the saved amount of bytes in `asc` or `desc`
It would be good to have a `danger-plugin-node-modules-analyzer` that: 1. runs your CLI 2. identify dependencies with problems 3. report an issue to the original repository (optional behavior) or patches...
add information to wheater or not the package complains with the required version!
https://github.com/entria/entria-deploy/blob/060dd5b14e0d0f38298b7f03c8b43551f350dca0/src/__tests__/shouldDeploy.spec.ts#L67 (will be here FOREVAR until we reach a decent amount of tests for future implementations)