Public Ticket #164
npm install failed
Closed
Comments
Sanjaya Dulal
replied
3 years ago on August 19, 2021 at 10:08 AM
It's working on old version of node.. Well i have switch it and run it successfully.
Thank you for your response.
Yamini Gaur
replied
3 years ago on August 19, 2021 at 06:12 AM
Hello Sir,
Hope you are doing well, It's a follow-up message regarding your current Ticket.
We did not get your feedback on the last message so just want to ask if your problem has been fixed we can close your ticket, but if you did not get a solution still please update us.
Note: in case of not receiving any reply in the next 2 days ticket will close automatically.
Thanks & Regards
Yamini
DexignZone
Yamini Gaur
replied
3 years ago on August 14, 2021 at 05:46 AM
Hello Sir,
Thanks for being our customer.
I think you don't read the documentation properly.
Please read it and then again update us about your problem.
Documentation Link is given below:
Link: https://samar.dexignzone.com/react/doc/
I hope after this you don't see these issues. But you see these again please update us, We are here to help you.
Thanks & regards
Yamini
DexignZone
Sanjaya Dulal
replied
started the conversation
3 years ago on August 13, 2021 at 07:41 AM
0 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'cache', 'clear' ]
1 info using npm@7.19.1
2 info using node@v16.5.0
3 timing npm:load:whichnode Completed in 0ms
4 timing config:load:defaults Completed in 1ms
5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 1ms
6 timing config:load:builtin Completed in 1ms
7 timing config:load:cli Completed in 1ms
8 timing config:load:env Completed in 0ms
9 timing config:load:file:/Users/sanjayadulal/Sites/samar-3/.npmrc Completed in 0ms
10 timing config:load:project Completed in 0ms
11 timing config:load:file:/Users/sanjayadulal/.npmrc Completed in 1ms
12 timing config:load:user Completed in 1ms
13 timing config:load:file:/usr/local/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:credentials Completed in 0ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 5ms
19 timing npm:load:configload Completed in 5ms
20 timing npm:load:setTitle Completed in 7ms
21 timing npm:load:setupLog Completed in 1ms
22 timing npm:load:cleanupLog Completed in 1ms
23 timing npm:load:configScope Completed in 0ms
24 timing npm:load:projectScope Completed in 0ms
25 timing npm:load Completed in 14ms
26 timing config:load:flatten Completed in 1ms
27 timing command:cache Completed in 0ms
28 verbose stack Error: As of npm@5, the npm cache self-heals from corruption issues
28 verbose stack by treating integrity mismatches as cache misses. As a result,
28 verbose stack data extracted from the cache is guaranteed to be valid. If you
28 verbose stack want to make sure everything is consistent, use `npm cache verify`
28 verbose stack instead. Deleting the cache can only make npm go slower, and is
28 verbose stack not likely to correct any problems you may be encountering!
28 verbose stack
28 verbose stack On the other hand, if you're debugging an issue with the installer,
28 verbose stack or race conditions that depend on the timing of writing to an empty
28 verbose stack cache, you can use `npm install --cache /tmp/empty-cache` to use a
28 verbose stack temporary cache instead of nuking the actual one.
28 verbose stack
28 verbose stack If you're sure you want to delete the entire cache, rerun this command
28 verbose stack with --force.
28 verbose stack at Cache.clean (/usr/local/lib/node_modules/npm/lib/cache.js:76:13)
28 verbose stack at Cache.cache (/usr/local/lib/node_modules/npm/lib/cache.js:59:27)
28 verbose stack at Cache.exec (/usr/local/lib/node_modules/npm/lib/cache.js:52:10)
28 verbose stack at Object.[_runCmd] (/usr/local/lib/node_modules/npm/lib/npm.js:121:12)
28 verbose stack at /usr/local/lib/node_modules/npm/lib/npm.js:29:35
28 verbose stack at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:73:5)
29 verbose cwd /Users/sanjayadulal/Sites/samar-3
30 verbose Darwin 21.0.0
31 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "cache" "clear"
32 verbose node v16.5.0
33 verbose npm v7.19.1
34 error As of npm@5, the npm cache self-heals from corruption issues
34 error by treating integrity mismatches as cache misses. As a result,
34 error data extracted from the cache is guaranteed to be valid. If you
34 error want to make sure everything is consistent, use `npm cache verify`
34 error instead. Deleting the cache can only make npm go slower, and is
34 error not likely to correct any problems you may be encountering!
34 error
34 error On the other hand, if you're debugging an issue with the installer,
34 error or race conditions that depend on the timing of writing to an empty
34 error cache, you can use `npm install --cache /tmp/empty-cache` to use a
34 error temporary cache instead of nuking the actual one.
34 error
34 error If you're sure you want to delete the entire cache, rerun this command
34 error with --force.
35 verbose exit 1
Hello Sir,
We are happy that your problem has been solved. But you have some other queries please tell us. We are here to help you.
Sir, we need a favor from you, please drop the best 5-star rating with your golden words ...
For Drop Item Rating you can follow these steps:-
Go to your Theme-forest Account
Follow this image
Thanks & Regards
Yamini
DexignZone