create-react-app -- Installation Error / Please take a look into the debug.log

Created on 26 May 2019  路  6Comments  路  Source: facebook/create-react-app

Is this a bug report?

Yes

Did you try recovering your dependencies?

Yes

Which terms did you search for in User Guide?

create-react-app

Environment

Environment Info:

System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Binaries:
Node: 12.1.0 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.9.0 - C:\Program Files\nodejsnpm.CMD
Browsers:
Edge: 44.17763.1.0
Internet Explorer: Not Found
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found

Steps to Reproduce

  1. "npx create-react-app client" OR "npm i -g create-react-app --> create-react-app client"

Expected Behavior

Installation successful

Actual Behavior

C:\Users\Subho\Documents\GitHub\MERN_Stack_Development>npx create-react-app client

Creating a new React app in C:\Users\Subho\Documents\GitHub\MERN_Stack_Development\client.

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

npm ERR! Unexpected end of JSON input while parsing near '..."f96a4cb344e5ad39dd8c'

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Subho\AppData\Roamingnpm-cache_logs\2019-05-26T02_07_55_063Z-debug.log

Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts has failed.

Deleting generated file... package.json
Deleting client/ from C:\Users\Subho\Documents\GitHub\MERN_Stack_Development
Done.

1

Debug-Log

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\Subho\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'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session a5f69323147262cd
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://registry.npmjs.org/react 39ms (from cache)
8 http fetch GET 200 https://registry.npmjs.org/react-dom 44ms (from cache)
9 http fetch GET 200 https://registry.npmjs.org/react-scripts 48ms (from cache)
10 silly pacote tag manifest for react@latest fetched in 75ms
11 silly pacote tag manifest for react-dom@latest fetched in 56ms
12 silly pacote tag manifest for react-scripts@latest fetched in 57ms
13 timing stage:loadCurrentTree Completed in 122ms
14 silly install loadIdealTree
15 silly install cloneCurrentTreeToIdealTree
16 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
17 silly install loadShrinkwrap
18 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
19 silly install loadAllDepsIntoIdealTree
20 silly resolveWithNewModule [email protected] checking installable status
21 silly resolveWithNewModule [email protected] checking installable status
22 silly resolveWithNewModule [email protected] checking installable status
23 http fetch GET 200 https://registry.npmjs.org/loose-envify 32ms (from cache)
24 http fetch GET 200 https://registry.npmjs.org/object-assign 31ms (from cache)
25 http fetch GET 200 https://registry.npmjs.org/prop-types 29ms (from cache)
26 http fetch GET 200 https://registry.npmjs.org/scheduler 33ms (from cache)
27 silly pacote range manifest for prop-types@^15.6.2 fetched in 37ms
28 silly resolveWithNewModule [email protected] checking installable status
29 silly pacote range manifest for loose-envify@^1.1.0 fetched in 43ms
30 silly resolveWithNewModule [email protected] checking installable status
31 silly pacote range manifest for object-assign@^4.1.1 fetched in 40ms
32 silly resolveWithNewModule [email protected] checking installable status
33 silly pacote range manifest for scheduler@^0.13.6 fetched in 39ms
34 silly resolveWithNewModule [email protected] checking installable status
35 http fetch GET 200 https://registry.npmjs.org/js-tokens 6ms (from cache)
36 silly pacote range manifest for js-tokens@^3.0.0 || ^4.0.0 fetched in 8ms
37 silly resolveWithNewModule [email protected] checking installable status
38 http fetch GET 200 https://registry.npmjs.org/react-is 8ms (from cache)
39 silly pacote range manifest for react-is@^16.8.1 fetched in 12ms
40 silly resolveWithNewModule [email protected] checking installable status
41 http fetch GET 200 https://registry.npmjs.org/@svgr%2fwebpack 42ms (from cache)
42 http fetch GET 200 https://registry.npmjs.org/@babel%2fcore 44ms (from cache)
43 http fetch GET 200 https://registry.npmjs.org/babel-eslint 41ms (from cache)
44 http fetch GET 200 https://registry.npmjs.org/@typescript-eslint%2feslint-plugin 47ms (from cache)
45 http fetch GET 200 https://registry.npmjs.org/@typescript-eslint%2fparser 52ms (from cache)
46 http fetch GET 200 https://registry.npmjs.org/babel-loader 54ms (from cache)
47 http fetch GET 200 https://registry.npmjs.org/babel-plugin-named-asset-import 62ms (from cache)
48 http fetch GET 200 https://registry.npmjs.org/babel-jest 63ms (from cache)
49 http fetch GET 200 https://registry.npmjs.org/camelcase 63ms (from cache)
50 http fetch GET 200 https://registry.npmjs.org/babel-preset-react-app 65ms (from cache)
51 silly pacote version manifest for @babel/[email protected] fetched in 77ms
52 silly resolveWithNewModule @babel/[email protected] checking installable status
53 silly pacote version manifest for @svgr/[email protected] fetched in 77ms
54 silly resolveWithNewModule @svgr/[email protected] checking installable status
55 silly pacote version manifest for [email protected] fetched in 77ms
56 silly resolveWithNewModule [email protected] checking installable status
57 silly pacote version manifest for @typescript-eslint/[email protected] fetched in 79ms
58 silly resolveWithNewModule @typescript-eslint/[email protected] checking installable status
59 silly pacote version manifest for @typescript-eslint/[email protected] fetched in 82ms
60 silly resolveWithNewModule @typescript-eslint/[email protected] checking installable status
61 silly pacote version manifest for [email protected] fetched in 80ms
62 silly resolveWithNewModule [email protected] checking installable status
63 silly pacote range manifest for babel-plugin-named-asset-import@^0.3.2 fetched in 84ms
64 silly resolveWithNewModule [email protected] checking installable status
65 silly pacote range manifest for babel-jest@^24.8.0 fetched in 86ms
66 silly resolveWithNewModule [email protected] checking installable status
67 silly pacote range manifest for babel-preset-react-app@^9.0.0 fetched in 87ms
68 silly resolveWithNewModule [email protected] checking installable status
69 silly pacote range manifest for camelcase@^5.2.0 fetched in 87ms
70 silly resolveWithNewModule [email protected] checking installable status
71 http fetch GET 200 https://registry.npmjs.org/case-sensitive-paths-webpack-plugin 58ms (from cache)
72 http fetch GET 200 https://registry.npmjs.org/dotenv 52ms (from cache)
73 http fetch GET 200 https://registry.npmjs.org/css-loader 60ms (from cache)
74 http fetch GET 200 https://registry.npmjs.org/dotenv-expand 57ms (from cache)
75 http fetch GET 200 https://registry.npmjs.org/eslint-config-react-app 58ms (from cache)
76 http fetch GET 200 https://registry.npmjs.org/eslint 60ms (from cache)
77 http fetch GET 200 https://registry.npmjs.org/eslint-plugin-import 70ms (from cache)
78 http fetch GET 200 https://registry.npmjs.org/eslint-loader 76ms (from cache)
79 http fetch GET 200 https://registry.npmjs.org/eslint-plugin-flowtype 76ms (from cache)
80 silly fetchPackageMetaData error for [email protected] Unexpected end of JSON input while parsing near '..."f96a4cb344e5ad39dd8c'
81 silly pacote version manifest for [email protected] fetched in 98ms
82 silly resolveWithNewModule [email protected] checking installable status
83 http fetch GET 200 https://registry.npmjs.org/eslint-plugin-jsx-a11y 88ms (from cache)
84 silly pacote version manifest for [email protected] fetched in 108ms
85 silly resolveWithNewModule [email protected] checking installable status
86 silly pacote version manifest for [email protected] fetched in 110ms
87 silly resolveWithNewModule [email protected] checking installable status
88 silly pacote version manifest for [email protected] fetched in 104ms
89 silly resolveWithNewModule [email protected] checking installable status
90 silly pacote range manifest for eslint-config-react-app@^4.0.1 fetched in 105ms
91 silly resolveWithNewModule [email protected] checking installable status
92 silly pacote range manifest for eslint@^5.16.0 fetched in 113ms
93 silly resolveWithNewModule [email protected] checking installable status
94 silly pacote version manifest for [email protected] fetched in 109ms
95 silly resolveWithNewModule [email protected] checking installable status
96 silly pacote version manifest for [email protected] fetched in 110ms
97 silly resolveWithNewModule [email protected] checking installable status
98 silly pacote version manifest for [email protected] fetched in 120ms
99 silly resolveWithNewModule [email protected] checking installable status
100 http fetch GET 200 https://registry.npmjs.org/eslint-plugin-react 74ms (from cache)
101 http fetch GET 200 https://registry.npmjs.org/file-loader 66ms (from cache)
102 http fetch GET 200 https://registry.npmjs.org/eslint-plugin-react-hooks 69ms (from cache)
103 http fetch GET 200 https://registry.npmjs.org/html-webpack-plugin 64ms (from cache)
104 http fetch GET 200 https://registry.npmjs.org/fs-extra 67ms (from cache)
105 http fetch GET 200 https://registry.npmjs.org/identity-obj-proxy 69ms (from cache)
106 http fetch GET 200 https://registry.npmjs.org/is-wsl 66ms (from cache)
107 silly pacote version manifest for [email protected] fetched in 92ms
108 silly resolveWithNewModule [email protected] checking installable status
109 http fetch GET 200 https://registry.npmjs.org/jest-environment-jsdom-fourteen 58ms (from cache)
110 http fetch GET 200 https://registry.npmjs.org/jest 59ms (from cache)
111 silly fetchPackageMetaData error for [email protected] Unexpected end of JSON input while parsing near '..."jest":"^24.1.0","mkd'
112 silly pacote version manifest for [email protected] fetched in 95ms
113 silly resolveWithNewModule [email protected] checking installable status
114 silly pacote range manifest for eslint-plugin-react-hooks@^1.5.0 fetched in 98ms
115 silly resolveWithNewModule [email protected] checking installable status
116 silly pacote version manifest for [email protected] fetched in 91ms
117 silly resolveWithNewModule [email protected] checking installable status
118 http fetch GET 200 https://registry.npmjs.org/jest-resolve 65ms (from cache)
119 silly pacote version manifest for [email protected] fetched in 98ms
120 silly resolveWithNewModule [email protected] checking installable status
121 silly pacote version manifest for [email protected] fetched in 99ms
122 silly resolveWithNewModule [email protected] checking installable status
123 silly pacote range manifest for is-wsl@^1.1.0 fetched in 94ms
124 silly resolveWithNewModule [email protected] checking installable status
125 silly pacote version manifest for [email protected] fetched in 88ms
126 silly resolveWithNewModule [email protected] checking installable status
127 silly pacote version manifest for [email protected] fetched in 93ms
128 silly resolveWithNewModule [email protected] checking installable status
129 http fetch GET 200 https://registry.npmjs.org/jest-watch-typeahead 58ms (from cache)
130 http fetch GET 200 https://registry.npmjs.org/mini-css-extract-plugin 54ms (from cache)
131 http fetch GET 200 https://registry.npmjs.org/optimize-css-assets-webpack-plugin 54ms (from cache)
132 http fetch GET 200 https://registry.npmjs.org/postcss-flexbugs-fixes 47ms (from cache)
133 http fetch GET 200 https://registry.npmjs.org/pnp-webpack-plugin 47ms (from cache)
134 http fetch GET 200 https://registry.npmjs.org/postcss-normalize 39ms (from cache)
135 http fetch GET 200 https://registry.npmjs.org/postcss-loader 49ms (from cache)
136 http fetch GET 200 https://registry.npmjs.org/postcss-preset-env 41ms (from cache)
137 silly pacote version manifest for [email protected] fetched in 72ms
138 silly resolveWithNewModule [email protected] checking installable status
139 http fetch GET 200 https://registry.npmjs.org/postcss-safe-parser 43ms (from cache)
140 silly pacote version manifest for [email protected] fetched in 71ms
141 silly resolveWithNewModule [email protected] checking installable status
142 silly pacote version manifest for [email protected] fetched in 74ms
143 silly resolveWithNewModule [email protected] checking installable status
144 silly pacote version manifest for [email protected] fetched in 67ms
145 silly resolveWithNewModule [email protected] checking installable status
146 silly pacote version manifest for [email protected] fetched in 69ms
147 silly resolveWithNewModule [email protected] checking installable status
148 http fetch GET 200 https://registry.npmjs.org/react-app-polyfill 42ms (from cache)
149 silly pacote version manifest for [email protected] fetched in 66ms
150 silly resolveWithNewModule [email protected] checking installable status
151 silly pacote version manifest for [email protected] fetched in 75ms
152 silly resolveWithNewModule [email protected] checking installable status
153 silly pacote version manifest for [email protected] fetched in 67ms
154 silly resolveWithNewModule [email protected] checking installable status
155 silly pacote version manifest for [email protected] fetched in 67ms
156 silly resolveWithNewModule [email protected] checking installable status
157 silly pacote range manifest for react-app-polyfill@^1.0.1 fetched in 65ms
158 silly resolveWithNewModule [email protected] checking installable status
159 http fetch GET 200 https://registry.npmjs.org/resolve 36ms (from cache)
160 http fetch GET 200 https://registry.npmjs.org/react-dev-utils 39ms (from cache)
161 http fetch GET 200 https://registry.npmjs.org/sass-loader 45ms (from cache)
162 http fetch GET 200 https://registry.npmjs.org/semver 46ms (from cache)
163 http fetch GET 200 https://registry.npmjs.org/style-loader 45ms (from cache)
164 silly pacote range manifest for react-dev-utils@^9.0.1 fetched in 58ms
165 silly resolveWithNewModule [email protected] checking installable status
166 silly pacote version manifest for [email protected] fetched in 60ms
167 silly resolveWithNewModule [email protected] checking installable status
168 http fetch GET 200 https://registry.npmjs.org/terser-webpack-plugin 44ms (from cache)
169 http fetch GET 200 https://registry.npmjs.org/ts-pnp 46ms (from cache)
170 http fetch GET 200 https://registry.npmjs.org/url-loader 47ms (from cache)
171 silly pacote version manifest for [email protected] fetched in 64ms
172 silly resolveWithNewModule [email protected] checking installable status
173 silly pacote version manifest for [email protected] fetched in 71ms
174 silly resolveWithNewModule [email protected] checking installable status
175 http fetch GET 200 https://registry.npmjs.org/webpack 59ms (from cache)
176 silly pacote version manifest for [email protected] fetched in 88ms
177 silly resolveWithNewModule [email protected] checking installable status
178 http fetch GET 200 https://registry.npmjs.org/webpack-dev-server 63ms (from cache)
179 silly pacote version manifest for [email protected] fetched in 90ms
180 silly resolveWithNewModule [email protected] checking installable status
181 silly pacote version manifest for [email protected] fetched in 110ms
182 silly resolveWithNewModule [email protected] checking installable status
183 silly pacote version manifest for [email protected] fetched in 112ms
184 silly resolveWithNewModule [email protected] checking installable status
185 silly pacote version manifest for [email protected] fetched in 113ms
186 silly resolveWithNewModule [email protected] checking installable status
187 http fetch GET 200 https://registry.npmjs.org/workbox-webpack-plugin 78ms (from cache)
188 http fetch GET 200 https://registry.npmjs.org/webpack-manifest-plugin 80ms (from cache)
189 silly pacote version manifest for [email protected] fetched in 99ms
190 silly resolveWithNewModule [email protected] checking installable status
191 silly pacote version manifest for [email protected] fetched in 82ms
192 silly resolveWithNewModule [email protected] checking installable status
193 silly pacote version manifest for [email protected] fetched in 84ms
194 silly resolveWithNewModule [email protected] checking installable status
195 http fetch GET 200 https://registry.npmjs.org/fsevents 67ms (from cache)
196 silly pacote version manifest for [email protected] fetched in 69ms
197 silly resolveWithNewModule [email protected] checking installable status
198 timing stage:rollbackFailedOptional Completed in 1ms
199 timing stage:runTopLevelLifecycles Completed in 755ms
200 silly saveTree [email protected]
200 silly saveTree +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | | -- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | |-- [email protected]
200 silly saveTree | -- [email protected] 200 silly saveTree +-- [email protected] 200 silly saveTree | +-- @babel/[email protected] 200 silly saveTree | |-- [email protected]
200 silly saveTree | +-- @svgr/[email protected]
200 silly saveTree | +-- @typescript-eslint/[email protected]
200 silly saveTree | | -- @typescript-eslint/[email protected] 200 silly saveTree | +-- @typescript-eslint/[email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | +-- [email protected] 200 silly saveTree | |-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | +-- [email protected]
200 silly saveTree | -- [email protected] 200 silly saveTree-- [email protected]
201 verbose stack SyntaxError: Unexpected end of JSON input while parsing near '..."f96a4cb344e5ad39dd8c'
201 verbose stack at JSON.parse ()
201 verbose stack at parseJson (C:\Users\Subho\AppData\Roamingnpm\node_modulesnpm\node_modulesjson-parse-better-errors\index.js:7:17)
201 verbose stack at C:\Users\Subho\AppData\Roamingnpm\node_modulesnpm\node_modules\node-fetch-npm\src\body.js:96:50
201 verbose stack at processTicksAndRejections (internal/process/task_queues.js:89:5)
202 verbose cwd C:\Users\Subho\Documents\GitHub\MERN_Stack_Development\client
203 verbose Windows_NT 10.0.17763
204 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Users\Subho\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "--save" "--save-exact" "--loglevel" "error" "react" "react-dom" "react-scripts"
205 verbose node v12.1.0
206 verbose npm v6.9.0
207 error Unexpected end of JSON input while parsing near '..."f96a4cb344e5ad39dd8c'
208 verbose exit [ 1, true ]

Reproducible Demo

https://github.com/isubhokarma/MERN_Stack_Development

needs investigation

Most helpful comment

@isubhokarma, can you please try cleaning out your npm cache?

npm cache clean --force

if that does or doesn't help, let us know!

All 6 comments

@isubhokarma

The error you are showing here is in create-react-app command but you gave us a demo link which means that the command was successful and you pushed the results to github.

I downloaded your repository and ran npm i without any errors, Do you still have this problem??

Hello, @mohsenSy
Yes, I'm still facing the same issue. I can't install - "server-folder/ npx create-react-app client" and the installation process it is coming up with this --

C:\Users\Subho\Documents\GitHub\MERN_Stack_Development>npx create-react-app client

Creating a new React app in C:\Users\Subho\Documents\GitHub\MERN_Stack_Development\client.

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

npm ERR! Unexpected end of JSON input while parsing near '..."f96a4cb344e5ad39dd8c'

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Subho\AppData\Roamingnpm-cache_logs\2019-05-27T03_36_41_725Z-debug.log

Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts has failed.

Deleting generated file... package.json
Deleting client/ from C:\Users\Subho\Documents\GitHub\MERN_Stack_Development
Done.

Please, take a look and try installing "npx create-react-app client" inside the server folder (ie. MERN_Stack_Development) and let me know ASAP.

While the installation process the terminal is showing some sudden error message like "jest-environment-jsdom-fourteen": "0.1.0 json error unexpected error".

@isubhokarma, can you please try cleaning out your npm cache?

npm cache clean --force

if that does or doesn't help, let us know!

@mrmckeb Thank You, Broo. It worked.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Aranir picture Aranir  路  3Comments

JimmyLv picture JimmyLv  路  3Comments

ap13p picture ap13p  路  3Comments

alleroux picture alleroux  路  3Comments

DaveLindberg picture DaveLindberg  路  3Comments