question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

create-react-app fails

See original GitHub issue

npm version: 6.9.0

I read the troubleshooting page (https://facebook.github.io/create-react-app/docs/troubleshooting) and saw nothing of relevance.

Environment

I am running on Windows 10, with node version 10.15.3, npm version 6.9.0, and create-react-app version 3.0.1. The environment says it does not find create-react-app even though it is definitely installed globally. I just updated it with “npm install -g npm@latest” to be absolutely sure.

Environment Info:

System: OS: Windows 10 CPU: (12) x64 Intel® Core™ i7-5820K CPU @ 3.30GHz Binaries: Node: 10.15.3 - C:\Program Files\nodejs\node.EXE Yarn: Not Found npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: 42.17134.1.0 Internet Explorer: 11.0.17134.1 npmPackages: react: Not Found react-dom: Not Found react-scripts: Not Found npmGlobalPackages: create-react-app: Not Found

Steps to Reproduce

Just try to create a react app with create-react-app: “npx create-react-app syn-mgr”

  1. I ran the command to create a new react app.
  2. create-react-app fails every single time.

Expected Behavior

I anticipated the app would be created, and I would be writing code right now.

Actual Behavior

The create failed. Following is the log file. The only oddity with my system is that I am in a rural area with dreadfully slow 3.0 Megabit DSL. (There is nothing faster available here.) Some systems misinterpret this slow connection to be timing out when, in reality, it is just God-awful slow–but still functioning properly.

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\Anthony\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   '--save',
1 verbose cli   '--save-exact',
1 verbose cli   '--loglevel',
1 verbose cli   'error',
1 verbose cli   'react',
1 verbose cli   'react-dom',
1 verbose cli   'react-scripts' ]
2 info using npm@6.9.0
3 info using node@v10.15.3
4 verbose npm-session 1a6738c28c990ad5
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 304 https://registry.npmjs.org/react-scripts 288ms (from cache)
8 silly pacote tag manifest for react-scripts@latest fetched in 301ms
9 http fetch GET 304 https://registry.npmjs.org/react 311ms (from cache)
10 silly pacote tag manifest for react@latest fetched in 332ms
11 http fetch GET 304 https://registry.npmjs.org/react-dom 324ms (from cache)
12 silly pacote tag manifest for react-dom@latest fetched in 333ms
13 timing stage:loadCurrentTree Completed in 378ms
14 silly install loadIdealTree
15 silly install cloneCurrentTreeToIdealTree
16 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
17 silly install loadShrinkwrap
18 timing stage:loadIdealTree:loadShrinkwrap Completed in 0ms
19 silly install loadAllDepsIntoIdealTree
20 silly resolveWithNewModule react-scripts@3.0.1 checking installable status
21 silly resolveWithNewModule react@16.8.6 checking installable status
22 silly resolveWithNewModule react-dom@16.8.6 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/prop-types 81ms (from cache)
24 silly pacote range manifest for prop-types@^15.6.2 fetched in 87ms
25 silly resolveWithNewModule prop-types@15.7.2 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/object-assign 88ms (from cache)
27 silly pacote range manifest for object-assign@^4.1.1 fetched in 94ms
28 silly resolveWithNewModule object-assign@4.1.1 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/scheduler 101ms (from cache)
30 silly pacote range manifest for scheduler@^0.13.6 fetched in 108ms
31 silly resolveWithNewModule scheduler@0.13.6 checking installable status
32 http fetch GET 304 https://registry.npmjs.org/loose-envify 199ms (from cache)
33 silly pacote range manifest for loose-envify@^1.1.0 fetched in 206ms
34 silly resolveWithNewModule loose-envify@1.4.0 checking installable status
35 http fetch GET 304 https://registry.npmjs.org/js-tokens 69ms (from cache)
36 silly pacote range manifest for js-tokens@^3.0.0 || ^4.0.0 fetched in 75ms
37 silly resolveWithNewModule js-tokens@4.0.0 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/react-is 69ms (from cache)
39 silly pacote range manifest for react-is@^16.8.1 fetched in 76ms
40 silly resolveWithNewModule react-is@16.8.6 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/@babel%2fcore 84ms (from cache)
42 silly pacote version manifest for @babel/core@7.4.3 fetched in 91ms
43 silly resolveWithNewModule @babel/core@7.4.3 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/case-sensitive-paths-webpack-plugin 82ms (from cache)
45 silly pacote version manifest for case-sensitive-paths-webpack-plugin@2.2.0 fetched in 88ms
46 silly resolveWithNewModule case-sensitive-paths-webpack-plugin@2.2.0 checking installable status
47 http fetch GET 304 https://registry.npmjs.org/@typescript-eslint%2feslint-plugin 204ms (from cache)
48 silly fetchPackageMetaData error for @typescript-eslint/eslint-plugin@1.6.0 Unexpected end of JSON input while parsing near '...\r\n"},"engines":{"no'
49 http fetch GET 304 https://registry.npmjs.org/@svgr%2fwebpack 248ms (from cache)
50 silly pacote version manifest for @svgr/webpack@4.1.0 fetched in 255ms
51 silly resolveWithNewModule @svgr/webpack@4.1.0 checking installable status
52 http fetch GET 304 https://registry.npmjs.org/@typescript-eslint%2fparser 260ms (from cache)
53 silly pacote version manifest for @typescript-eslint/parser@1.6.0 fetched in 280ms
54 silly resolveWithNewModule @typescript-eslint/parser@1.6.0 checking installable status
55 http fetch GET 304 https://registry.npmjs.org/babel-jest 290ms (from cache)
56 http fetch GET 304 https://registry.npmjs.org/babel-loader 297ms (from cache)
57 silly pacote range manifest for babel-jest@^24.8.0 fetched in 298ms
58 silly resolveWithNewModule babel-jest@24.8.0 checking installable status
59 silly pacote version manifest for babel-loader@8.0.5 fetched in 303ms
60 silly resolveWithNewModule babel-loader@8.0.5 checking installable status
61 http fetch GET 304 https://registry.npmjs.org/css-loader 134ms (from cache)
62 silly pacote version manifest for css-loader@2.1.1 fetched in 141ms
63 silly resolveWithNewModule css-loader@2.1.1 checking installable status
64 http fetch GET 304 https://registry.npmjs.org/babel-plugin-named-asset-import 321ms (from cache)
65 silly pacote range manifest for babel-plugin-named-asset-import@^0.3.2 fetched in 326ms
66 silly resolveWithNewModule babel-plugin-named-asset-import@0.3.2 checking installable status
67 http fetch GET 304 https://registry.npmjs.org/babel-eslint 341ms (from cache)
68 silly pacote version manifest for babel-eslint@10.0.1 fetched in 348ms
69 silly resolveWithNewModule babel-eslint@10.0.1 checking installable status
70 http fetch GET 304 https://registry.npmjs.org/dotenv 145ms (from cache)
71 silly pacote version manifest for dotenv@6.2.0 fetched in 151ms
72 silly resolveWithNewModule dotenv@6.2.0 checking installable status
73 http fetch GET 304 https://registry.npmjs.org/camelcase 369ms (from cache)
74 silly pacote range manifest for camelcase@^5.2.0 fetched in 375ms
75 silly resolveWithNewModule camelcase@5.3.1 checking installable status
76 http fetch GET 304 https://registry.npmjs.org/babel-preset-react-app 386ms (from cache)
77 silly pacote range manifest for babel-preset-react-app@^9.0.0 fetched in 394ms
78 silly resolveWithNewModule babel-preset-react-app@9.0.0 checking installable status
79 http fetch GET 304 https://registry.npmjs.org/dotenv-expand 146ms (from cache)
80 silly pacote version manifest for dotenv-expand@4.2.0 fetched in 152ms
81 silly resolveWithNewModule dotenv-expand@4.2.0 checking installable status
82 http fetch GET 304 https://registry.npmjs.org/eslint 138ms (from cache)
83 silly fetchPackageMetaData error for eslint@^5.16.0 Unexpected end of JSON input while parsing near '...:"~0.2.0","user-home"'
84 http fetch GET 304 https://registry.npmjs.org/eslint-config-react-app 137ms (from cache)
85 silly pacote range manifest for eslint-config-react-app@^4.0.1 fetched in 143ms
86 silly resolveWithNewModule eslint-config-react-app@4.0.1 checking installable status
87 http fetch GET 304 https://registry.npmjs.org/eslint-loader 145ms (from cache)
88 silly pacote version manifest for eslint-loader@2.1.2 fetched in 151ms
89 silly resolveWithNewModule eslint-loader@2.1.2 checking installable status
90 http fetch GET 304 https://registry.npmjs.org/eslint-plugin-flowtype 151ms (from cache)
91 silly pacote version manifest for eslint-plugin-flowtype@2.50.1 fetched in 160ms
92 silly resolveWithNewModule eslint-plugin-flowtype@2.50.1 checking installable status
93 http fetch GET 304 https://registry.npmjs.org/eslint-plugin-import 154ms (from cache)
94 silly pacote version manifest for eslint-plugin-import@2.16.0 fetched in 161ms
95 silly resolveWithNewModule eslint-plugin-import@2.16.0 checking installable status
96 http fetch GET 304 https://registry.npmjs.org/eslint-plugin-jsx-a11y 148ms (from cache)
97 silly pacote version manifest for eslint-plugin-jsx-a11y@6.2.1 fetched in 155ms
98 silly resolveWithNewModule eslint-plugin-jsx-a11y@6.2.1 checking installable status
99 http fetch GET 304 https://registry.npmjs.org/eslint-plugin-react 156ms (from cache)
100 silly pacote version manifest for eslint-plugin-react@7.12.4 fetched in 163ms
101 silly resolveWithNewModule eslint-plugin-react@7.12.4 checking installable status
102 http fetch GET 304 https://registry.npmjs.org/eslint-plugin-react-hooks 151ms (from cache)
103 silly pacote range manifest for eslint-plugin-react-hooks@^1.5.0 fetched in 158ms
104 silly resolveWithNewModule eslint-plugin-react-hooks@1.6.0 checking installable status
105 http fetch GET 304 https://registry.npmjs.org/file-loader 155ms (from cache)
106 http fetch GET 304 https://registry.npmjs.org/fs-extra 148ms (from cache)
107 silly pacote version manifest for file-loader@3.0.1 fetched in 162ms
108 silly resolveWithNewModule file-loader@3.0.1 checking installable status
109 silly pacote version manifest for fs-extra@7.0.1 fetched in 155ms
110 silly resolveWithNewModule fs-extra@7.0.1 checking installable status
111 http fetch GET 304 https://registry.npmjs.org/identity-obj-proxy 138ms (from cache)
112 http fetch GET 304 https://registry.npmjs.org/html-webpack-plugin 162ms (from cache)
113 silly pacote version manifest for identity-obj-proxy@3.0.0 fetched in 146ms
114 silly resolveWithNewModule identity-obj-proxy@3.0.0 checking installable status
115 silly pacote version manifest for html-webpack-plugin@4.0.0-beta.5 fetched in 171ms
116 silly resolveWithNewModule html-webpack-plugin@4.0.0-beta.5 checking installable status
117 http fetch GET 304 https://registry.npmjs.org/is-wsl 145ms (from cache)
118 silly pacote range manifest for is-wsl@^1.1.0 fetched in 151ms
119 silly resolveWithNewModule is-wsl@1.1.0 checking installable status
120 http fetch GET 304 https://registry.npmjs.org/jest 137ms (from cache)
121 silly pacote version manifest for jest@24.7.1 fetched in 146ms
122 silly resolveWithNewModule jest@24.7.1 checking installable status
123 http fetch GET 304 https://registry.npmjs.org/jest-environment-jsdom-fourteen 139ms (from cache)
124 silly pacote version manifest for jest-environment-jsdom-fourteen@0.1.0 fetched in 145ms
125 silly resolveWithNewModule jest-environment-jsdom-fourteen@0.1.0 checking installable status
126 http fetch GET 304 https://registry.npmjs.org/jest-resolve 145ms (from cache)
127 silly pacote version manifest for jest-resolve@24.7.1 fetched in 153ms
128 silly resolveWithNewModule jest-resolve@24.7.1 checking installable status
129 http fetch GET 304 https://registry.npmjs.org/jest-watch-typeahead 140ms (from cache)
130 silly pacote version manifest for jest-watch-typeahead@0.3.0 fetched in 148ms
131 silly resolveWithNewModule jest-watch-typeahead@0.3.0 checking installable status
132 http fetch GET 304 https://registry.npmjs.org/mini-css-extract-plugin 141ms (from cache)
133 silly pacote version manifest for mini-css-extract-plugin@0.5.0 fetched in 148ms
134 silly resolveWithNewModule mini-css-extract-plugin@0.5.0 checking installable status
135 http fetch GET 304 https://registry.npmjs.org/optimize-css-assets-webpack-plugin 136ms (from cache)
136 silly pacote version manifest for optimize-css-assets-webpack-plugin@5.0.1 fetched in 143ms
137 silly resolveWithNewModule optimize-css-assets-webpack-plugin@5.0.1 checking installable status
138 http fetch GET 304 https://registry.npmjs.org/pnp-webpack-plugin 150ms (from cache)
139 silly pacote version manifest for pnp-webpack-plugin@1.2.1 fetched in 158ms
140 silly resolveWithNewModule pnp-webpack-plugin@1.2.1 checking installable status
141 http fetch GET 304 https://registry.npmjs.org/postcss-flexbugs-fixes 136ms (from cache)
142 silly pacote version manifest for postcss-flexbugs-fixes@4.1.0 fetched in 142ms
143 silly resolveWithNewModule postcss-flexbugs-fixes@4.1.0 checking installable status
144 http fetch GET 304 https://registry.npmjs.org/postcss-loader 145ms (from cache)
145 silly pacote version manifest for postcss-loader@3.0.0 fetched in 151ms
146 silly resolveWithNewModule postcss-loader@3.0.0 checking installable status
147 http fetch GET 304 https://registry.npmjs.org/postcss-normalize 153ms (from cache)
148 silly pacote version manifest for postcss-normalize@7.0.1 fetched in 160ms
149 silly resolveWithNewModule postcss-normalize@7.0.1 checking installable status
150 http fetch GET 304 https://registry.npmjs.org/postcss-preset-env 144ms (from cache)
151 silly pacote version manifest for postcss-preset-env@6.6.0 fetched in 152ms
152 silly resolveWithNewModule postcss-preset-env@6.6.0 checking installable status
153 http fetch GET 304 https://registry.npmjs.org/react-dev-utils 147ms (from cache)
154 silly pacote range manifest for react-dev-utils@^9.0.1 fetched in 154ms
155 silly resolveWithNewModule react-dev-utils@9.0.1 checking installable status
156 http fetch GET 304 https://registry.npmjs.org/resolve 147ms (from cache)
157 silly pacote version manifest for resolve@1.10.0 fetched in 154ms
158 silly resolveWithNewModule resolve@1.10.0 checking installable status
159 http fetch GET 304 https://registry.npmjs.org/sass-loader 143ms (from cache)
160 silly pacote version manifest for sass-loader@7.1.0 fetched in 150ms
161 silly resolveWithNewModule sass-loader@7.1.0 checking installable status
162 http fetch GET 304 https://registry.npmjs.org/postcss-safe-parser 220ms (from cache)
163 silly pacote version manifest for postcss-safe-parser@4.0.1 fetched in 226ms
164 silly resolveWithNewModule postcss-safe-parser@4.0.1 checking installable status
165 http fetch GET 304 https://registry.npmjs.org/semver 147ms (from cache)
166 http fetch GET 304 https://registry.npmjs.org/react-app-polyfill 214ms (from cache)
167 silly pacote version manifest for semver@6.0.0 fetched in 153ms
168 silly resolveWithNewModule semver@6.0.0 checking installable status
169 silly pacote range manifest for react-app-polyfill@^1.0.1 fetched in 220ms
170 silly resolveWithNewModule react-app-polyfill@1.0.1 checking installable status
171 http fetch GET 304 https://registry.npmjs.org/style-loader 146ms (from cache)
172 silly pacote version manifest for style-loader@0.23.1 fetched in 151ms
173 silly resolveWithNewModule style-loader@0.23.1 checking installable status
174 http fetch GET 304 https://registry.npmjs.org/terser-webpack-plugin 145ms (from cache)
175 silly pacote version manifest for terser-webpack-plugin@1.2.3 fetched in 153ms
176 silly resolveWithNewModule terser-webpack-plugin@1.2.3 checking installable status
177 http fetch GET 304 https://registry.npmjs.org/ts-pnp 136ms (from cache)
178 silly pacote version manifest for ts-pnp@1.1.2 fetched in 141ms
179 silly resolveWithNewModule ts-pnp@1.1.2 checking installable status
180 http fetch GET 304 https://registry.npmjs.org/url-loader 137ms (from cache)
181 silly pacote version manifest for url-loader@1.1.2 fetched in 143ms
182 silly resolveWithNewModule url-loader@1.1.2 checking installable status
183 http fetch GET 304 https://registry.npmjs.org/webpack 116ms (from cache)
184 silly pacote version manifest for webpack@4.29.6 fetched in 132ms
185 silly resolveWithNewModule webpack@4.29.6 checking installable status
186 http fetch GET 304 https://registry.npmjs.org/webpack-dev-server 120ms (from cache)
187 silly pacote version manifest for webpack-dev-server@3.2.1 fetched in 130ms
188 silly resolveWithNewModule webpack-dev-server@3.2.1 checking installable status
189 http fetch GET 304 https://registry.npmjs.org/workbox-webpack-plugin 117ms (from cache)
190 silly pacote version manifest for workbox-webpack-plugin@4.2.0 fetched in 123ms
191 silly resolveWithNewModule workbox-webpack-plugin@4.2.0 checking installable status
192 http fetch GET 304 https://registry.npmjs.org/fsevents 126ms (from cache)
193 silly pacote version manifest for fsevents@2.0.6 fetched in 133ms
194 warn deprecated fsevents@2.0.6: Please update: there are crash fixes
195 silly resolveWithNewModule fsevents@2.0.6 checking installable status
196 http fetch GET 304 https://registry.npmjs.org/webpack-manifest-plugin 185ms (from cache)
197 silly pacote version manifest for webpack-manifest-plugin@2.0.4 fetched in 193ms
198 silly resolveWithNewModule webpack-manifest-plugin@2.0.4 checking installable status
199 timing stage:rollbackFailedOptional Completed in 0ms
200 timing stage:runTopLevelLifecycles Completed in 1817ms
201 silly saveTree syn-mgr@0.1.0
201 silly saveTree +-- react-dom@16.8.6
201 silly saveTree | +-- loose-envify@1.4.0
201 silly saveTree | | `-- js-tokens@4.0.0
201 silly saveTree | +-- object-assign@4.1.1
201 silly saveTree | +-- prop-types@15.7.2
201 silly saveTree | | `-- react-is@16.8.6
201 silly saveTree | `-- scheduler@0.13.6
201 silly saveTree +-- react-scripts@3.0.1
201 silly saveTree | +-- @babel/core@7.4.3
201 silly saveTree | | `-- resolve@1.10.0
201 silly saveTree | +-- @svgr/webpack@4.1.0
201 silly saveTree | +-- @typescript-eslint/parser@1.6.0
201 silly saveTree | +-- babel-eslint@10.0.1
201 silly saveTree | +-- babel-jest@24.8.0
201 silly saveTree | +-- babel-loader@8.0.5
201 silly saveTree | +-- babel-plugin-named-asset-import@0.3.2
201 silly saveTree | +-- babel-preset-react-app@9.0.0
201 silly saveTree | +-- camelcase@5.3.1
201 silly saveTree | +-- case-sensitive-paths-webpack-plugin@2.2.0
201 silly saveTree | +-- css-loader@2.1.1
201 silly saveTree | +-- dotenv-expand@4.2.0
201 silly saveTree | +-- dotenv@6.2.0
201 silly saveTree | +-- eslint-config-react-app@4.0.1
201 silly saveTree | +-- eslint-loader@2.1.2
201 silly saveTree | +-- eslint-plugin-flowtype@2.50.1
201 silly saveTree | +-- eslint-plugin-import@2.16.0
201 silly saveTree | +-- eslint-plugin-jsx-a11y@6.2.1
201 silly saveTree | +-- eslint-plugin-react-hooks@1.6.0
201 silly saveTree | +-- eslint-plugin-react@7.12.4
201 silly saveTree | +-- file-loader@3.0.1
201 silly saveTree | +-- fs-extra@7.0.1
201 silly saveTree | +-- fsevents@2.0.6
201 silly saveTree | +-- html-webpack-plugin@4.0.0-beta.5
201 silly saveTree | +-- identity-obj-proxy@3.0.0
201 silly saveTree | +-- is-wsl@1.1.0
201 silly saveTree | +-- jest-environment-jsdom-fourteen@0.1.0
201 silly saveTree | +-- jest-resolve@24.7.1
201 silly saveTree | +-- jest-watch-typeahead@0.3.0
201 silly saveTree | +-- jest@24.7.1
201 silly saveTree | +-- mini-css-extract-plugin@0.5.0
201 silly saveTree | +-- optimize-css-assets-webpack-plugin@5.0.1
201 silly saveTree | +-- pnp-webpack-plugin@1.2.1
201 silly saveTree | | `-- ts-pnp@1.1.2
201 silly saveTree | +-- postcss-flexbugs-fixes@4.1.0
201 silly saveTree | +-- postcss-loader@3.0.0
201 silly saveTree | +-- postcss-normalize@7.0.1
201 silly saveTree | +-- postcss-preset-env@6.6.0
201 silly saveTree | +-- postcss-safe-parser@4.0.1
201 silly saveTree | +-- react-app-polyfill@1.0.1
201 silly saveTree | +-- react-dev-utils@9.0.1
201 silly saveTree | +-- resolve@1.10.0
201 silly saveTree | +-- sass-loader@7.1.0
201 silly saveTree | +-- semver@6.0.0
201 silly saveTree | +-- style-loader@0.23.1
201 silly saveTree | +-- terser-webpack-plugin@1.2.3
201 silly saveTree | +-- ts-pnp@1.1.2
201 silly saveTree | +-- url-loader@1.1.2
201 silly saveTree | +-- webpack-dev-server@3.2.1
201 silly saveTree | +-- webpack-manifest-plugin@2.0.4
201 silly saveTree | +-- webpack@4.29.6
201 silly saveTree | `-- workbox-webpack-plugin@4.2.0
201 silly saveTree `-- react@16.8.6
202 verbose stack SyntaxError: Unexpected end of JSON input while parsing near '...\r\n"},"engines":{"no'
202 verbose stack     at JSON.parse (<anonymous>)
202 verbose stack     at parseJson (C:\Users\Anthony\AppData\Roaming\npm\node_modules\npm\node_modules\json-parse-better-errors\index.js:7:17)
202 verbose stack     at consumeBody.call.then.buffer (C:\Users\Anthony\AppData\Roaming\npm\node_modules\npm\node_modules\node-fetch-npm\src\body.js:96:50)
202 verbose stack     at process._tickCallback (internal/process/next_tick.js:68:7)
203 verbose cwd E:\Projects\CogniLogics\syn-mgr
204 verbose Windows_NT 10.0.17134
205 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Anthony\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save" "--save-exact" "--loglevel" "error" "react" "react-dom" "react-scripts"
206 verbose node v10.15.3
207 verbose npm  v6.9.0
208 error Unexpected end of JSON input while parsing near '...\r\n"},"engines":{"no'
209 verbose exit [ 1, true ]

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (1 by maintainers)

github_iconTop GitHub Comments

3reactions
cooervocommented, Jun 19, 2019

I also have this issue and cleaning the cache does nothing. It not working with v8 nor 10.16 😕

Update

Seems the problem is yarn force it to use npm:

 create-react-app myproject --use-npm
0reactions
stale[bot]commented, Aug 27, 2019

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

create-react-app Failing to create a new ... - Stack Overflow
This is due to the network issues try to download all dependency one by one or try to clean cache "npm cache clean...
Read more >
npx create-react-app fails · Issue #12559 - GitHub
Describe the bug Command npx create-react-app my-app fails to complete Environment Environment Info: current version of create-react-app: ...
Read more >
npx create-react-app not working? Here's the solution.
The current solution is simple — run create-react-app and target the latest version. Run creact-react-app using the latest version. npx create- ...
Read more >
What To Do if create-react-app Doesn't Work
1. npm uninstall -g create-react-app. This is the npm command to uninstall your global installation of create-react-app .
Read more >
create-react-app: command not found (React) error [Solved]
Use `npx` to solve the error create-react-app: command not found, e.g. `npx create-react-app my-app` or install the package globally by running `npm install ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found