Data Structure
Networking
RDBMS
Operating System
Java
MS Excel
iOS
HTML
CSS
Android
Python
C Programming
C++
C#
MongoDB
MySQL
Javascript
PHP
Physics
Chemistry
Biology
Mathematics
English
Economics
Psychology
Social Studies
Fashion Studies
Legal Studies
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
What is the difference between Bower and npm in JavaScript?
npm
npm is generally used for managing Node.js modules and does nested dependency tree. It also works for front-end and used for developer tools like Grunt, CoffeeScript, etc.
Without using nested dependencies it is difficult to avoid dependency conflicts. So, using npm has proven to be great.
Whatever you add in Node is structured as modules. On using NPM for browser-side dependencies, you'll structure your code like Node.
Here’s the dependency structure:
project root [node_modules] -> dependency P -> dependency Q [node_modules] -> dependency P -> dependency R [node_modules] -> dependency Q [node_modules] -> dependency P -> dependency S
Bower
Bower requires a flat dependency tree and is used for the front end. It is useful for front-end packages.
It loads plain old JavaScript files like adding in the <script>…</script> in the <head> tag.
It is optimized for the front-end and used a flat dependency tree, which required only a single version for each package. This eventually reduced page load to a minimum.
Note: Bower is now deprecated.
Here’s the dependency structure:
project root [bower_components] -> dependency P -> dependency Q // wants P -> dependency R // wants Q and R -> dependency S
120 Views
To Continue Learning Please Login