
## Table of Contents

1. [Introduction](#introduction)
2. [How to Enable Gulp](#how-to-enable-gulp)
3. [How to Enable Bower](#how-to-enable-bower)
4. [Git is Not Recognized Too?](#git-is-not-recognized-too)
5. [How to Enable Yo](#how-to-enable-yo)
6. [Still Not Working!?](#still-not-working)
7. [Conclusion](#conclusion)

## Introduction

You'll often see the following errors when running npm commands on a Windows OS system.

```
'Gulp' is not recognized as an internal or external command, operable program or batch file.
```

```
'Bower' is not recognized as an internal or external command, operable program or batch file.
```

```
'yo' is not recognized as an internal or external command, operable program or batch file.
```

Basically, you have to add the appropriate paths to the Environment Variables' `Path`.

## How to Enable Gulp

For gulp, you will have to add the following path to the Path System Variables so the command line will recognize npm's global path. Also, install gulp so the `gulp` command will be recognized. At the end, you'll have to restart the command line if you haven't done so after changing the system variables.

- Add path to Windows System Variables
  - %USERPROFILE%\AppData\Roaming\npm

  - C:\Program Files\nodejs\

Run the npm install command to install gulp:

    - `npm install -g gulp`

Restart Windows command line.

## How to Enable Bower

If you have already set up gulp, then the only thing you have to do is run npm for bower as a global package.

- `npm install -g bower`

## Git is Not Recognized Too?

- Go to Windows' Environment Variables and edit the Path variables. Make sure they contain the following paths, and also make sure Git actually exists at those locations.
  - Could be either of these:
    - `%PROGRAMFILES(x86)%\Git\bin`

    - %PROGRAMFILES(x86)%\Git\cmd

  Or maybe:
  - `%PROGRAMFILES%\Git\bin`

  - %PROGRAMFILES%\Git\cmd

## How to Enable Yo

It is the same as bower at this point. You will need to install Yeoman globally.

- `npm install -g yo`

If you can't install yo and the command line displays an error containing `If you are behind a proxy, please make sure that the 'proxy' config is set properly`, try running `npm config ls -l`. This command will show all the config settings for npm. Check the proxy — if the proxy is `null`, change it to `http://registry.npmjs.org/` with the following command:

```
npm config set registry http://registry.npmjs.org/
```

## Still Not Working!?

Before trying to figure out what's happening, restart your command line again — it might work. Also, it is better to use the Node.js command prompt.

## Conclusion

The "not recognized as an internal or external command" error on Windows is typically caused by missing paths in the system's Environment Variables. By adding the correct npm and Node.js paths, installing packages globally, and restarting the command line, you can resolve these issues for gulp, bower, yo, and Git.


How to fix 'XXX' is not recognized as an internal or external command, operable program or batch file.

Module is not Recognized as an Internal or External Command


## Table of Contents

1. [Introduction](#introduction)
2. [Installing live-server](#installing-live-server)
3. [Running live-server](#running-live-server)
4. [Troubleshooting](#troubleshooting)
5. [Conclusion](#conclusion)

## Introduction

NPM **live-server** is very useful when you want to set up a server to
serve files during development, such as serving HTML/JavaScript/CSS files as a web server. To use it, you'll need to have
`npm` installed first. On my development machine, I'm using Windows
7 with Node.js version `v6.5.0` and npm version `3.10.3`.

## Installing live-server

After installing Node.js, type the following command to install the npm package
**live-server** globally on your machine.

```
npm install -g live-server
```

The above command will install the npm module `live-server` globally on your
machine. Once installed, you can use it in any directory folder on your PC.

## Running live-server

Navigate to the folder you want to serve and type the following command:

```
live-server
```

Now, after you type the command, if the browser shows your folder contents, then you're
good to go.

## Troubleshooting

If the command line displays
**"live-server is not recognized as an internal or external command"**, then the live-server or Node.js execution path is probably not set up in
your Windows environment variables.

To fix this, verify your **System Properties → Environment Variables → Path Variable**.
Check to see if either the Node.js or live-server path is there. If it is
there, then restart the command line and run it again — sometimes the command line
needs a restart.

If the path is not there, you can reference the version that works on
my computer. The following is the path in my Windows environment path:

```
C:\Program Files\nodejs\
```

The following is how I run live-server in my picture folder.
![](https://d1p0mp3f1fx0hz.cloudfront.net/_zjqzo8u1k.png)

## Conclusion

The npm **live-server** package is a simple and effective tool for serving files during development. Install it globally with `npm install -g live-server`, navigate to your project folder, and run `live-server` to get started. If you encounter path issues on Windows, make sure the Node.js path is added to your system environment variables.


How to use the npm package live-server to serve files during development.

npm

Module is not Recognized as an Internal or External Command

How to Use npm live-server