42

In my package.json file, I have bower listed as a dependency. After I run npm install, bower gets installed locally. When I try to run bower after installing it locally I get an error

"bower" is not recognized as an internal or external command

It seems the only way to resolve this is to install bower globally. Why should I have to do this? If my project contains a local copy of bower, why won't node use it?

nbro
  • 15,395
  • 32
  • 113
  • 196
Rigil
  • 609
  • 3
  • 8
  • 15

4 Answers4

50

Installing locally makes bower available to the current project (where it stores all of the node modules in node_modules). This is usually only good for using a module like so var module = require('module'); It will not be available as a command that the shell can resolve until you install it globally npm install -g module where npm will install it in a place where your path variable will resolve this command.

Edit: This documentation explains it pretty thorougly.

cangosta
  • 1,174
  • 2
  • 13
  • 27
Jimi
  • 901
  • 7
  • 11
  • 3
    What would be the point in using bower locally such as var bower = require('bower'); ? – Rigil Dec 09 '14 at 22:57
  • 3
    Well, bower is a bad example since I don't think they expose an api through javascript, but ```express``` is something that I've used in a project that has a command line interface as well as a library you use locally in your js files. (See my edit for helpful documentation) – Jimi Dec 09 '14 at 23:03
  • 2
    It is also useful because commands in the `scripts` block in `package.json` automatically resolve local commands. That means you could have a script that depended on bower without having an undocumented dependency on bower. – loganfsmyth Dec 10 '14 at 00:38
23

You can execute your local instance by typing the line below in cmd:

node_modules/bower/bin/bower <bower args>
Selameab
  • 231
  • 2
  • 3
3

We use both PHP and JavaScript, so we have composer and npm.

Each of the projects we work on have different packages both for runtime of the package as well as build/dev tools.

As there are version constraints in each project, installing version x of a package globally (that would be run from the command line), would cause us issues, we install all the tooling in each package. Much easier to define in the appropriate composer.json / package.json files.

But running the CLI tools is a pain if you have to constantly add an additional path to the command.

To that end, we have recommend to the team that the following paths are added to your $PATH in the appropriate .bashrc (or equivalent):

./vendor/bin:./node_modules/.bin

(EDIT: For Windows, the paths would be .\vendor\bin;.\node_modules\.bin;)

So, whilst in project X, we have access to the CLI tools for that project. Switch to project Y, and we get that projects tools.

Sure, you are going to get duplications, but each project is maintained by different teams (and some people are in multiple teams), so again, having 1 version in the global setup is an issue there.

Richard A Quadling
  • 3,769
  • 30
  • 40
2

Usually you install NPM modules globally if you want them included in your path to be ran from the command line. Since it is installed locally you will have to run it from the node_modules folder.

Joseph Dailey
  • 4,735
  • 2
  • 15
  • 18
  • 1
    As linked in the accepted answer, it's not as straightforward as installing everything globally and not the recommended way. – PhilT Apr 22 '15 at 19:56