Skip to content

error: bundling failed: Error: ENOENT: no such file or directory, uv_cwd #21038

@patrice4github

Description

@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

Activity

patrice4github

patrice4github commented on Sep 10, 2018

@patrice4github
Author

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

mjonesjr90 commented on Sep 10, 2018

@mjonesjr90

Seeing the same issue

patrice4github

patrice4github commented on Sep 10, 2018

@patrice4github
Author

Have you tried rebooting?

atyenoria

atyenoria commented on Sep 11, 2018

@atyenoria

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

CodeMuz

CodeMuz commented on Sep 11, 2018

@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

patrice4github commented on Sep 11, 2018

@patrice4github
Author
mjonesjr90

mjonesjr90 commented on Sep 11, 2018

@mjonesjr90

Restarting worked for me as well - thanks!

react-native-bot

react-native-bot commented on Sep 12, 2018

@react-native-bot
Collaborator

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

DalerAsrorov commented on Oct 11, 2018

@DalerAsrorov

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

kaushal9678

kaushal9678 commented on Dec 23, 2018

@kaushal9678

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

arlovip

arlovip commented on Apr 1, 2019

@arlovip

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

2 remaining items

kaushal9678

kaushal9678 commented on May 3, 2019

@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

kelset commented on May 3, 2019

@kelset
Contributor

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

Youn-ha

Youn-ha commented on Jun 27, 2019

@Youn-ha

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

al-exe

al-exe commented on Aug 2, 2019

@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

ghost
dvetal

dvetal commented on Nov 9, 2019

@dvetal

I saw this on 57.7 . just a note.

Gian-08

Gian-08 commented on Nov 12, 2019

@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

raimonkh commented on Nov 13, 2019

@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

toro705 commented on Dec 6, 2019

@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

raimonkh commented on Dec 9, 2019

@raimonkh

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

ryancwalsh

ryancwalsh commented on Apr 10, 2020

@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.

locked as resolved and limited conversation to collaborators on May 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @hramos@patrice4github@CodeMuz@ryancwalsh@kaushal9678

        Issue actions

          error: bundling failed: Error: ENOENT: no such file or directory, uv_cwd · Issue #21038 · facebook/react-native