#i tried it and again nothing changes

1 messages · Page 1 of 1 (latest)

strange hawk
#

come i control ur pc

#

so i can fix ur nextjs

#

give me code

thick musk
#

code of what?

strange hawk
#

use that link

#

i can remote control ur pc

#

so i can run that script and fix that issue

thick musk
#

which link?

strange hawk
#

npm cache clean

#

try this command

#

npm cache clean -f

thick musk
#

PS C:\Users\vzhoo\Desktop\Real-estate> npm cache clean
npm ERR! As of npm@5, the npm cache self-heals from corruption issues
npm ERR! by treating integrity mismatches as cache misses. As a result,
npm ERR! data extracted from the cache is guaranteed to be valid. If you
npm ERR! want to make sure everything is consistent, use npm cache verify
npm ERR! instead. Deleting the cache can only make npm go slower, and is
npm ERR! not likely to correct any problems you may be encountering!
npm ERR!
npm ERR! On the other hand, if you're debugging an issue with the installer,
npm ERR! or race conditions that depend on the timing of writing to an empty
npm ERR! cache, you can use npm install --cache /tmp/empty-cache to use a
npm ERR! temporary cache instead of nuking the actual one.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command
npm ERR! with --force.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\vzhoo\AppData\Local\npm-cache_logs\2023-07-11T10_09_30_479Z-debug-0.log

strange hawk
#

connect me to ur pc