I’m not sure what the best way to do this is, but I think that it’s worth doing.
Discription

The Problem

When you have a large codebase with many modules, it can be hard to keep track of which dependencies are being used by your application and which ones are just being transitively pulled in because they’re needed by some other dependency. This problem is especially acute when you use tools like npm link , since there’s no easy way for users of your package to tell whether or not their app will actually need the module in question
https://t.co/R7crnBN4y4

Back to Main

Subscribe for the latest news: