What is the difference between package.json vs bower.json.?
what is the criteria that we should consider before defining the dependencies in both files.
And what difference will it make by running "bower install" and "npm install" ?
What is the difference between package.json vs bower.json.?
what is the criteria that we should consider before defining the dependencies in both files.
And what difference will it make by running "bower install" and "npm install" ?
NPM (package.json)
npm is most commonly used for managing Node.js modules, but it works for the front-end too when combined with Browserify and/or $ npm dedupe.
Bower (bower.json)
Bower is created solely for the front-end and is optimized with that in mind. The biggest difference is that npm does nested dependency tree (size heavy) while Bower requires a flat dependency tree (puts the burden of dependency resolution on the user).
A nested dependency tree means that your dependencies can have their own dependencies which can have their own, and so on. This is really great on the server where you don't have to care much about space and latency. It lets you not have to care about dependency conflicts as all your dependencies use e.g. their own version of Underscore. This obviously doesn't work that well on the front-end. Imagine a site having to download three copies of jQuery.
In short, NPM aims for stability. Bower aims for minimal resource load. If you draw out the dependency structure.
npm dependencies are defined or added to package.json. Bower dependencies are in bower.json.
** Package.json file is for node related package manager while bower can manage application level package dependencies. I like bower more.
** We need to find which dependencies related to development and which are production.
** "bower install" -- Install all dependencies mentioned in Dependencies object. ** "bower install -D" -- Install all dependencies mentioned in DevDependencies object.
Same with Npm Install and npm install -D
© 2022 - 2024 — McMap. All rights reserved.