I see from this question stack overflow the difference between the gazebo and npm:
npm is used to manage Node.js modules, but it can also work with the interface in combination with Browserify or WebPack. npm has a nested dependency tree, so your dependencies can have their own dependencies, which can have their own ... which basically can mean many versions of the same modules together, but not a problem on the server, and Browserify only processes this by binding the corresponding modules.
Bower is only used for the interface module and is optimized for this. This requires a flat dependency tree, which puts a strain on the resolution of dependencies on the user, which makes sense on the client, since we want to minimize the number of inclusions,
My question is:
If we use Browserify, does it make sense to use bower to manage foreground dependencies besides the following two advantages?
- management of front-end css modules includes, for example, pure.css or bootstrap.css,
- including 1 or 2 large JavaScript libraries, for example. Angular, React or jQuery as a global version on a page separate for your Browserify package - it would be useful to reduce the bloat of your .js package, even if it means an extra HTTP request