"create-react-app hello-world" fails on Vagrant Ubuntu 12.04 #1693

tgig · 2017-03-02T00:51:00Z

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.

Can you reproduce the problem with latest npm?

I am using npm version 4.3.0

Description

I can't use create-react-app hello-world on Vagrant Ubuntu . It fails with the error "Aborting installation", then deletes the files it previously installed.

Actual behavior

root@precise64:/code/React# create-react-app hello-world
Creating a new React app in /code/React/hello-world.

Installing packages. This might take a couple minutes.
Installing react, react-dom, and react-scripts...

npm WARN prefer global marked@0.3.6 should be installed with -g
hello-world@0.1.0 /code/React/hello-world
+-- react@15.4.2
| +-- fbjs@0.8.9
| | +-- core-js@1.2.7
| | +-- isomorphic-fetch@2.2.1
| | | `-- node-fetch@1.6.3
| | |   +-- encoding@0.1.12
...
...
| +-- stream-cache@0.0.2
  | `-- webpack-dev-middleware@1.10.1
  |   +-- memory-fs@0.4.1
  |   `-- mime@1.3.4
  +-- webpack-manifest-plugin@1.1.0
  `-- whatwg-fetch@2.0.2

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.17 (node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

Aborting installation.

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting hello-world/ from /code/React
Done.

Environment

Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected):

/code/React
`-- (empty)

node -v: 6.9.1
npm -v: 4.3.0

Then, specify:

Operating system: Vagrant virtual machine running Ubuntu 12.04 LTS
Browser and version: n/a

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

gaearon · 2017-03-02T00:58:25Z

Can you please find which create-react-app and then edit the script to replace

      if (reason.command) {
        console.log('  ' + chalk.cyan(reason.command), 'has failed.')
      }

here with this:

      if (reason.command) {
        console.log('  ' + chalk.cyan(reason.command), 'has failed.')
      } else {
        console.log(chalk.red('  Unexpected error. Please report it as a bug:'));
        console.log(reason);
      }

and then try again and paste the output here? (I’d also appreciate a PR adding this diagnostic code to the tool, we should’ve done this before releasing.)

tgig · 2017-03-02T01:28:33Z

Thanks for the super fast response.

Created the PR and here is the output:


Aborting installation.
  Unexpected error. Please report it as a bug:
/code/react/hello-world/node_modules/graceful-fs/graceful-fs.js:58
�$
^
SyntaxError: Invalid or unexpected token
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/code/react/hello-world/node_modules/fs-extra/lib/index.js:4:11)
    at Module._compile (module.js:570:32)

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting hello-world/ from /code/react
Done.

gaearon · 2017-03-02T01:33:06Z

This is kinda weird:

/code/react/hello-world/node_modules/graceful-fs/graceful-fs.js:58
�$

Can you show the contents of this file around this line?

tgig · 2017-03-02T01:47:34Z

Nothing looks out of place on the surface of it. Same as other copies of this library on my computer. This is what I'm seeing:

vim /usr/lib/node_modules/create-react-app/node_modules/graceful-fs/graceful-fs.js

function patch (fs) {
  // Everything that references the open() function needs to be in here
  polyfills(fs) //THIS IS LINE 58
  fs.gracefulify = patch
  fs.FileReadStream = ReadStream;  // Legacy name.
  fs.FileWriteStream = WriteStream;  // Legacy name.

gaearon · 2017-03-02T01:48:44Z

Why did it point to /code/react/hello-world/ in the original stack trace?
Can you check there too?

tgig · 2017-03-02T01:49:22Z

I would love to check there, but the program deletes the files in the cleanup process as it is aborting.

gaearon · 2017-03-02T01:49:28Z

Oh well, you obviously can’t, it was deleted 😄
Can you comment the deletion out?

tgig · 2017-03-02T01:49:48Z

Sure, I'll give it a shot

gaearon · 2017-03-02T01:50:19Z

Should be a matter of commenting this section.

tgig · 2017-03-02T02:11:04Z

Interesting!

The hello-world/node_modules/graceful-fs/graceful-fs.js file is definitely not happy. I can't seem to copy/paste the corrupted text. It looks different in vim and Sublime Text. Screenshots instead:

vim

Sublime

gaearon · 2017-03-02T02:12:38Z

Can you install npm i -g npm@3.10.9 and try again? Maybe some weird bug in 4.x.

tgig · 2017-03-02T02:21:12Z

No love. I actually had a previous version of npm and upgraded to the latest before submitting this bug. I did go back to 3.10.9 and still get an error.

Not sure if this is relevant, since the deleting code is still commented, but I'm getting a different error (but similar corruption) now:

Aborting installation.
  Unexpected error. Please report it as a bug:
/code/react/hello-world/node_modules/react-scripts/scripts/init.js:47
  } else {

SyntaxError: Invalid or unexpected token
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at /usr/lib/node_modules/create-react-app/index.js:235:18
    at process._tickCallback (internal/process/next_tick.js:103:7)

Done.

gaearon · 2017-03-02T02:21:51Z

Are you behind a proxy, or using a non-standard npm registry by any chance?

tgig · 2017-03-02T02:22:44Z

No, sorry, neither of those things.

gaearon · 2017-03-02T02:24:06Z

Can you run npm ls graceful-fs in that folder, check the version, and then run npm install graceful-fs@x.y.z (your version) in another separate folder to verify this is reproducible with npm alone?

tgig · 2017-03-02T02:32:30Z

Not exactly sure what you're looking for, so may be doing this wrong, but:

root@precise64:/code/react/hello-world# npm ls graceful-fs
hello-world@0.1.0 /code/react/hello-world
`-- react-scripts@0.9.3
  `-- fs-extra@0.30.0
    `-- graceful-fs@4.1.11

Then:

root@precise64:/code/react/tempdir# npm install graceful-fs@4.1.11
/code/react/tempdir
`-- graceful-fs@4.1.11

npm WARN enoent ENOENT: no such file or directory, open '/code/react/tempdir/package.json'
npm WARN tempdir No description
npm WARN tempdir No repository field.
npm WARN tempdir No README data
npm WARN tempdir No license field.

No apparent corruption in the file:

gaearon · 2017-03-02T02:32:37Z

While I empathize with your problem, those screenshots are beautiful in a way.

gaearon · 2017-03-02T02:33:35Z

Thanks, this is even more interesting.
Let's try this in a separate folder now: npm install react-scripts@0.9.3.

tgig · 2017-03-02T02:38:09Z

Seems to have completed successfully:

root@precise64:/code/react/tempdir2# npm i --save react-scripts@0.9.3
npm WARN saveError ENOENT: no such file or directory, open '/code/react/tempdir2/package.json'
/code/react/tempdir2
`-- react-scripts@0.9.3
  +-- autoprefixer@6.7.2
  | +-- browserslist@1.7.5
  | | `-- electron-to-chromium@1.2.4
  | +-- caniuse-db@1.0.30000631
  | +-- normalize-range@0.1.2
  | +-- num2fraction@1.2.2
  | +-- postcss@5.2.15
  | | `-- js-base64@2.1.9
  | `-- postcss-value-parser@3.3.0
  +-- babel-core@6.22.1
  | +-- babel-code-frame@6.22.0
...
...
  | | `-- uuid@2.0.3
  | +-- sockjs-client@1.1.2
  | | `-- faye-websocket@0.11.1
  | +-- stream-cache@0.0.2
  | `-- webpack-dev-middleware@1.10.1
  |   +-- memory-fs@0.4.1
  |   `-- mime@1.3.4
  +-- webpack-manifest-plugin@1.1.0
  `-- whatwg-fetch@2.0.2

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.17 (node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open '/code/react/tempdir2/package.json'
npm WARN tempdir2 No description
npm WARN tempdir2 No repository field.
npm WARN tempdir2 No README data
npm WARN tempdir2 No license field.
root@precise64:/code/react/tempdir2# ls
node_modules

gaearon · 2017-03-02T02:41:38Z

Does /code/react/tempdir2/node_modules/graceful-fs/graceful-fs.js look normal?

adamdicarlo · 2017-03-02T02:42:38Z

@tgig What kind of network adapter are you using?

adamdicarlo · 2017-03-02T02:44:31Z

I've seen my Anker USB 3 -> Ethernet adapter (part of a USB 3 hub) corrupt data. Seems to happen when the machine has slept and reawoken. (I've seen this happen on macOS; not sure if you're directly in Linux or in a VM/container...)

gaearon · 2017-03-02T02:46:41Z

I don’t know what’s causing this, but it’s clearly some sort of data corruption. Whether it happens on the disk, or during fetching, I can’t tell.

tgig · 2017-03-02T02:46:47Z

Yes, the file in tempdir2 looks completely normal.

And, I'm on a Macbook Pro, running Vagrant virtual machines, with a wireless connection. I've never seen this kind of behavior before...

root@precise64:/code/react/tempdir2# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:0d.0 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 02)

tgig · 2017-03-02T02:48:35Z

I'll try the good 'ol remove everything, reboot, reinstall, reboot, try again method and see if that makes any difference.

Thanks a lot for your help, could not have gotten nearly this far w/o you.

Will get back soon.

gaearon · 2017-03-02T02:50:42Z

I’d also suggest installing Yarn. CRA will use it automatically if it’s installed on the system. Not saying Yarn would fix it, but would give us another data point.

tgig · 2017-03-02T03:33:15Z

Hey, it worked! Not sure if it was the uninstall/reinstall, or having Yarn do the magic. But... here we go.

Unfortunately, now experiencing another weird issue:

I'm running this inside of a Vagrant box. When I edit the file in my Sublime Text editor from my local machine, the development server does not recognize the change, and does not re-load the files. When I use vim inside the vagrant machine, everything works as expected.

I'm happy to research this on my own or open a new issue. Maybe it's an easy fix and you can point me in the right direction?

gaearon · 2017-03-02T03:40:59Z

When I edit the file in my Sublime Text editor from my local machine, the development server does not recognize the change, and does not re-load the files.

Can you try creating an .env file in the project root and adding CHOKIDAR_USEPOLLING=true to it? Then restart the server.

tgig · 2017-03-02T06:07:33Z

Worked. Thanks again! I'm good to go.

gaearon added the issue: bug label Mar 2, 2017

tgig mentioned this issue Mar 2, 2017

Diagnostic code #1695

Merged

gaearon removed the issue: bug label Mar 2, 2017

tgig closed this as completed Mar 2, 2017

gaearon mentioned this issue Mar 6, 2017

Aborting installation. npm install --save --save-exact react react-dom react-scripts has failed. #1735

Closed

lock bot locked and limited conversation to collaborators Jan 22, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"create-react-app hello-world" fails on Vagrant Ubuntu 12.04 #1693

"create-react-app hello-world" fails on Vagrant Ubuntu 12.04 #1693

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017 •

edited

Loading

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

gaearon commented Mar 2, 2017 •

edited

Loading

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

adamdicarlo commented Mar 2, 2017

adamdicarlo commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

"create-react-app hello-world" fails on Vagrant Ubuntu 12.04 #1693

"create-react-app hello-world" fails on Vagrant Ubuntu 12.04 #1693

Comments

tgig commented Mar 2, 2017

Can you reproduce the problem with latest npm?

Description

Actual behavior

Environment

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017 • edited Loading

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

gaearon commented Mar 2, 2017 • edited Loading

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

adamdicarlo commented Mar 2, 2017

adamdicarlo commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017

tgig commented Mar 2, 2017

gaearon commented Mar 2, 2017 •

edited

Loading

gaearon commented Mar 2, 2017 •

edited

Loading