Bower is not recognized as an internal or external command

Question

I successfully installed nodejs and expressed the framework, however I downloaded bower via

npm install -g bower 

which was successfully executed.

However, whenever I try to install something with bower, I get an error

 bower is not recognised as an internal or external command 

when I search my computer for a gazebo or bower.exe, I can not find it.

Answer 1

I also use Windows 7 and I had this problem too.

After I followed the steps outlined in Scott Marchan's answer , the conversation worked.

Find the location of your national npm binaries: npm config get prefix. This path might look something like this: C: \ Users \ username \ AppData \ Roaming \ npm. Add the path from step 1 to your path.

Open the Windows control panel, find the environment, then click either change the environment variables for your account or change the system environment variables`.

Find a variable named Path or PATH or create one if it does not exist.

Paste the path from step 1 here (; separate).

You may need to restart the command prompt window.

You should now be able to enter bower commands.

Answer 2

I solved this problem using the command

 $ npm install -g bower 

make sure -g exists on the command.

I am using os Window10.

Answer 3

Install Bower Windows:

1. Install Node.js (required)
2. npm install -g bower
3. Add the Path environment variable for your Systems and Users as follows:

; C: \ Users \ I \ AppData \ Roaming \ NPM \ node_modules \ stanovoy \ Bin

4. Reboot machine
5. Open a command prompt anywhere and type bower to make sure it works. MADE.

Answer 4

• Open cmd

• Verify that the sidebar is installed successfully:

  bower version -v If the bower version is shown, go to step 3, otherwise run:

  npm install -g bower to install the gazebo

• Close and reopen cmd (to apply the new environment variables)

• using the cd command to go to the folder with the bower.json file, then run

  bower installation MADE.

Answer 5

Sometimes even after Scott's steps do not resolve the problem. Open a command prompt in administrator mode. This solves the problem.

Answer 6

• Click Window + R
  
• % appdata% Press Enter
  
• C: \ Users \ Hoog \ AppData \ Roaming \ NPM
  
• Double-click the bower.cmd icon
  
• Press Shift Right Mouse Click Then Selec Open the command window here
  
• Paste bower install MDBootstrap
  

SCREENSHOT

Answer 7

Check if your cmd / bash hint was located when you successfully run the "npm install" command

Look for any of the following. -bower.cmd - windows script command -bower - file you can perform a quick search in the directory.

if you find it, copy the file path. "I found mine in the directory where I successfully completed npm install" + node_modules.bin "-" D: \ Work \ notepadplusplus \ htdocs \ laravel-main \ angulartest \ public \ fed \ node_modules.bin "

Then do these

• Open Windows Control Panel
• Go to Advance
• Environment Variables
• Click either change the environment variables for your account or change the system environment variables `.
• Find a variable named Path or PATH or create one if it does not exist.
• Paste the path from your search before (; delimiter and no space).
• restart the command prompt window or bash window.

There is no concrete way, since we all have a different structure of our catalogs. The only exact thing here is to find the location of bower.cmd, and this will be used for the path to your Windows environment.

Answer 8

Although we already have good answers, I will give an additional hint. Check if there is a .npmrc file inside the / Users / YOUR _USER / folder. When this problem arose with me, my .npmrc file had this content:

 http_proxy=http://<LOGIN>:<PASSWORD>@<PROXY>:<PORT> https_proxy=http://<LOGIN>:<PASSWORD>@<PROXY>:<PORT> proxy=http://<LOGIN>:<PASSWORD>@<PROXY>:<PORT>/ https-proxy=http://<LOGIN>:<PASSWORD>@<PROXY>:<PORT> prefix = "D:\\<SOME_DIR>\\nodejs" cache = "D:\\<SOME_DIR>\\nodejs\\npm-cache" 

Because of the lines, the prefix and cache, the gazebo was installed inside the folder specified in the prefix.

SOLUTION: I deleted the line prefix and cache . I installed the gazebo again with the following command:

 npm install -g bower 

After that, my gazebo became global, as expected.

Answer 9

C:\Users\[username]\AppData\Roaming\npm;

must exist in PATH for "user variables" and "system variables"

Answer 10

I solved the problem of changing permissions on the node.js. folder I gave read and write access to the file, and the problem was resolved. node.js file path: C: \ Program Files \ nodejs

Answer 11

I just wanted to add an update for Windows 10 users. I found that typing the gazebo in the search bar will return the "execute command" option. Do this and he will then suggest if bower can send the information, return y / n, and you should be good to go.

Answer 12

Add the bower directory to the PATH environment variable. Avoid space between directories:

 C:\Program Files\nodejs;C:\Users\W\AppData\Roaming\npm\node_modules\bower\bin;C:\Users\W\AppData\Roaming\npm 

This helped me remove the user variable and write the PATH environment variable in the system variables.

Answer 13

I ran into the same problem. I decided using the following steps

1. Go to Control Panel \ System and Security \ System and click Advanced System Settings.

2. In this, you can see the environment variables on the Advanced tab. Now the environment variables window opens.

3. Select the path and click the "Edit" button and add C: \ Users \\ AppData \ Roaming \ npm. Click OK to save.

Note: before adding the path, add a colon (;) before this path, if there was no previous

Now you can install the gazebo. Hope it helps.