create-react-app fails with "404 Not Found" on ieee754

Created on 10 Oct 2018  路  5Comments  路  Source: facebook/create-react-app

Consistently getting the following install failure when attempting to create a react app. This error occurs when using yarn, npx, or npm

$ yarn create react-app react-app-test
yarn create v1.10.1
[1/4] 馃攳 Resolving packages...
[2/4] 馃殮 Fetching packages...
[3/4] 馃敆 Linking dependencies...
[4/4] 馃搩 Building fresh packages...
success Installed "[email protected]" with binaries:
- create-react-app
[##################################################################-] 66/67
Creating a new React app in /Users/mlone/code/node/react_pg/learning-react/react-app-test.

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

yarn add v1.10.1
[1/4] 馃攳 Resolving packages...
[2/4] 馃殮 Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@xtuc/ieee754/-/ieee754-1.2.0.tgz: Request failed "404 Not Found"".
info If you think this is a bug, please open a bug report with the information provided in "/Users/mlone/code/node/react_pg/learning-react/react-app-test/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Aborting installation.
yarnpkg add --exact react react-dom react-scripts --cwd /Users/mlone/code/node/react_pg/learning-react/react-app-test has failed.

Deleting generated file... package.json
Deleting generated file... yarn.lock
Done.
error Command failed.
Exit code: 1
Command: /usr/local/bin/create-react-app
Arguments: react-app-test
Directory: /Users/mlone/code/node/react_pg/learning-react
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.

Most helpful comment

Thank you. You pointed me in the right direction. We have an internal .npmrc with specific settings causing the 404s. Updating it per our documentation corrected the issue.

All 5 comments

We can clearly see that package @xtuc/ieee754 exists. You can even follow the link with tgz from the error.
I believe it is a temporary error either with your network or package registry.

Thank you. You pointed me in the right direction. We have an internal .npmrc with specific settings causing the 404s. Updating it per our documentation corrected the issue.

Same error with ie754-1.2.0 404 not found. After removing .npmrc it could successfully install

my .npmrc only contained

_auth=<TOKEN>
email=<EMAIL>
//registry.npmjs.org/:_authToken=<TOKEN>

:/

Had the same issue, it was the _auth field causing ours, but we use npm, we had to downgrade our webpack to not have this problem. We needed _auth to use our nexus registry for npm modules, we have a ton of other npm dependencies that do fine with the _auth token being in the npmrc, maybe it's getting criss-crossed with an _auth key value pair in xutc's registry? This is an issue with that webpack dependency best I can tell.

I had the same issue. We have a private npm registry too which needs authentication. for me removing auth for the private registry resolved the issue, but this way I cannot use both registries...

Was this page helpful?
0 / 5 - 0 ratings

Related issues

akctba picture akctba  路  80Comments

gabrielmicko picture gabrielmicko  路  70Comments

benneq picture benneq  路  99Comments

razvan-soare picture razvan-soare  路  161Comments

gaearon picture gaearon  路  85Comments