Solve - create-next-app: command not found error

avatar

Borislav Hadzhiev

Sat Mar 12 20223 min read

'Solve - create-next-app: command not found error' #

Use npx to solve the error "create-next-app: command not found", e.g. npx create-next-app@latest or install the package globally by running npm install -g create-next-app@latest to be able to use the command without the npx prefix.

command not found create next app

The fastest way to solve the error is to use the npx command.

shell
# 👇️ create js app npx create-next-app@latest # 👇️ for a TypeScript project npx create-next-app@latest --typescript # 👇️ Print package version npx create-next-app@latest --version

Alternatively, you can install create-next-app globally.

shell
# 👇️ install package globally npm install -g create-next-app@latest # 👇️ create js app create-next-app # 👇️ for a TypeScript project create-next-app --typescript # 👇️ print package version create-next-app --version
If the global installation of create-next-app fails, you might have to run the command prefixed with sudo.
shell
# 👇️ if you got permissions error sudo npm install -g create-next-app@latest # 👇️ create js app create-next-app # 👇️ for a TypeScript project create-next-app --typescript # 👇️ print package version create-next-app --version

Refer to the official npm page of the create-next-app package for command options.

If the "create-next-app: command not found" error is not resolved, try restarting your terminal.

If that doesn't help, run the following command:

shell
npm config get prefix

The command will show you the path where npm puts your globally installed packages. The global packages will be in the bin directory at the specified path.

Look at the PATH environment variable on your operating system and add the path that the npm config get prefix command outputs, if it's not already there.

If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that didn't work, try to add the path to the bin folder (from npm config get prefix) to your PATH environment variable and restart your terminal.

For example, on macOS, you can update your path with the following command:

shell
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH

And on Windows, the output of the npm config get prefix command will look something like: C:\Users\Your_User_Name\AppData\Roaming\npm.

Edit the environment variable on your machine and add the specified path (replacing the placeholder with your username).

If you are on linux, you can add the output from the npm config get prefix command to your .bashrc file.

~/.bashrc
# 👇️ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that doesn't help try to reinstall Node.js on your machine and then install create-next-app globally by running npm install -g create-next-app@latest.

During the installation you might get a prompt for whether you want to automatically update the PATH environment variable on your system, make sure to tick the option.
shell
# 👇️ install package globally npm install -g create-next-app@latest # 👇️ create js app create-next-app # 👇️ for a TypeScript project create-next-app --typescript # 👇️ print package version create-next-app --version
If the global installation of create-next-app fails, you might have to run the command prefixed with sudo.
shell
# 👇️ if you got permissions error sudo npm install -g create-next-app@latest # 👇️ create js app create-next-app # 👇️ for a TypeScript project create-next-app --typescript # 👇️ print package version create-next-app --version

Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.

Use the search field on my Home Page to filter through my more than 1,000 articles.