react-native 0.57.0-rc.0 - Error: ENOENT: no such file or directory [Windows]

[ExoMemphiz]

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

[skip envinfo]
Windows 10, trying to run on Android.

Description

Tried to run the newest NPM package of 0.57.0-rc.0 (Hoping it would fix AccessibilityInfo error)
I ran into this error instead:

 BUNDLE  [android, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1)::ffff:127.0.0.1 - - [17/Aug/2018:11:25:37 +0000] "GET /index.delta?platform=android&dev=true&minify=false HTTP/1.1" 500 - "-" "okhttp/3.10.0"
error: bundling failed: Error: ENOENT: no such file or directory, lstat 'D:\Development\Action Menu\testVersion2\node_modules\react-native\scripts\index.js'
    at Object.realpathSync (fs.js:1657:15)
    at DependencyGraph.getSha1 (D:\Development\Action Menu\testVersion2\node_modules\metro\src\node-haste\DependencyGraph.js:236:29)
    at D:\Development\Action Menu\testVersion2\node_modules\metro\src\Bundler.js:203:56
    at Generator.next (<anonymous>)
    at step (D:\Development\Action Menu\testVersion2\node_modules\metro\src\Bundler.js:11:657)
    at D:\Development\Action Menu\testVersion2\node_modules\metro\src\Bundler.js:11:817
    at <anonymous>
 BUNDLE  [android, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1), failed.

Reproducible Demo

Run:

react-native init --version="0.57.0-rc.0" testVersion
cd testVersion
react-native run-android

[gengjiawen]

Have the same issue:

 BUNDLE  [android, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1)::ffff:127.0.0.1 - - [17/Aug/2018:13:11:28 +0000] "GET /index.delta?platform=android&dev=true&minify=false HTTP/1.1" 500 - "-" "okhttp/3.10.0"
error: bundling failed: Error: ENOENT: no such file or directory, lstat 'D:\Developer\FrontEnd\test_057\node_modules\react-native\scripts\index.js'
    at Object.realpathSync (fs.js:1430:7)
    at DependencyGraph.getSha1 (D:\Developer\FrontEnd\test_057\node_modules\metro\src\node-haste\DependencyGraph.js:236:29)
    at D:\Developer\FrontEnd\test_057\node_modules\metro\src\Bundler.js:203:56
    at Generator.next (<anonymous>)
    at step (D:\Developer\FrontEnd\test_057\node_modules\metro\src\Bundler.js:11:657)
    at D:\Developer\FrontEnd\test_057\node_modules\metro\src\Bundler.js:11:817
    at process._tickCallback (internal/process/next_tick.js:68:7)

[gengjiawen]

Looks like something forget to bundle:

[kelset]

Hey folks thank for reporting, just double checked locally (on macOS) and it seems to me that it's not just Windows related (I'll remove the label) - I get this error /testVersion/node_modules/react-native/scripts/packager.sh: No such file or directory

My current hypotesis is that it's something outdated in the react-native run-xxx command, that instead of running the "latest" version of the command > node node_modules/react-native/local-cli/cli.js start runs an outdated version (that points to an old reference that is not there anymore).

Can you try to run npm start to manually start the packager and then in a second window run the react-native run-xxx command again?

[gengjiawen]

You can use npm run start to start the dev server as an workaround.

[gengjiawen]

And I also tried the android release build, works too.

[timri]

The bundler, when spawned from "react-native run-android", looks in node_modules/react-native/scripts first, when I interpret the message correctly. See screenshot (unfortunatly I can not mark&copy text in that window):

When I use "react-native start", only the project-dir is searched (but 3 times??):

D:\vagrant\TestWin>react-native start
Scanning folders for symlinks in D:\vagrant\TestWin\node_modules (24ms)

┌──────────────────────────────────────────────────────────────────────────────┐
│                                                                              │
│  Running Metro Bundler on port 8081.                                         │
│                                                                              │
│  Keep Metro running while developing on any JS projects. Feel free to        │
│  close this tab and run your own Metro instance if you prefer.               │
│                                                                              │
│  https://github.com/facebook/react-native                                    │
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   D:\vagrant\TestWin
   D:\vagrant\TestWin
   D:\vagrant\TestWin

Loading dependency graph, done.
 BUNDLE  [android, dev] ./index.js ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100.0% (505/505), done.

::ffff:127.0.0.1 - - [17/Aug/2018:18:23:53 +0000] "GET /index.delta?platform=android&dev=true&minify=false HTTP/1.1" 200 - "-" "okhttp/3.10.0"

The good news is, that 0.57.0-rc.0 seems to fix #20353 (I would comment that there, however that issue is locked....)

[timri]

Fixing this seems easy, when I replace

react-native/local-cli/runAndroid/runAndroid.js

Line 365 in 625c54d

const procConfig = {cwd: scriptsDir};

with

  const procConfig = {};

"react-native run-android" works (on windows), because otherwise the scripsDir is taken as projectRoot for the packager, since that is the default-value in

react-native/local-cli/core/index.js

Line 59 in 625c54d

const appRoot = process.cwd();

At least if I understand the code correctly here, it's the first time I look into the react-native-code ;-)
Or maybe it should better be set to the root-Folder (explicitly)?

[kelset]

Hey Tim, thanks for the investigation, it seems to be in line with my hypothesis. Want to try and submit a PR for it? I feel like the same error will be found on the runIOS file

[ferily7]

I tried what @timri did with the procConfig, but I still seem to get the same error:

bundling failed: Error: ENOENT: no such file or directory, lstat 'C:\Users\user\Documents\Test\node_modules\react-native\scripts\index.js'
    at Object.realpathSync (fs.js:1657:15)
    at DependencyGraph.getSha1 (C:\Users\user\Documents\Test\node_modules\metro\src\node-haste\DependencyGraph.js:236:29)
    at C:\Users\user\Documents\Test\node_modules\metro\src\Bundler.js:203:56
    at Generator.next (<anonymous>)
    at step (C:\Users\user\Documents\Test\node_modules\metro\src\Bundler.js:11:657)
    at C:\Users\user\Documents\Test\node_modules\metro\src\Bundler.js:11:817
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

Edit: For some reason it didn't work for me the other day, but I just tested it today and it worked!

[sharathk]

I'm on Windows 10 and Tried as @timri suggested

In react-native/local-cli/runAndroid/runAndroid.js

Line 365 in 625c54d
const procConfig = {cwd: scriptsDir};
with
const procConfig = {};

Worked for me..

[kesha-antonov]

macos. Same problem
node_modules/react-native/scripts/packager.sh: No such file or directory

[kelset]

Ok, so. I spent some time trying to understand what this is caused by and I found two "different" issues.

First one, basically on macOS when run-XXX get called this file gets executed launchPackager.command but this file references packager.sh which doesn't get bundled in the "node_module" version of react-native. I don't know why this happens but, yeah, I feel like packager.sh needs to be in the node_module. (cc @hramos maybe you know why it's not there?)
BTW, if I manually add the script, the command gets run properly and the Metro packager runs, but when it tries to bundle gives me back this error:

error: bundling failed: Error: ENOENT: no such file or directory, lstat '/private/tmp/RNTestProject/node_modules/react-native/index.js'
    at Object.realpathSync (fs.js:1421:7)
    at DependencyGraph.getSha1 (/private/tmp/RNTestProject/node_modules/metro/src/node-haste/DependencyGraph.js:236:29)
    at /private/tmp/RNTestProject/node_modules/metro/src/Bundler.js:203:56
    at Generator.next (<anonymous>)
    at step (/private/tmp/RNTestProject/node_modules/metro/src/Bundler.js:11:657)
    at /private/tmp/RNTestProject/node_modules/metro/src/Bundler.js:11:817
    at process._tickCallback (internal/process/next_tick.js:68:7)

The second issue is related to the bundler, and I think I figured out why, or, at least, which commit may be related to the issue. Looking at the history for react-native/local-cli/cliEntry.js and react-native/local-cli/core/index.js one of the last commits is by @CompuIves and it seems to be related to the config that gets passed around the CLI.

Two more people who may have a better understading of why the run command fails to load the bundler with the right configuration are @janicduplessis and @rafeca.