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

ExoMemphiz · 2018-08-17T11:30:48Z

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

The text was updated successfully, but these errors were encountered:

gengjiawen · 2018-08-17T13:12:40Z

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 · 2018-08-17T13:19:29Z

Looks like something forget to bundle:

kelset · 2018-08-17T14:02:34Z

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 · 2018-08-17T14:03:06Z

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

gengjiawen · 2018-08-17T14:05:25Z

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

timri · 2018-08-17T18:29:10Z

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 · 2018-08-17T19:21:36Z

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 · 2018-08-17T19:49:32Z

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 · 2018-08-17T22:33:34Z

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 · 2018-08-18T03:20:34Z

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

kelset · 2018-08-18T17:52:57Z

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.

gengjiawen · 2018-08-19T07:50:45Z

The package.sh is removed by one of my prs to make it test RNTester cross-platform, not sure why it affect this. Is it run-android use different method on winodws platform ?

kelset · 2018-08-20T10:05:41Z

@gengjiawen I don't think it "strictly" affects this issue, it's simply something that I found out during my investigation (so, like, a side issue) - but I think that then we need to reverse that change to re-add that file. Would it be possible?

gengjiawen · 2018-08-20T13:03:15Z

Okay, I will create a pr, I removed it because I the file is redundant at that time.

gengjiawen · 2018-08-20T13:11:19Z

@kelset PR created: #20751.

gengjiawen · 2018-08-20T13:12:10Z

Also, as I mentioned earlier, this has workaround. You can use npm run start to start the dev server.

gengjiawen · 2018-08-20T14:37:43Z

I checked the log again, looks like metro find the wrong project roots. cc @rafeca

Looking for JS files in
   D:\Developer\FrontEnd\test_057\node_modules\react-native\scripts
   D:\Developer\FrontEnd\test_057
   D:\Developer\FrontEnd\test_057

dmead · 2018-08-22T09:49:55Z

I made the fix as discussed above on line 365 of runAndroid.js

It's does eliminate that error, but i'm left with this error

fungilation · 2018-08-22T11:32:13Z

I'm getting a different error but related to Metro also (on Windows), after upgrading to 0.57.0-rc.0:

> react-native run-android
Scanning folders for symlinks in C:\Users\Gary\Documents\code\WonderSwipe\node_modules (29ms)
(node:21456) UnhandledPromiseRejectionWarning: Error: Cannot find module 'metro/src/blacklist'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (C:\Users\Gary\Documents\code\WonderSwipe\rn-cli.config.js:3:19)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Module._compile (C:\Users\Gary\Documents\code\WonderSwipe\node_modules\pirates\lib\index.js:83:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Object.newLoader [as .js] (C:\Users\Gary\Documents\code\WonderSwipe\node_modules\pirates\lib\index.js:88:7)
    at Module.load (internal/modules/cjs/loader.js:599:32)
(node:21456) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:21456) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

npm start hits the same error.

@public

Summary: @public This diff fixes the `projectRoot` calculation on React Native when the app does not have a config file. This should fix the issues reported in #20712 Reviewed By: hramos Differential Revision: D9444982 fbshipit-source-id: 4cb41fa5224d2addf92976cc119e49dea6a6346b

@public

Summary: @public This diff fixes the `projectRoot` calculation on React Native when the app does not have a config file. This should fix the issues reported in #20712 Reviewed By: hramos Differential Revision: D9444982 fbshipit-source-id: 4cb41fa5224d2addf92976cc119e49dea6a6346b

kelset · 2018-08-23T08:36:40Z

Looks like @rafeca committed a fix for this, we have cherry picked it and will be out with rc3.

In the meantime, can anyone test if master is now fixed?

zenz · 2018-08-23T13:22:10Z

@kelset, It dosen't work I replace local-cli/util/Config.js with @rafeca's committed version, but same error appeared.

kelset · 2018-08-23T13:41:15Z

@zenz I just tested locally myself and I can confirm that Rafael's commit fixes the run-XXX command starting the packager correctly (no triple search or errors). Both on iOS and Android.

To test them you need to git clone the repo, checkout to the 0.57 branch and then run ./scripts/test-manual-e2e.sh.

Probably you didn't clean your project properly while testing? Anyway, I think we'll proceed soon to release a rc3 version so that we can make sure it works fine for everyone.

zenz · 2018-08-23T14:49:11Z

@kelset I did what you said, no luck. and .sh file is only workable under *nix, not windows.

gengjiawen · 2018-08-25T02:39:47Z

Fixed on rc3. I have verified using react-native init --version="0.57.0-rc.3" testRc3.

chakrihacker · 2018-08-25T05:33:22Z

I installed "0.57.0-rc.3" and I still have the error registerevents which is mentioned by @dmead

gengjiawen · 2018-08-25T06:51:08Z

Is it a clean install, or an upgraded project ?

chakrihacker · 2018-08-25T07:20:28Z

Clean install

gengjiawen · 2018-08-25T07:26:02Z

Can you provide a reproduce repo ?

dmead · 2018-08-25T11:25:44Z

Are you guys trying to repro on Windows?

…

On Sat, Aug 25, 2018, 3:27 AM Jiawen Geng ***@***.***> wrote: Can you provide an repro repo ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#20712 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKzMquBoabdSAfpWaTvpHd98Xatzt1Fks5uUPxQgaJpZM4WBaWZ> .

joe307bad · 2018-08-26T20:51:48Z

@dmead I am using Windows 10 and still have this issue with 0.57.0-rc.3

zenz · 2018-08-27T03:01:08Z

I confirmed that 0.57.rc3 solved the problem. under windows 10.

chakrihacker · 2018-08-27T07:02:56Z

@gengjiawen Here's the repo https://github.com/chakrihacker/testRc3 which I created with this react-native init --version="0.57.0-rc.3" testRc3

zenz · 2018-08-27T07:39:57Z

@chakrihacker I download your app and do react-native run-android, it's running well. I think you should check your system configuration.

chakrihacker · 2018-08-27T08:23:18Z

My react-native-cli version is 2.0.1 and I am using react-native for past 6 months and my latest is on 0.55.4, what system configuration should I check?

I have the same error what @timri had

zenz · 2018-08-27T10:56:39Z

@chakrihacker did you use yarn for package management? or npm? which version?
I'm using yarn 1.7.0, and updating android build-tools to 27.0.3 and platform27.

chakrihacker · 2018-08-27T11:03:04Z

I'm using yarn 1.9.4 with same android build-tools and platform.

I am getting this error ::ffff:127.0.0.1 - - [27/Aug/2018:11:08:16 +0000] "GET /index.delta?platform=android&dev=true&minify=false&deltaBundleId=10e3175f5899423e HTTP/1.1" 200 - "-" "okhttp/3.10.0"

@public

Summary: @public This diff fixes the `projectRoot` calculation on React Native when the app does not have a config file. This should fix the issues reported in facebook#20712 Reviewed By: hramos Differential Revision: D9444982 fbshipit-source-id: 4cb41fa5224d2addf92976cc119e49dea6a6346b

Summary: add `packager.sh` for run-android task for unix like system. This only fix on linux and macOS. pass all current ci. none [GENERAL] [BUGFIX] [CLI] - add `packager.sh` back for run-android task Pull Request resolved: facebook#20751 Differential Revision: D9398197 Pulled By: hramos fbshipit-source-id: 213b066c0c034136c5ad5bbf8d45c6f331b1d185

@public

Summary: @public This diff fixes the `projectRoot` calculation on React Native when the app does not have a config file. This should fix the issues reported in facebook#20712 Reviewed By: hramos Differential Revision: D9444982 fbshipit-source-id: 4cb41fa5224d2addf92976cc119e49dea6a6346b

@public

Summary: @public This diff fixes the `projectRoot` calculation on React Native when the app does not have a config file. This should fix the issues reported in facebook#20712 Reviewed By: hramos Differential Revision: D9444982 fbshipit-source-id: 4cb41fa5224d2addf92976cc119e49dea6a6346b

joegoodall2 · 2018-09-20T11:03:13Z

@chakrihacker Did you get this resolved?
#20712 (comment)

chakrihacker · 2018-09-20T14:42:41Z

It's working, you can close this issue

Summary: add `packager.sh` for run-android task for unix like system. This only fix on linux and macOS. pass all current ci. none [GENERAL] [BUGFIX] [CLI] - add `packager.sh` back for run-android task Pull Request resolved: facebook#20751 Differential Revision: D9398197 Pulled By: hramos fbshipit-source-id: 213b066c0c034136c5ad5bbf8d45c6f331b1d185

kelset added Platform: Windows Building on Windows. Impact: Regression Describes a behavior that used to work on a prior release, but stopped working recently. Tech: Bundler 📦 This issue is related to the bundler (Metro, Haul, etc) used. labels Aug 17, 2018

This comment has been minimized.

Sign in to view

kelset mentioned this issue Aug 20, 2018

0.57.0 Discussion react-native-community/releases#34

Closed

facebook-github-bot closed this as completed in a84785c Aug 20, 2018

gengjiawen reopened this Aug 20, 2018

kelset removed the Platform: Windows Building on Windows. label Aug 21, 2018

ngraef mentioned this issue Aug 22, 2018

[0.57.0-rc.0] react-native-git-upgrade and old school upgrade are broken #20710

Closed

gengjiawen closed this as completed Aug 25, 2018

mgcrea mentioned this issue Sep 13, 2018

[0.57] _this._registerEvents is not a function on a clean project #21094

Closed

3 tasks

facebook locked as resolved and limited conversation to collaborators Sep 20, 2018

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 25, 2019

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

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

Comments

ExoMemphiz commented Aug 17, 2018 • edited Loading

Environment

Description

Reproducible Demo

gengjiawen commented Aug 17, 2018

gengjiawen commented Aug 17, 2018

kelset commented Aug 17, 2018 • edited Loading

gengjiawen commented Aug 17, 2018

gengjiawen commented Aug 17, 2018

timri commented Aug 17, 2018

timri commented Aug 17, 2018

kelset commented Aug 17, 2018

ferily7 commented Aug 17, 2018 • edited Loading

sharathk commented Aug 18, 2018

This comment has been minimized.

kelset commented Aug 18, 2018

This comment has been minimized.

gengjiawen commented Aug 19, 2018

This comment has been minimized.

kelset commented Aug 20, 2018

gengjiawen commented Aug 20, 2018

gengjiawen commented Aug 20, 2018

gengjiawen commented Aug 20, 2018 • edited Loading

gengjiawen commented Aug 20, 2018 • edited Loading

dmead commented Aug 22, 2018

fungilation commented Aug 22, 2018

kelset commented Aug 23, 2018

zenz commented Aug 23, 2018

kelset commented Aug 23, 2018 • edited Loading

zenz commented Aug 23, 2018

gengjiawen commented Aug 25, 2018

chakrihacker commented Aug 25, 2018

gengjiawen commented Aug 25, 2018

chakrihacker commented Aug 25, 2018

gengjiawen commented Aug 25, 2018 • edited Loading

dmead commented Aug 25, 2018 via email

joe307bad commented Aug 26, 2018

zenz commented Aug 27, 2018

chakrihacker commented Aug 27, 2018

zenz commented Aug 27, 2018

chakrihacker commented Aug 27, 2018 • edited Loading

zenz commented Aug 27, 2018

chakrihacker commented Aug 27, 2018 • edited Loading

joegoodall2 commented Sep 20, 2018

chakrihacker commented Sep 20, 2018

ExoMemphiz commented Aug 17, 2018 •

edited

Loading

kelset commented Aug 17, 2018 •

edited

Loading

ferily7 commented Aug 17, 2018 •

edited

Loading

gengjiawen commented Aug 20, 2018 •

edited

Loading

gengjiawen commented Aug 20, 2018 •

edited

Loading

kelset commented Aug 23, 2018 •

edited

Loading

gengjiawen commented Aug 25, 2018 •

edited

Loading

chakrihacker commented Aug 27, 2018 •

edited

Loading

chakrihacker commented Aug 27, 2018 •

edited

Loading