CODEWITHSUNDEEP
node.jsreactjsreact-nativereact-native-ios
user10034296
user10034296

Reputation: 179

React Native Ios Error - ENOENT: no such file or directory, uv_cwd (null))

I get this error when running a new react native project. There is no error with the default starter code, but if a change even a letter of the starter text, I get this error.

Failed to load bundle(http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false) with error:(/Users/Pandey/Final/App.js: ENOENT: no such file or directory, uv_cwd (null))

Upvotes: 14

Views: 32606

Answers (9)

DEEP BLACK
DEEP BLACK

Reputation: 1

in case running npx expo start, restarting it makes work fine.

Upvotes: 0

samran
samran

Reputation: 723

I just change the directory and create project here its work fine

Upvotes: 1

Muhammad Numan
Muhammad Numan

Reputation: 25353

run this command on terminal

$ killall node

and check again I hope this error will not come again

Upvotes: 0

Jim O'Connell
Jim O'Connell

Reputation: 81

I just encountered this. I had multiple tabs open in my terminal, including one that had cdd into a now-deleted copy of my project directory.

In other words, i'd deleted the directory in a different tab and re-cloned it from Github. The other terminal tab was stuck in a 'ghost' directory.

cd out of it and back in and you should be fine.

Upvotes: 2

Yogesh Nikam Patil
Yogesh Nikam Patil

Reputation: 1280

It could also be that you have renamed a folder and your shell got messed up.

Upvotes: 1

Francesco Borzi
Francesco Borzi

Reputation: 61814

I had a similar issue and solved by switching to another directory (a non-npm project) and updating my global npm from there:

sudo npm install -g npm

then I switched back to the project and re-install the dependencies with npm install.

Upvotes: 4

Nikhil Singh
Nikhil Singh

Reputation: 49

If you are using capistrano and PM2 to deploy your project, this might happen due to them not being in sync. The proper thing to do in such case, would be to kill PM2 daemon, and start afresh. So, that capistrano will treat it as a new instance. This helped in my case.

Upvotes: 0

Dan
Dan

Reputation: 987

Seems to be an issue with the metro-bundler task. Check your terminal tabs to see if any are open from a previous project.

Metro Bundler Task in Terminal

Control + C to end it. If you know the port it was running on, you can check the port and kill the tasks from there.

ex. sudo lsof -i :8080

Find the PID and kill it with kill -9 PID_NUMBER.

Then go back to your root project directory and run npm start to start a new Metro Bundler.

Upvotes: 2

Pukar Sharma
Pukar Sharma

Reputation: 203

I had the same issue while building a node module and trying that in the test app. I solved it by closing and restarting the metro bundler.

The other methods I tried (but did not work for me):

  1. react-native upgrade
  2. unlink and link the module
  3. uninstalling the package and reinstalling.

Hope it was helpful! Cheers!

Upvotes: 17

Related Questions