search

matheus1lva / node-modules-analyzer

Apache License 2.0
22 stars 1 forks source link

Danger plugin #4

Open renanmav opened 4 years ago

renanmav commented 4 years ago

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 the package (using patch-package) to remove the unnecessary files

Something similar to this, but for bundle size.

I can help with the implementation.

matheus1lva commented 4 years ago

Nice! That is in the actual roadmap!

Let me fix the codebase, since it has been gone through the MVP phase already and we can start working on it!

matheus1lva commented 4 years ago

There is also some improvements and bugs I found that have to be fixed ~believe me or not, dreaming, that proved right today by @sibelius LOL~

matheus1lva commented 4 years ago

1 more thing left before we can do it: add a proper algorithm to scan sub node_modules folders, that supports monorepos! That is the next things i'm already doing!

matheus1lva commented 4 years ago

@renanmav we are almost there! There is only one more feature (i consider the most important) so we can start kicking this plugin!

we now need to scan the package.json file in order to find if we have src folders being published that were not required. What i mean by that: when we have a compilation step that generates a dist/build/opt/out/lib or whatever you may call it that is compiled code! In those scenarios they are not necessary, but in others they are!