After running npm install -g expo-cli and successfully installing the packages globally, expo is still not recognized as an internal or external command. Does anyone know how I might get around this issue using windows 10, or what to do in terms of something like a path variable.
Probably the only thing missing is to add the expo executable to your path.
For Windows 10, you can simply add the npm folder to your path environment variable.
Hit Windows key and search for Environment variables.
Inside the Path variable under System variables, add a new
entry (entries are separated by semicolons) with this content (without /node_modules ):
%USERPROFILE%\AppData\Roaming\npm
OR if you are using yarn C:\Users\{USER}\AppData\Local\Yarn\bin (as #Qwerty mentioned above)
Open a new command prompt and enter
> expo
You will see something like this:
I may be too late to answer this, but for people looking for the same error this is what worked for me.
Install yarn if you don't have it. I used the command choco install yarn (you'll have to install Chocolatey). If you have scoop installed, scoop install yarn also works.
Use yarn to install expo with yarn global add expo-cli.
expo start should work now. yarn start and npm start should also work.
Hope that helps!
I wondered it was working last night when I first installed and run the "react-native" project but the very next day it showed me the same error as yours.
Here is what I did in windows 10 Operating System:
Add the following path :
environment variable > System Variables > PATH > C:\Users\YOUR_USERNAME\AppData\Roaming\npm
Now I ran the following commands one by one in CMD:
i) npm -g uninstall expo-cli --save
ii) npm install -g expo-cli
Now start the Project and run npm start and now it works for me.
I didn't try this article one but it also shows the solution for the same problem,
see here
Added These path of npm like this i have the same issue i fix it by adding the path to environment system
C:\Users\abobakr\AppData\Roaming\npm
After that close CMD and open it again it should work believe me
go to the environment variable, then in the user variable section find Path and press the edit button, you will see a new window, press new and add the following
%USERPROFILE%\AppData\Roaming\npm
then press ok. Now,
expo --version
Here is the solution I came out with.
I ran npm list -g
then copy the directory on the first line and paste in your system enviroment variables under the variable name 'path'
close all the terminals and run expo or any other command.
This worked for me :
Download latest version of nodejs - https://nodejs.org/en/download/
After installing nodejs reboot your computer
install : npm install --global expo-cli
Generate a new project with - npx expo-cli init projectName
cd projectName
npm start
If it still doesnt work or you can't access npm. Try setting the path with the Windows PowerShell:
Open Windows Powershell as Administrator
Type: setx path "%path%;C:\Users\USERNAME\AppData\Roaming\npm"
It worked for me.
Re-install node.js and
then run npm install -g expo-cli in command prompt.
If you are using Windows 10 or 11, the solution to edit your Path variable works well.
Just make sure that you replace "YOUR_USERNAME" with your username on the computer:
This means that if my username is "Green", I will replace YOUR_USERNAME here:
C:\Users\YOUR_USERNAME\AppData\Roaming\npm
to
C:\Users\Green\AppData\Roaming\npm.
This article is very detailed in solving the problem in case if the above does not work for you.
I had the same problem last night, and I've recently started my journey in ReactNative. So, there might be better answers out there.
If you're following the ReactNative Official documentation, the first time npm start works fine, the subsequent ones throws an error saying expo is not recognized. I got around that by running expo start and not npm start ( which basically is the same thing but doesn't work for some reason ).
So, mine looks like a work around rather than an explanation as to why this happens or how to permanently fix it.
For me,
i uninstalled node.js,
i re-installed node.js,
i ran npm install -g expo-cli,
then ran expo --version (the expo command began to work).
Hope this helps.
This worked for me:
You must uninstall node js then install it again.
You must run npm install expo-cli.
It will solve your problem
This is a more general problem where your global node modules are not in your system path. This question is what you are looking for: Nodejs cannot find installed module on Windows?
I have fixed this in Windows 10 by setting Path C:\Users\[USERNAME] this line save my hrs
uninstall expo using this command
npm -g uninstall expo-cli --save
and reinstall expo using this command
npm install -g expo-cli
then it will work properly
I faced same problem and it was not getting resolved by "npm install --global expo-cli".
Global CLI was having error as SS below -
npm list -g --depth 0
Followed below steps to get it resolved
npm uninstall --global expo-cli
Deleted global package causing error C:\Users<USERNAME>\AppData\Roaming\npm\node_modules\expo-cli
npm install --global expo-cli
And expo cli worked.
Happy coding!!!
If you need a solution to Run Expo command without Environment Variable update then on your terminal use below command for windows system:
R:\> C:\Users\{user}\AppData\Roaming\npm\expo.cmd init {projectname}
Where you directly point the expo.cmd file rather than specifying in the environment variable.
And update the expo to C:\Users{user}\AppData\Roaming\npm\expo.cmd in package.json to run the project.
// package.json
"scripts": {
"start": "C:\\Users\\{user}\\AppData\\Roaming\\npm\\expo.cmd start",
"android": "C:\\Users\\{user}\\AppData\\Roaming\\npm\\expo.cmd start --android",
"ios": "C:\\Users\\{user}\\AppData\\Roaming\\npm\\expo.cmd start --ios",
"web": "C:\\Users\\{user}\\AppData\\Roaming\\npm\\expo.cmdstart --web",
"eject": "C:\\Users\\{user}\\AppData\\Roaming\\npm\\expo.cmd eject"
},
If you are using yarn global add expo-cli, try npm install -g expo-cli.
I don't know why but when i go into C:\Users\%{user}%\AppData\Roaming\npm there isn't the expo package(and other packages that I thought I install globally by yarn) but there are other that I installed globally by npm.
If adding C:\Users\%{user}%\AppData\Roaming\npm to PATH variable doesn't work, give this a shot.
If you set the environment path as said in other replies and the command is still not recognized, try running whatever you're using to execute the command in administrator mode.
I'm using VS Code terminal and expo was not recognized until I ran it as administartor.
Related
I have been trying to install some packages and libraries like react-dom and react-icons but I have not been able to get any luck.
Every time I run an npm install command such as:
npm install react-icons --save
or:
npm install react react-dom
All I get is a blank line in terminal and my install doesn't go through.
This is irregardless of whether I add --save or not.
It is also irregardless of whether I use something like an integrated terminal in VS Code or my native terminal application.
npm start works and such so I'm thinking its just my install command that is failing.
It might be the case npm is not istalled? Do you have Node.js installed? NPM is included with Node.js installation. In order to check open your terminal and type npm -v. If it's installed you are going to see something like v8.10.0.
I am trying to install the Vue CLI in ubuntu (WSL), but it doesn't seem to work for some reason. I ran the command yarn add global #vue/cli, and I also tried with npm install #vue/cli --global. The commands run as though they were successfull, but as soon as I run vue --version, it throws command vue not found. Any ideas?
Solved! (partly) after a lot of time, I went with the npm installation and it worked out of the box. To use yarn, add the following to your ~/.bashrc:
export PATH="$PATH:$(yarn global bin)"
When I run npm start, I get this error. What is the solution for this?
This issue has been addressed here, you can refer to it.
Complete solution is
First add Poweshell to PATH as %SystemRoot%/system32/WindowsPowerShell/v1.0.
open powershell as admin and write this command Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force.
last thing fire npm-windows-upgrade.
Check your node version. update node & npm
try sudo npm start if you are in macOS or linux
try to download create-react-app again npm i -g create-react-app
try to create the app in another folder create-react-app APPNAME
Still not working? Then delete node module folder and run npm install
Not yet? delete both node module & package-lock.json and npm install
Try to run on another PORT
This image contains details about the error when I am typing npm-start
I have created a react-app using create-react-app. I have created another app using the same but when I type npm-start, it displays an error and localhost:3000 stops working.
Missing npm package
Use the cmd to install npm package npm install
Check the docs here
To solve this problem you can follow these steps.
First, reinstall node_modules:
rm -rf node_modules/ && npm i //(rm -rf will only work if you have macOS for windows you need to delete node_modules manually)//
Then, start the project:
npm start
or
yarn start
This error solved by few easier simple steps. That steps are
Go to your setting
Open your environment variable screen
Delete ComSpec variable completely and click ok
Uninstall your NodeJS
Reinstall your nodejs setup,
Finally it will be work
I installed npm-run-all and also configured the environment variable (which may or may not be not required) on my Windows machine but am getting an error:
'npm-run-all' is not recognized as an internal or external command,
operable program or batch file
I am trying to build my current project with npm run build which includes the script where the error is thrown:
npm-run-all -p build-css build-webpack
Do I have to do any additional things to make it run?
Make sure the npm-run-all is in your package.json devDependencies.
If npm-run-all is present in your package.json, run npm i
If not present install it, run: npm i npm-run-all -D
If error is still present, follow these steps:
Remove node_modules folder: run rm -rf node_modules
Install all dependecies: run npm i
Hope this helps!
You may just need to run the following command first (from the directory with the package.json file)
npm install
Please do that like this.
npm i npm-run-all -g
And then this issue will be fixed.
You have a couple of options here, besides installing npm-run-all as a global package as suggested by #Vaibhav in the comments:
1) Create an NPM script
The package.json file has a scripts section which can used to define shortcuts for anything you need to run while you're working on your app. There are some pre-defined scripts, like run or test than can be executed with simply npm start/npm test or you can define anything you like and then run it with npm run my-script-name. You could try:
{
"scripts": {
"start": "npm-run-all -p build-css build-webpack"
}
}
Any NPM module referenced here "just works" (i.e. the path to the executable is resolved under the hood by NPM)
2) NPX
In newer versions of NPM (i.e. >= 5.2 or so), the "NPX" executable is provided. This has a similar effect to running commands inside an NPM script. You would run:
npx npm-run-all -p build-css build-webpack
Again, the path would be automatically resolved.
If you have an older NPM install, you can also install it separately:
npm install -g npx
npm install -g npm-run-all
Works for me.
Double check if npm-run-all is in your package.json devDependencies.
I had same problem while using code editor Brackets.
To resolve the error, I did the following steps.
Add nodejs new system variable to your PC under Control Panel -> System -> Advanced System Settings
;C:\Program Files\nodejs\
After that, re-run command:
npm
I don't know if this would help anyone, but I got this error because I was doing nodemon server.js instead of nodemon server/server.js. I wasn't in the right folder!
Did you reopen the terminal after you installed node?
If you have installed npm with the current terminal window open. Your terminal window will not have loaded the latest path settings (with npm location) to find the npm application to run the command. In this case try below steps .
Try closing the current terminal session.
Reopen a new session.
Try the command again ( will pick up the new path settings with npm installed)
This worked for me.
npm audit fix --force
Also you can try downgrading your autoprefixer, seems version 10.0.0 doesn't work well with postcss
npm i autoprefixer#9.8.6