vivo环境搭建不成功

Creator 2.x
#1

  • Creator 版本：

  • 目标平台：

  • 详细报错信息，包含调用堆栈：

  • 重现方式：

  • 之前哪个版本是正常的 ：

  • 手机型号 ：

  • 手机浏览器 ：

  • 编辑器操作系统 ：

  • 编辑器之前是否有其它报错 ：

  • 出现概率：

  • 额外线索：

#2

粘贴的图像1920×1048 97.5 KB

nodejs升级，卸载重装好几次了都不行

#3

这下面是日志：

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:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js’,
1 verbose cli ‘install’,
1 verbose cli ‘-g’,
1 verbose cli ‘@vivo-minigame/cli’
1 verbose cli ]
2 info using npm@6.12.0
3 info using node@v12.13.0
4 verbose npm-session dcd2155fdc9a843a
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/@vivo-minigame%2Fcli 1141ms (from cache)
8 silly pacote tag manifest for @vivo-minigame/cli@latest fetched in 1159ms
9 timing stage:loadCurrentTree Completed in 1173ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 1ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule @vivo-minigame/cli@1.1.7 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/@babel%2Fruntime-corejs2 238ms (from cache)
18 silly pacote range manifest for @babel/runtime-corejs2@^7.5.5 fetched in 242ms
19 silly resolveWithNewModule @babel/runtime-corejs2@7.7.2 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/import-global 627ms (from cache)
21 http fetch GET 304 https://registry.npmjs.org/debug 634ms (from cache)
22 http fetch GET 304 https://registry.npmjs.org/commander 636ms (from cache)
23 silly pacote range manifest for import-global@^0.1.0 fetched in 634ms
24 silly resolveWithNewModule import-global@0.1.0 checking installable status
25 http fetch GET 304 https://registry.npmjs.org/didyoumean 637ms (from cache)
26 http fetch GET 304 https://registry.npmjs.org/inquirer 636ms (from cache)
27 http fetch GET 304 https://registry.npmjs.org/latest-version 637ms (from cache)
28 http fetch GET 304 https://registry.npmjs.org/lru-cache 637ms (from cache)
29 silly pacote range manifest for debug@^4.1.1 fetched in 643ms
30 silly resolveWithNewModule debug@4.1.1 checking installable status
31 silly pacote range manifest for commander@^2.20.0 fetched in 644ms
32 silly resolveWithNewModule commander@2.20.3 checking installable status
33 silly pacote range manifest for didyoumean@^1.2.1 fetched in 645ms
34 silly resolveWithNewModule didyoumean@1.2.1 checking installable status
35 silly pacote range manifest for inquirer@^6.4.1 fetched in 643ms
36 silly resolveWithNewModule inquirer@6.5.2 checking installable status
37 silly pacote range manifest for latest-version@^5.1.0 fetched in 643ms
38 silly resolveWithNewModule latest-version@5.1.0 checking installable status
39 silly pacote range manifest for lru-cache@^5.1.1 fetched in 642ms
40 silly resolveWithNewModule lru-cache@5.1.1 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/@vivo-minigame%2Fcli-shared-utils 868ms (from cache)
42 silly pacote range manifest for @vivo-minigame/cli-shared-utils@^1.1.7 fetched in 871ms
43 silly resolveWithNewModule @vivo-minigame/cli-shared-utils@1.1.7 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/core-js 221ms (from cache)
45 silly pacote range manifest for core-js@^2.6.5 fetched in 227ms
46 warn deprecated core-js@2.6.10: core-js@<3.0 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
47 silly resolveWithNewModule core-js@2.6.10 checking installable status
48 http fetch GET 304 https://registry.npmjs.org/regenerator-runtime 230ms (from cache)
49 silly pacote range manifest for regenerator-runtime@^0.13.2 fetched in 231ms
50 silly resolveWithNewModule regenerator-runtime@0.13.3 checking installable status
51 http fetch GET 304 https://registry.npmjs.org/execa 216ms (from cache)
52 silly pacote range manifest for execa@^2.0.3 fetched in 223ms
53 silly resolveWithNewModule execa@2.1.0 checking installable status
54 http fetch GET 304 https://registry.npmjs.org/ora 224ms (from cache)
55 http fetch GET 304 https://registry.npmjs.org/minimist 224ms (from cache)
56 http fetch GET 304 https://registry.npmjs.org/semver 226ms (from cache)
57 silly pacote range manifest for minimist@^1.2.0 fetched in 229ms
58 silly resolveWithNewModule minimist@1.2.0 checking installable status
59 silly pacote range manifest for ora@^3.4.0 fetched in 229ms
60 silly resolveWithNewModule ora@3.4.0 checking installable status
61 silly pacote range manifest for semver@^6.2.0 fetched in 230ms
62 silly resolveWithNewModule semver@6.3.0 checking installable status
63 http fetch GET 304 https://registry.npmjs.org/string.prototype.padstart 230ms (from cache)
64 http fetch GET 304 https://registry.npmjs.org/readline 231ms (from cache)
65 silly pacote range manifest for string.prototype.padstart@^3.0.0 fetched in 234ms
66 silly resolveWithNewModule string.prototype.padstart@3.0.0 checking installable status
67 silly pacote range manifest for readline@^1.3.0 fetched in 234ms
68 silly resolveWithNewModule readline@1.3.0 checking installable status
69 http fetch GET 304 https://registry.npmjs.org/fs-extra 242ms (from cache)
70 silly pacote range manifest for fs-extra@^8.1.0 fetched in 244ms
71 silly resolveWithNewModule fs-extra@8.1.0 checking installable status
72 http fetch GET 304 https://registry.npmjs.org/chalk 246ms (from cache)
73 silly pacote range manifest for chalk@^2.4.2 fetched in 249ms
74 silly resolveWithNewModule chalk@2.4.2 checking installable status
75 http fetch GET 304 https://registry.npmjs.org/escape-string-regexp 226ms (from cache)
76 http fetch GET 304 https://registry.npmjs.org/supports-color 228ms (from cache)
77 silly pacote range manifest for escape-string-regexp@^1.0.5 fetched in 229ms
78 silly resolveWithNewModule escape-string-regexp@1.0.5 checking installable status
79 silly pacote range manifest for supports-color@^5.3.0 fetched in 230ms
80 silly resolveWithNewModule supports-color@5.5.0 checking installable status
81 http fetch GET 304 https://registry.npmjs.org/ansi-styles 312ms (from cache)
82 silly pacote range manifest for ansi-styles@^3.2.1 fetched in 314ms
83 silly resolveWithNewModule ansi-styles@3.2.1 checking installable status
84 http fetch GET 304 https://registry.npmjs.org/color-convert 213ms (from cache)
85 silly pacote range manifest for color-convert@^1.9.0 fetched in 232ms
86 silly resolveWithNewModule color-convert@1.9.3 checking installable status
87 http fetch GET 304 https://registry.npmjs.org/color-name 214ms (from cache)
88 silly pacote version manifest for color-name@1.1.3 fetched in 223ms
89 silly resolveWithNewModule color-name@1.1.3 checking installable status
90 http fetch GET 304 https://registry.npmjs.org/has-flag 242ms (from cache)
91 silly pacote range manifest for has-flag@^3.0.0 fetched in 247ms
92 silly resolveWithNewModule has-flag@3.0.0 checking installable status
93 http fetch GET 304 https://registry.npmjs.org/get-stream 293ms (from cache)
94 http fetch GET 304 https://registry.npmjs.org/is-stream 293ms (from cache)
95 http fetch GET 304 https://registry.npmjs.org/p-finally 295ms (from cache)
96 http fetch GET 304 https://registry.npmjs.org/npm-run-path 297ms (from cache)
97 http fetch GET 304 https://registry.npmjs.org/onetime 298ms (from cache)
98 http fetch GET 304 https://registry.npmjs.org/cross-spawn 302ms (from cache)
99 silly pacote range manifest for get-stream@^5.0.0 fetched in 302ms
100 silly resolveWithNewModule get-stream@5.1.0 checking installable status
101 http fetch GET 304 https://registry.npmjs.org/strip-final-newline 300ms (from cache)
102 http fetch GET 304 https://registry.npmjs.org/merge-stream 302ms (from cache)
103 silly pacote range manifest for is-stream@^2.0.0 fetched in 305ms
104 silly resolveWithNewModule is-stream@2.0.0 checking installable status
105 silly pacote range manifest for npm-run-path@^3.0.0 fetched in 304ms
106 silly resolveWithNewModule npm-run-path@3.1.0 checking installable status
107 silly pacote range manifest for p-finally@^2.0.0 fetched in 304ms
108 silly resolveWithNewModule p-finally@2.0.1 checking installable status
109 http fetch GET 304 https://registry.npmjs.org/signal-exit 304ms (from cache)
110 silly pacote range manifest for onetime@^5.1.0 fetched in 305ms
111 silly resolveWithNewModule onetime@5.1.0 checking installable status
112 silly pacote range manifest for cross-spawn@^7.0.0 fetched in 310ms
113 silly resolveWithNewModule cross-spawn@7.0.1 checking installable status
114 silly pacote range manifest for strip-final-newline@^2.0.0 fetched in 306ms
115 silly resolveWithNewModule strip-final-newline@2.0.0 checking installable status
116 silly pacote range manifest for merge-stream@^2.0.0 fetched in 309ms
117 silly resolveWithNewModule merge-stream@2.0.0 checking installable status
118 silly pacote range manifest for signal-exit@^3.0.2 fetched in 308ms
119 silly resolveWithNewModule signal-exit@3.0.2 checking installable status
120 http fetch GET 304 https://registry.npmjs.org/path-key 233ms (from cache)
121 http fetch GET 304 https://registry.npmjs.org/shebang-command 234ms (from cache)
122 http fetch GET 304 https://registry.npmjs.org/which 235ms (from cache)
123 silly pacote range manifest for path-key@^3.1.0 fetched in 237ms
124 silly resolveWithNewModule path-key@3.1.0 checking installable status
125 silly pacote range manifest for shebang-command@^2.0.0 fetched in 237ms
126 silly resolveWithNewModule shebang-command@2.0.0 checking installable status
127 silly pacote range manifest for which@^2.0.1 fetched in 238ms
128 silly resolveWithNewModule which@2.0.2 checking installable status
129 http fetch GET 304 https://registry.npmjs.org/shebang-regex 211ms (from cache)
130 silly pacote range manifest for shebang-regex@^3.0.0 fetched in 216ms
131 silly resolveWithNewModule shebang-regex@3.0.0 checking installable status
132 http fetch GET 304 https://registry.npmjs.org/isexe 215ms (from cache)
133 silly pacote range manifest for isexe@^2.0.0 fetched in 219ms
134 silly resolveWithNewModule isexe@2.0.0 checking installable status
135 http fetch GET 304 https://registry.npmjs.org/pump 211ms (from cache)
136 silly pacote range manifest for pump@^3.0.0 fetched in 217ms
137 silly resolveWithNewModule pump@3.0.0 checking installable status
138 http fetch GET 304 https://registry.npmjs.org/end-of-stream 233ms (from cache)
139 http fetch GET 304 https://registry.npmjs.org/once 234ms (from cache)
140 silly pacote range manifest for end-of-stream@^1.1.0 fetched in 238ms
141 silly resolveWithNewModule end-of-stream@1.4.4 checking installable status
142 silly pacote range manifest for once@^1.3.1 fetched in 239ms
143 silly resolveWithNewModule once@1.4.0 checking installable status
144 http fetch GET 304 https://registry.npmjs.org/wrappy 206ms (from cache)
145 silly pacote range manifest for wrappy@1 fetched in 210ms
146 silly resolveWithNewModule wrappy@1.0.2 checking installable status
147 http fetch GET 304 https://registry.npmjs.org/mimic-fn 224ms (from cache)
148 silly pacote range manifest for mimic-fn@^2.1.0 fetched in 232ms
149 silly resolveWithNewModule mimic-fn@2.1.0 checking installable status
150 http fetch GET 304 https://registry.npmjs.org/jsonfile 249ms (from cache)
151 http fetch GET 304 https://registry.npmjs.org/universalify 248ms (from cache)
152 http fetch GET 304 https://registry.npmjs.org/graceful-fs 253ms (from cache)
153 silly pacote range manifest for universalify@^0.1.0 fetched in 255ms
154 silly resolveWithNewModule universalify@0.1.2 checking installable status
155 silly pacote range manifest for jsonfile@^4.0.0 fetched in 257ms
156 silly resolveWithNewModule jsonfile@4.0.0 checking installable status
157 silly pacote range manifest for graceful-fs@^4.2.0 fetched in 260ms
158 silly resolveWithNewModule graceful-fs@4.2.3 checking installable status
159 http fetch GET 304 https://registry.npmjs.org/yallist 202ms (from cache)
160 silly pacote range manifest for yallist@^3.0.2 fetched in 205ms
161 silly resolveWithNewModule yallist@3.1.1 checking installable status
162 http fetch GET 304 https://registry.npmjs.org/cli-cursor 257ms (from cache)
163 silly pacote range manifest for cli-cursor@^2.1.0 fetched in 259ms
164 silly resolveWithNewModule cli-cursor@2.1.0 checking installable status
165 http fetch GET 304 https://registry.npmjs.org/wcwidth 255ms (from cache)
166 http fetch GET 304 https://registry.npmjs.org/cli-spinners 258ms (from cache)
167 http fetch GET 304 https://registry.npmjs.org/log-symbols 257ms (from cache)
168 http fetch GET 304 https://registry.npmjs.org/strip-ansi 257ms (from cache)
169 silly pacote range manifest for wcwidth@^1.0.1 fetched in 257ms
170 silly resolveWithNewModule wcwidth@1.0.1 checking installable status
171 silly pacote range manifest for cli-spinners@^2.0.0 fetched in 263ms
172 silly resolveWithNewModule cli-spinners@2.2.0 checking installable status
173 silly pacote range manifest for log-symbols@^2.2.0 fetched in 261ms
174 silly resolveWithNewModule log-symbols@2.2.0 checking installable status
175 silly pacote range manifest for strip-ansi@^5.2.0 fetched in 261ms
176 silly resolveWithNewModule strip-ansi@5.2.0 checking installable status
177 http fetch GET 304 https://registry.npmjs.org/restore-cursor 217ms (from cache)
178 silly pacote range manifest for restore-cursor@^2.0.0 fetched in 230ms
179 silly resolveWithNewModule restore-cursor@2.0.0 checking installable status
180 silly pacote range manifest for onetime@^2.0.0 fetched in 2ms
181 silly resolveWithNewModule onetime@2.0.1 checking installable status
182 silly pacote range manifest for mimic-fn@^1.0.0 fetched in 2ms
183 silly resolveWithNewModule mimic-fn@1.2.0 checking installable status
184 http fetch GET 304 https://registry.npmjs.org/ansi-regex 200ms (from cache)
185 silly pacote range manifest for ansi-regex@^4.1.0 fetched in 204ms
186 silly resolveWithNewModule ansi-regex@4.1.0 checking installable status
187 http fetch GET 304 https://registry.npmjs.org/defaults 225ms (from cache)
188 silly pacote range manifest for defaults@^1.0.3 fetched in 236ms
189 silly resolveWithNewModule defaults@1.0.3 checking installable status
190 http fetch GET 304 https://registry.npmjs.org/clone 218ms (from cache)
191 silly pacote range manifest for clone@^1.0.2 fetched in 229ms
192 silly resolveWithNewModule clone@1.0.4 checking installable status
193 http fetch GET 304 https://registry.npmjs.org/function-bind 245ms (from cache)
194 http fetch GET 304 https://registry.npmjs.org/define-properties 248ms (from cache)
195 http fetch GET 304 https://registry.npmjs.org/es-abstract 249ms (from cache)
196 silly pacote range manifest for function-bind@^1.0.2 fetched in 249ms
197 silly resolveWithNewModule function-bind@1.1.1 checking installable status
198 silly pacote range manifest for define-properties@^1.1.2 fetched in 252ms
199 silly resolveWithNewModule define-properties@1.1.3 checking installable status
200 silly pacote range manifest for es-abstract@^1.4.3 fetched in 252ms
201 silly resolveWithNewModule es-abstract@1.16.0 checking installable status
202 http fetch GET 304 https://registry.npmjs.org/object-keys 218ms (from cache)
203 silly pacote range manifest for object-keys@^1.0.12 fetched in 225ms
204 silly resolveWithNewModule object-keys@1.1.1 checking installable status
205 http fetch GET 304 https://registry.npmjs.org/es-to-primitive 274ms (from cache)
206 http fetch GET 304 https://registry.npmjs.org/is-regex 273ms (from cache)
207 http fetch GET 304 https://registry.npmjs.org/string.prototype.trimleft 274ms (from cache)
208 http fetch GET 304 https://registry.npmjs.org/string.prototype.trimright 274ms (from cache)
209 http fetch GET 304 https://registry.npmjs.org/has 279ms (from cache)
210 http fetch GET 304 https://registry.npmjs.org/is-callable 280ms (from cache)
211 silly pacote range manifest for es-to-primitive@^1.2.0 fetched in 284ms
212 silly resolveWithNewModule es-to-primitive@1.2.1 checking installable status
213 silly pacote range manifest for is-regex@^1.0.4 fetched in 282ms
214 silly resolveWithNewModule is-regex@1.0.4 checking installable status
215 http fetch GET 304 https://registry.npmjs.org/object-inspect 282ms (from cache)
216 http fetch GET 304 https://registry.npmjs.org/has-symbols 284ms (from cache)
217 silly pacote range manifest for string.prototype.trimleft@^2.1.0 fetched in 283ms
218 silly resolveWithNewModule string.prototype.trimleft@2.1.0 checking installable status
219 silly pacote range manifest for string.prototype.trimright@^2.1.0 fetched in 283ms
220 silly resolveWithNewModule string.prototype.trimright@2.1.0 checking installable status
221 silly pacote range manifest for has@^1.0.3 fetched in 287ms
222 silly resolveWithNewModule has@1.0.3 checking installable status
223 silly pacote range manifest for is-callable@^1.1.4 fetched in 286ms
224 silly resolveWithNewModule is-callable@1.1.4 checking installable status
225 silly pacote range manifest for object-inspect@^1.6.0 fetched in 286ms
226 silly resolveWithNewModule object-inspect@1.7.0 checking installable status
227 silly pacote range manifest for has-symbols@^1.0.0 fetched in 288ms
228 silly resolveWithNewModule has-symbols@1.0.1 checking installable status
229 http fetch GET 304 https://registry.npmjs.org/is-symbol 199ms (from cache)
230 silly pacote range manifest for is-symbol@^1.0.2 fetched in 206ms
231 silly resolveWithNewModule is-symbol@1.0.2 checking installable status
232 http fetch GET 304 https://registry.npmjs.org/is-date-object 300ms (from cache)
233 silly pacote range manifest for is-date-object@^1.0.1 fetched in 304ms
234 silly resolveWithNewModule is-date-object@1.0.1 checking installable status
235 http fetch GET 304 https://registry.npmjs.org/ms 200ms (from cache)
236 silly pacote range manifest for ms@^2.1.1 fetched in 204ms
237 silly resolveWithNewModule ms@2.1.2 checking installable status
238 http fetch GET 304 https://registry.npmjs.org/global-dirs 210ms (from cache)
239 silly pacote range manifest for global-dirs@^0.1.0 fetched in 215ms
240 silly resolveWithNewModule global-dirs@0.1.1 checking installable status
241 http fetch GET 304 https://registry.npmjs.org/ini 241ms (from cache)
242 silly pacote range manifest for ini@^1.3.4 fetched in 245ms
243 silly resolveWithNewModule ini@1.3.5 checking installable status
244 http fetch GET 304 https://registry.npmjs.org/run-async 268ms (from cache)
245 http fetch GET 304 https://registry.npmjs.org/through 265ms (from cache)
246 http fetch GET 304 https://registry.npmjs.org/lodash 272ms (from cache)
247 http fetch GET 304 https://registry.npmjs.org/string-width 270ms (from cache)
248 silly pacote range manifest for run-async@^2.2.0 fetched in 273ms
249 silly resolveWithNewModule run-async@2.3.0 checking installable status
250 http fetch GET 304 https://registry.npmjs.org/cli-width 277ms (from cache)
251 http fetch GET 304 https://registry.npmjs.org/mute-stream 275ms (from cache)
252 http fetch GET 304 https://registry.npmjs.org/external-editor 279ms (from cache)
253 silly pacote range manifest for through@^2.3.6 fetched in 271ms
254 silly resolveWithNewModule through@2.3.8 checking installable status
255 silly pacote range manifest for lodash@^4.17.12 fetched in 278ms
256 silly resolveWithNewModule lodash@4.17.15 checking installable status
257 silly pacote range manifest for string-width@^2.1.0 fetched in 276ms
258 silly resolveWithNewModule string-width@2.1.1 checking installable status
259 silly pacote range manifest for cli-width@^2.0.0 fetched in 282ms
260 silly resolveWithNewModule cli-width@2.2.0 checking installable status
261 http fetch GET 304 https://registry.npmjs.org/rxjs 279ms (from cache)
262 silly pacote version manifest for mute-stream@0.0.7 fetched in 284ms
263 silly resolveWithNewModule mute-stream@0.0.7 checking installable status
264 silly pacote range manifest for external-editor@^3.0.3 fetched in 287ms
265 silly resolveWithNewModule external-editor@3.1.0 checking installable status
266 silly pacote range manifest for rxjs@^6.4.0 fetched in 284ms
267 silly resolveWithNewModule rxjs@6.5.3 checking installable status
268 http fetch GET 304 https://registry.npmjs.org/ansi-escapes 290ms (from cache)
269 silly pacote range manifest for ansi-escapes@^3.2.0 fetched in 291ms
270 silly resolveWithNewModule ansi-escapes@3.2.0 checking installable status
271 http fetch GET 304 https://registry.npmjs.org/figures 564ms (from cache)
272 silly pacote range manifest for figures@^2.0.0 fetched in 568ms
273 silly resolveWithNewModule figures@2.0.0 checking installable status
274 http fetch GET 304 https://registry.npmjs.org/iconv-lite 211ms (from cache)
275 silly pacote range manifest for iconv-lite@^0.4.24 fetched in 214ms
276 silly resolveWithNewModule iconv-lite@0.4.24 checking installable status
277 http fetch GET 304 https://registry.npmjs.org/chardet 216ms (from cache)
278 http fetch GET 304 https://registry.npmjs.org/tmp 215ms (from cache)
279 silly pacote range manifest for chardet@^0.7.0 fetched in 219ms
280 silly resolveWithNewModule chardet@0.7.0 checking installable status
281 silly pacote range manifest for tmp@^0.0.33 fetched in 217ms
282 silly resolveWithNewModule tmp@0.0.33 checking installable status
283 http fetch GET 304 https://registry.npmjs.org/safer-buffer 203ms (from cache)
284 silly pacote range manifest for safer-buffer@>= 2.1.2 < 3 fetched in 206ms
285 silly resolveWithNewModule safer-buffer@2.1.2 checking installable status
286 http fetch GET 304 https://registry.npmjs.org/os-tmpdir 210ms (from cache)
287 silly pacote range manifest for os-tmpdir@~1.0.2 fetched in 217ms
288 silly resolveWithNewModule os-tmpdir@1.0.2 checking installable status
289 http fetch GET 304 https://registry.npmjs.org/is-promise 211ms (from cache)
290 silly pacote range manifest for is-promise@^2.1.0 fetched in 215ms
291 silly resolveWithNewModule is-promise@2.1.0 checking installable status
292 http fetch GET 304 https://registry.npmjs.org/tslib 197ms (from cache)
293 silly pacote range manifest for tslib@^1.9.0 fetched in 200ms
294 silly resolveWithNewModule tslib@1.10.0 checking installable status
295 silly pacote range manifest for strip-ansi@^4.0.0 fetched in 3ms
296 silly resolveWithNewModule strip-ansi@4.0.0 checking installable status
297 http fetch GET 304 https://registry.npmjs.org/is-fullwidth-code-point 220ms (from cache)
298 silly pacote range manifest for is-fullwidth-code-point@^2.0.0 fetched in 223ms
299 silly resolveWithNewModule is-fullwidth-code-point@2.0.0 checking installable status
300 silly pacote range manifest for ansi-regex@^3.0.0 fetched in 3ms
301 silly resolveWithNewModule ansi-regex@3.0.0 checking installable status
302 http fetch GET 304 https://registry.npmjs.org/package-json 212ms (from cache)
303 silly pacote range manifest for package-json@^6.3.0 fetched in 216ms
304 silly resolveWithNewModule package-json@6.5.0 checking installable status
305 http fetch GET 304 https://registry.npmjs.org/got 228ms (from cache)
306 http fetch GET 304 https://registry.npmjs.org/registry-url 228ms (from cache)
307 silly fetchPackageMetaData error for got@^9.6.0 Unexpected end of JSON input while parsing near ‘…WoW2VO+SYpFp69C27ag+6’
308 silly pacote range manifest for registry-url@^5.0.0 fetched in 234ms
309 silly resolveWithNewModule registry-url@5.1.0 checking installable status
310 http fetch GET 304 https://registry.npmjs.org/registry-auth-token 242ms (from cache)
311 silly pacote range manifest for registry-auth-token@^4.0.0 fetched in 245ms
312 silly resolveWithNewModule registry-auth-token@4.0.0 checking installable status
313 timing stage:rollbackFailedOptional Completed in 0ms
314 timing stage:runTopLevelLifecycles Completed in 11346ms
315 verbose stack SyntaxError: Unexpected end of JSON input while parsing near ‘…WoW2VO+SYpFp69C27ag+6’
315 verbose stack at JSON.parse ()
315 verbose stack at parseJson (C:\Program Files\nodejs\node_modules\npm\node_modules\json-parse-better-errors\index.js:7:17)
315 verbose stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-fetch-npm\src\body.js:96:50
315 verbose stack at runMicrotasks ()
315 verbose stack at processTicksAndRejections (internal/process/task_queues.js:93:5)
316 verbose cwd C:\Users\pld
317 verbose Windows_NT 10.0.17763
318 verbose argv “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js” “install” “-g” “@vivo-minigame/cli”
319 verbose node v12.13.0
320 verbose npm v6.12.0
321 error Unexpected end of JSON input while parsing near ‘…WoW2VO+SYpFp69C27ag+6’
322 verbose exit [ 1, true ]

#4

麻烦各位大佬了

#5

我把npm升级成淘宝镜像cnpm，然后再安装vivo的脚手架，然后就成功了，分享一下心得，希望后面的人不要再碰到我这样的问题了

2赞