NPM/Bower/Composer - differences?
[update, four years later]
-
bower
is deprecated, and should not be used anymore for new projects. To a large extent, it has been subsumed into node dependency management (from their website: "While Bower is maintained, we recommend using Yarn and Webpack or Parcel for front-end projects"). -
yarn
came out of the wood as a betternpm
(fixing several ofnpm
flaws), and this is really what you should use now, as it is the new de-facto standard if you are doing front-end or node development. It does consume the samepackage.json
as npm, and is almost entirely compatible with it. - I wouldn't use
composer
at this point (because I wouldn't usephp
), although it seems to still be alive and popular
[original answer]
npm
is nodejs package manager. It therefore targets nodejs environments, which usually means server-side nodejs projects or command-line projects (bower itself is a npm package). If you are going to do anything with nodejs, then you are going to use npm.
bower
is a package manager that aims at (front-end) web projects. You need npm and nodejs to install bower and to execute it, though bower packages are not meant specifically for nodejs, but rather for the "browser" environment.
composer
is a dependency manager that targets php projects. If you are doing something with symfony (or plain old php), this is likely the way to go
Summing it up:
- doing node? you do npm
- doing php? try composer
- front-end javascript? try bower
And yes, the "json" files describe basic package information and dependencies. And yes, they are needed.
Now, what about the READMEs? :-)
- https://github.com/bower/bower
- https://www.npmjs.org/doc/cli/npm.html
- https://getcomposer.org/doc/00-intro.md
Related videos on Youtube
panthro
Updated on December 19, 2021Comments
-
panthro over 2 years
Can someone explain to me the difference between
NPM
,Bower
andComposer
.They are all package managers - correct?
But when should each one be used?
Also, each one appears to have a json file that accompanies it, does this store all the packages you require so they can be installed by cmd line? Why do you need this file?
-
mijaved almost 3 yearsAlso add Yarn (yarnpkg.com), NuGet (nuget.org) and Chocolatey (chocolatey.org) in the list, also read: en.wikipedia.org/wiki/…
-
-
sompylasar almost 10 yearsWhat about php+frontent applications? What's the best option?
-
Mangled Deutz almost 10 yearsDepends where you draw the line. Is your MVC in js (and your php is reduced to a WS)? Then likely use bower. Is your MVC in php (say, symfony), and you have a bunch of js hooked into your server side views? Then composer is likely your best pick.
-
PhoneixS over 9 years@MangledDeutz so can you use composer to manage javascript libraries?
-
Angel S. Moreno over 9 yearsThe most annoying and counter productive part is when you are working on libraries where, some only use bower; some only use composer and yet others only use npm. Would be nice to find a single package manager that with a single command handles all these package managers. It should be called Inception.
-
Angel S. Moreno over 9 yearsdid some googling and found github.com/francoispluchino/composer-asset-plugin
-
Eric over 9 yearsI think @AngelS.Moreno is right. There are too many lets make a 4th. :)
-
JG Estiot almost 9 years@AngelS.Moreno you are right and I would even go further than just stopping at installers and dependency managers. There are too many of everything. Too many JS libraries that do the same, too many PHP Frameworks and so on. If people could just work collaboratively on one thing, it would change life for a lot of us.
-
Ganesh Babu over 8 years@MangledDeutz Composer is not a package manager. It is a dependency manager. This is what I found in the definition. Can you please elaborate in brief about the difference between dependency manager and package manager
-
Mangled Deutz over 8 years@GaneshBabu.T.Y : there is no difference IMHO, and Composer is certainly a package manager (the explanation they put forward is quite ridiculous). If you still want to stick with that distinction though, then npm would be both a package and a dependency manager, and bower would be a dependency manager.
-
anonym over 7 years@GaneshBabu Since you depend on a lot of packages for your development, Composer works as a package manager for these dependencies.
-
online Thomas about 7 years
-
Chuck Le Butt about 7 yearsThis is out of date now. These days you can use NPM in place of Bower, and lots of people recommend doing just that. NPM is not just limited to nodejs environments.
-
Mangled Deutz almost 7 yearsAgreed. I would just use yarn today :)