React-native: error: bundling failed: Error: ENOENT: no such file or directory, uv_cwd

[patrice4github]

Sorry this comes back again with the latest 0.56. No steps to reproduce, the startup just won't work.

Environment

Patrices-iMac:adn-083 patricegagnon$ react-native info
Scanning folders for symlinks in /Users/patricegagnon/_projects/outs/adn-083/node_modules (15ms)
(node:71272) ExperimentalWarning: The fs.promises API is experimental

React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 34.46 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.1.0 - /usr/local/bin/node
Yarn: 1.6.0 - /usr/local/bin/yarn
npm: 5.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
IDEs:
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
react: 16.4.1 => 16.4.1
react-native: 0.56.0 => 0.56.0
npmGlobalPackages:
create-react-native-app: 1

Description

This appears to be a regression as we've seen this before. The app refuses to start.

Reproducible Demo

The entire project is shared on Dropbox. It just refuses to start:

The project

[patrice4github]

Here is the console stacktrace:

error: bundling failed: Error: ENOENT: no such file or directory, uv_cwd at Object.resolve (path.js:1086:25) at loadPrivatePartialConfig (/Users/patricegagnon/_projects/outs/adn-083/node_modules/@babel/core/lib/config/partial.js:44:39) at loadFullConfig (/Users/patricegagnon/_projects/outs/adn-083/node_modules/@babel/core/lib/config/full.js:43:39) at transformSync (/Users/patricegagnon/_projects/outs/adn-083/node_modules/@babel/core/lib/transform-sync.js:15:38) at Object.transform (/Users/patricegagnon/_projects/outs/adn-083/node_modules/metro/src/reactNativeTransformer.js:163:5) at Object.<anonymous> (/Users/patricegagnon/_projects/outs/adn-083/node_modules/metro/src/JSTransformer/worker.js:204:23) at Generator.next (<anonymous>) at step (/Users/patricegagnon/_projects/outs/adn-083/node_modules/metro/src/JSTransformer/worker.js:328:291) at /Users/patricegagnon/_projects/outs/adn-083/node_modules/metro/src/JSTransformer/worker.js:328:521 BUNDLE [ios, dev] ../../index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1), failed.

[mjonesjr90]

Seeing the same issue

[patrice4github]

Have you tried rebooting?

[atyenoria]

I came across the same issue just now. npm reinstalling and rebooting work fine.

[CodeMuz]

Check if $ yarn start works. The metro bundler wasn't able to run on port 8081 for me and I needed to run $ killall node

[patrice4github]

I think that's what it is, why rebooting fixes it.
The process gets a hang of the port 8081, and somehow won't release it.

I call this a bug. There should be a proper termination of the metro
bundler so the port is always released properly.

On Tue, Sep 11, 2018 at 4:38 AM, murray [e-mail] wrote:

Check if $ yarn start works. The metro bundler wasn't able to run on port
8081 for me and I needed to run $ killall node

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/21038#issuecomment-420193598,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABpbfsA_FMWuLTNRBz96aE6RyeqDuKzRks5uZ3aZgaJpZM4WhiaI
.

[mjonesjr90]

Restarting worked for me as well - thanks!

[react-native-bot]

It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists.

The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

[DalerAsrorov]

Thanks @CodeMuz, $ killall node and then $ rm -rf ios/build/ && react-native run-ios worked for me.

[kaushal9678]

Just close your current terminal window and run again ios, android commands. It will work. It worked for me.

[lchenfox]

Check if $ yarn start works. The metro bundler wasn't able to run on port 8081 for me and I needed to run $ killall node

Thanks. It solved my problem

[Digvijaykumar21]

digvijay@digvijay:~/Desktop/test$ kilall node

Command 'kilall' not found, did you mean:

command 'killall' from deb psmisc

Try: sudo apt install

digvijay@digvijay:~/Desktop/test$ killall node
node: no process found
digvijay@digvijay:~/Desktop/test$ killall -s KILL node
node: no process found
digvijay@digvijay:~/Desktop/test$ killall --s KILL node
node: no process found
digvijay@digvijay:~/Desktop/test$ killall node
node: no process found

[ramseykes]

Maybe you moved the file

[kaushal9678]

Just remove your app from the emulator or device and close the terminal that running bundler. Now start the process again by calling react-native run-android or iOS it will work.

[kelset]

Closing as it seems that it's just a caching issue - thanks everyone for the feedback!

[Youn-ha]

Rebooting fixed my problem out too. I tried every other methods but all failed. thanks for everyone

[al-exe]

Check if $ yarn start works. The metro bundler wasn't able to run on port 8081 for me and I needed to run $ killall node

you saved my life, thank you

[Goran7777]

I have had same problem when my wi-fi conection stack on milisecond when script runs.

[dvetal]

I saw this on 57.7 . just a note.

[Gian-08]

ENOENT: no such file or directory, scandir 'C:\Users\gian-\gsm-v3\pages\node_modules\imagenes'
Failed building JavaScript bundle. HELP ME PLEASE :(

[raimonkh]

I've seen this on MacOS when building on CircleCI (the android app).

Error: ENOENT: no such file or directory, open '/Users/distiller/repo/android/app/build/generated/assets/react/<apname>/release/CodePushHash'

I haven't found the issue yet

[toro705]

I've seen this on MacOS when building on CircleCI (the android app).

Error: ENOENT: no such file or directory, open '/Users/distiller/repo/android/app/build/generated/assets/react/<apname>/release/CodePushHash'

I haven't found the issue yet

found any answers yet?

[raimonkh]

@toro705 in our case we created those files manually as the build process only required they "existed" although empty...

[ryancwalsh]

Just close your current terminal window and run again ios, android commands. It will work. It worked for me.

Thanks @kaushal9678 . I was in Homestead Vagrant. I exited out of that terminal session, ran vagrant ssh again to get back in, ran npm install again, and then npm start worked without error.