Front-end package management tools The difference between NPM vs Bower

Front-end package management tools The difference between NPM vs Bower

The following for Internet data collation:

NPM is node Package Manager->javascript (-relative) package Manager

The difference between Bower and NPM:
The biggest difference between NPM and Bower is that NPM supports nested dependency management, while Bower can only support flat dependencies (nested dependencies, which are solved by programmers themselves).

Simply put, NPM is a modular installation tool for back-end development, and Bower is the front-end modular installation tool.

Why are there a lot of projects Bower and NPM used, because it's about using bower to manage the front-end packages, and NPM to manage some back-end packages and build tools, for example, Yeoman,grunt,gulp,jshint

NPM Install-g Bower

Bower Install [#]

One of the biggest differences with NPM is that NPM is mainly used for internal dependency pack management in Node.js projects, and the installed modules are located in the Node_modules folder under the project root directory. While Bower is used for front-end development in most cases, dependency management for content such as css/js/templates can be customized by the dependent download directory structure.

Unified build mechanism is not the responsibility of package management tool, the core value of Package Manager is to solve the dependency relationship

Other front-end package management tools: COMPONENT,SPM

Resources

Http://www.hlqf.net/archives/139.html

Http://blog.javachen.com/2014/05/10/bower-intro.html

https://segmentfault.com/a/1190000002525359