Installing fail

[zjoin]

I installing create-react-app my-app --scripts-version custom-react-scripts, but it's fail

How to fix it?

[andrewhl]

I just came here to post the same issue. +1

[andrewhl]

Running:

`npm install --save-dev --save-exact custom-react-scripts` failed

inside the project folder gives me:

npm ERR! Darwin 15.5.0
npm ERR! argv "/Users/andrew/.nvm/versions/node/v6.6.0/bin/node" "/Users/andrew/.nvm/versions/node/v6.6.0/bin/npm" "install" "--save-dev" "--save-exact" "custom-react-scripts"
npm ERR! node v6.6.0
npm ERR! npm  v3.10.3

npm ERR! Path must be a string. Received undefined
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/andrew/code/ideas/npm-debug.log

[jbach]

@kitze suggested downgrading to Node 6.2.0, which ought to fix the problem. I think it might also be a problem with npm 3.10.3 (introduced with node 6.3.0) rather than node itself, as using npm@3.8.3 on Node 6.7.0 works for me.

It also seems like this is only an issue with custom-react-scripts and not with the regular react-scripts? @kitze, maybe merging recent changes from facebookincubator/create-react-app to your fork would fix things?

Edit: It works with npm@3.9.5 on Node 6.7.0 as well (which was introduced with node 6.2.2), could it be npm@3.10.3 that’s causing troubles? It also works with npm@3.9.6 and breaks with npm@3.10.0. So that confirms it’s an issue with npm rather than node.

[schabluk]

Same here. Node v6.7.0, npm 3.10.8.

[claylevering]

+1 to this and not really interested in downgrading my Node / NPM (or using alternatives with nvm).

[kitze]

@jbach I just merged all the changes from the original create-react-app repo. I also merged few PRs and released version 0.0.15 on npm. I'm still getting the error. I'm investigating what can be the issue...

[andrewhl]

Godspeed, my friend. I really want to use this library, but this failure is preventing me from even getting off the ground.

[spion]

Sounds like an issue with bundledDependencies being "fixed" (but not fully) in latest npm: https://github.com/npm/npm/blob/b38573fae383aaaeaec0548c2ae616778a3b5dab/CHANGELOG.md#erk

Specifically in this case it has problems when trying to normalize the path of babel-preset-es2015 which is a bundled dependency included by babel-preset-react-app. (I added some logging to find the module that causes the error)

My guess is, if you remove stage-0 (or some other module thats causing the conflict, though not sure which one!) from the bundled dependencies list, it will work. I'm assuming its stage-0 because the react-app preset already includes some of those, and that conflict causes the bundle to become "deeper" (in terms of nested node_modules), but I can't be certain.

edit: Actually tested, and removing stage-0 from bundled dependencies does seem to work.

[kitze]

@spion thank you! I'll test it and push a fix asap.

[kitze]

@spion the problem is that bundledDependencies get generated from the release.sh script:

# This modifies $clean_path/package.json to copy all dependencies to bundledDependencies
node ./node_modules/.bin/bundle-deps

[raygesualdo]

Just tried to give custom-react-scripts a shot today and ran into this install issue. Any quick fixes or hacks to get it working?

[claylevering]

@raygesualdo I'v gotten around it by temporarily using npm@3.9.5 - npm i -g npm@3.9.5