Original error loadvirtual requires existing shrinkwrap file

Install Error: ERR! code ENOLOCK #3107

Current Situation

Installed on a fresh Mac Mini (Late 2012) with upgraded 8GB ram and SSD but got a few errors and not sure if I should ignore or be worried about the «9 vulnerabilities».

I’ve installed on my other M1 Mac Mini before without any issues and found the set up a walk in the park, so I’m not a total noob, but still new to dealing with terminal. 🙂

server$ npm install -g npm@8.6.0 npm ERR! code EACCES npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/npm npm ERR! dest /usr/local/lib/node_modules/.npm-i9nnxROI npm ERR! errno -13 npm ERR! Error: EACCES: permission denied, rename ‘/usr/local/lib/node_modules/npm’ -> ‘/usr/local/lib/node_modules/.npm-i9nnxROI’ npm ERR! [Error: EACCES: permission denied, rename ‘/usr/local/lib/node_modules/npm’ -> ‘/usr/local/lib/node_modules/.npm-i9nnxROI’] < npm ERR! errno: -13, npm ERR! code: ‘EACCES’, npm ERR! syscall: ‘rename’, npm ERR! path: ‘/usr/local/lib/node_modules/npm’, npm ERR! dest: ‘/usr/local/lib/node_modules/.npm-i9nnxROI’ npm ERR! >npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! A complete log of this run can be found in: npm ERR! /Users/server/.npm/_logs/2022-04-07T11_55_42_592Z-debug-0.log HomeServer:

server$ npm audit fix —force npm WARN using —force Recommended protections disabled. npm ERR! code ENOLOCK npm ERR! audit This command requires an existing lockfile. npm ERR! audit Try creating one first with: npm i —package-lock-only npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file npm ERR! A complete log of this run can be found in: npm ERR! /Users/server/.npm/_logs/2022-04-07T11_56_55_318Z-debug-0.log HomeServer:

server$ npm audit fix npm ERR! code ENOLOCK npm ERR! audit This command requires an existing lockfile. npm ERR! audit Try creating one first with: npm i —package-lock-only npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file npm ERR! A complete log of this run can be found in: npm ERR! /Users/server/.npm/_logs/2022-04-07T11_57_15_495Z-debug-0.log HomeServer:

Источник

Does not install on Windows 10 (x64) #306

Problem

Not installing. Does not install on Windows 10(x64)

What is expected to happen?

Cordova should install.

What does actually happen?

This is what happens:
C:>npm install -g cordova
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142

added 487 packages, and audited 488 packages in 3m

30 packages are looking for funding
run npm fund for details

6 vulnerabilities (5 moderate, 1 high)

To address all issues (including breaking changes), run:
npm audit fix —force

Run npm audit for details.
npm notice
npm notice New patch version of npm available! 8.1.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g npm@8.1.2 to update!
npm notice

C:>npm audit fix —force
npm WARN using —force Recommended protections disabled.
npm ERR! code ENOLOCK
npm ERR! audit This command requires an existing lockfile.
npm ERR! audit Try creating one first with: npm i —package-lock-only
npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersTestUserAppDataLocalnpm-cache_logs2021-10-31T06_11_51_150Z-debug.log

Information

Command or Code

C:>npm install -g cordova

Environment, Platform, Device

Windows 10 (x64) Laptop Intel Corei7

Version information

Checklist

• I searched for existing GitHub issues
• I updated all Cordova tooling to most recent version
• [ x] I included all the necessary information above

The text was updated successfully, but these errors were encountered:

Источник

pm2 install gives WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. #5134

What’s going wrong?

How could we reproduce this issue?

On new Ubuntu 20 linux install:

1. Install Node 12
2. Upgrade npm using npm install -g npm
3. Install pm2 using npm install pm2 -g

Supporting information

The text was updated successfully, but these errors were encountered:

To solve this problem it is necessary to update some dependencies from pm2/io package | pm2/io repo.
The dependencies that are giving the warning are probably these @opencensus/core & @opencensus/propagation-b3 , just update to version 0.0.22 or 0.1.0 must work at least for production(final build), but that would break the build so it’s not easy as change 2 digits.

The warning is really annoying tho

P.S. There are warnings in the dev dependencies too but I don’t know if they will matter.

This library uses too many old dependencies. Is no one maintaining it anymore?

Any updates on this? I have been trying to get rid of warnings in my app and pm2 is the only one left causing issues.

@KevinNovak nop, I tried to update one time but I had some problems doing it, so I created a issue where the problem is, to ask for help but for now, there’s no update.

I did this fork but I broke a lot of things and I still don’t have the time to see it.

If that’s too annoying you could try to fix and open a PR, but I’m not sure if they will approve (are they active?).

Edit:

Actually, there is a pull request regarding this

But it was not approved yet because it has conflicts

There is an issue for the problem:

Not that someone really cares to fix it. Like me btw, that just gave in because I didn’t want to use it anymore (doesn’t have a use for my use case nowadays). And it is just a warning, not really that important for this project in specific, just annoying.

+1 here
when is solved?

@Unitech Could you please leave some information here? This 3-year old deprecated module should be updated imo.

Same here. Hope to hear your expertise on the issue.

@Unitech Any update on this issue? It’s too outdated. Hope to hear from you guy soon

warning pm2 > @pm2/io > @opencensus/propagation-b3 > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
warning pm2 > @pm2/io > @opencensus/core > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
warning pm2 > @pm2/io > @opencensus/propagation-b3 > @opencensus/core > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
[2/4] 🚚 Fetching packages.
error create-strapi-app@4.1.9: The engine «node» is incompatible with this module. Expected version «>=12.22.0

Could we get an update on this? I’ve been having this issue for over a year now. Is there some breaking change preventing package upgrades? Or is it just the risk involved? I wouldn’t mind testing a pre-release version if it helped to address this.

I downloaded the version of node 8.19.2
npm -v 8.19.2
`npm install -g @soketi/soketi
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.

changed 348 packages, and audited 349 packages in 1m

29 packages are looking for funding
run npm fund for details

1 high severity vulnerability

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details. npm audit
npm ERR! code ENOLOCK
npm ERR! audit This command requires an existing lockfile.
npm ERR! audit Try creating one first with: npm i —package-lock-only
npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-12-27T18_58_34_193Z-debug-0.log soketi start

🕵️‍♂️ Initiating metrics endpoints.

🎉 Server is up and running!
📡 The Websockets server is available at 127.0.0.1:6001
🔗 The HTTP API server is available at http://127.0.0.1:6001
🎊 The /usage endpoint is available on port 9601. `

And run. But it would be interesting to update Soketi.
Happy New Year!

Источник

Original Error Loadvirtual Requires Existing Shrinkwrap File Best Recipes

Recently Recipes

Cute chocolate «cauldrons» hold a cool, creamy orange-flavored yogurt in this recipe. The unfilled cups.

Provided by Taste of Home

Provided by Catherine McCord

This is my technique for veal demi-glace, and there’s not much to it. I’m going for a pure veal stock.

Provided by Chef John

OMG. I had to make this cake this past Sunday for my Mary Kay party.. It was a huge hit. It was also.

Provided by vicky hunt

Good food doesn’t always have to cost a fortune! Your family will love this. Full of flavor and easy.

Provided by Melissa Baldan

This is a very good potato dish , I stem baby red potatoes and smother them in real butter and parsley.

Provided by Karla Everett

Provided by á-174942

Try this Instant Pot®-friendly variation of a traditional bean stew from the Portuguese region of Azores.

Provided by Ryan C Mathews

Provided by Florence Fabricant

A unique twist on a classic white chocolate fudge recipe! While quick and easy to prepare, Bruce’s®.

Provided by Bruce’s Yams

Sure you can make a quick Chicken Pot Pie using already made pie crust, canned soups, vegetables and.

Provided by Julia Ferguson

This delicious red velvet pound cake is the perfect combination of flavors. Make sure the cake has cooled.

Provided by Taste of Home

Dis is da toe curlin Texicajun hybrid of a classic dish. This will put a smile on everyone’s face that’s.

Provided by Lupe Boudreaux

Provided by Kemp Minifie

This is a tender and delicious baked pork chop recipe, with an Italian flair.

Источник

5 React Native Expo Errors and Their Solutions

Programming can be difficult. Especially, when trying to code an android/iOS app with React Native when you know nothing about JavaScript.

There are a lot of spontaneous errors I ran into while creating my first react native project. To avoid you the trouble of searching them all up in your browser, scrolling through articles, and trying out those little command prompt/terminal snippets until something else happens, I saved you two or more frustrating days by putting them all in this article.

1. npm ERR! code ENOENT

npm failed to open a file or directory needed to execute the command. In my case, the command was ‘npm start’.

I fixed this error by changing the project directory. I named my project ‘first-project’ and the package.json was in there. I was trying to execute ‘npm start’ from my project’s folder. If this is the problem for you, change the project directory with ‘cd’

If not, you are missing packages! What’s the solution?

Try clearing your npm cache.

In files, on your computer, go to

and delete the npm file (and npm cache if there is one). After deletion, in the command prompt/terminal run

If npm install fails with code ENOENT try updating you’re npm version,

removing node modules and package-lock.json,

and reinstalling dependencies

Find more solutions on this StackOverflow page.

2. npm ERR! code ENOLOCK

Are you seeing something like this

I did too when I ran ‘npm audit’. I tried a couple of things.

First, I tried clearing my npm cache again:

, but that solution does not work all the time. Second, I tried adding a new package.json and package-lock.json file in the directory:

I thought that fixed the nasty ENOLOCK error, but it didn’t. All creating a package.json and package-lock.json file did was create files; however, the error lingered.

What worked for me? I restarted my Visual Studio Code window. Once I opened a new terminal, the error was gone. I saved you thirty minutes of frustration with this one. You’re welcome.

Find more solutions on this StackOverflow page.

3. running scripts is disabled on this system

Yep, another one. I urge you not to slam your computer shut and walk off. Here is the solution first.

First, let me ask if you got this error

when trying the command ‘expo —version’ in Visual Studio Code’s terminal? Try opening up PowerShell as administrator and running:

If that fails, try

Running ‘expo start’ in Visual Studio Code’s terminal is not authorized by default. Try running ‘expo start’ or ‘expo —version’ in your command prompt/terminal on your computer (not vscode).

Find more solutions on this StackOverflow page.

4. Error:0308010c:digital envelope routines::unsupported

For this one, I had to install nvm, which is a Node Version Manager (nvm). The problem was the version of node I was using (18.12.1). If you downloaded the most recent one, you would get this error, like I did. Try downgrading the node version.

I tried node 14.20.1, but this version is too old for expo, so I uninstalled that one and tried 16.18.1, which is working for me.

For help downgrading your node version with nvm, check out this StackOverflow page.

To save you more time, here is a YouTube video that helped me downgrade my node version.

5. Error from chokidar (c:): Error: EBUSY: resource busy or locked, lstat ‘c:DumpStack.log.tmp’

This EBusy error is the last one I am covering in this article. If you want me to cover more errors in future articles, leave a comment.

Also, if this article saved you time and prevented frustrations, help others by sharing.

If you are getting ‘Error from chokidar…’ this might not be your original error. Look through the terminal again and find the error message before this one. Chances are there is a mistake in package.json or App.js.

Find more solutions on this StackOverflow page.

Thank you for scrolling. Remember, share this article if you found it useful. Comment more solutions to further help others and if you want more articles on common programming errors.

Источник

Current Situation

I’m installing Homebridge for the first time on mac mini (with M1 chip).
Installed node.js without an issue.
Ran the install script for homebridge and got some warning messages:

npm WARN deprecated class-transformer@0.3.2: This release contains a breaking change from 0.3.1 but otherwise functions properly. Please read the changelog on Github to learn more.
…
5 high severity vulnerabilities

To address all issues (including breaking changes), run:
npm audit fix —force

…

I ran «npn audit fix —force» … but I think that didn’t work

Logs

npm WARN deprecated class-transformer@0.3.2: This release contains a breaking change from 0.3.1 but otherwise functions properly. Please read the changelog on Github to learn more.

added 434 packages, and audited 435 packages in 4m

68 packages are looking for funding
  run `npm fund` for details

5 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm notice 
npm notice New minor version of npm available! 8.1.0 -> 8.2.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.2.0
npm notice Run npm install -g npm@8.2.0 to update!
npm notice 
------------------
and here's the log after trying to do the "npm audit fix --force":

0 verbose cli [
0 verbose cli   '/usr/local/bin/node',
0 verbose cli   '/usr/local/bin/npm',
0 verbose cli   'audit',
0 verbose cli   'fix',
0 verbose cli   '--force'
0 verbose cli ]
1 info using npm@8.1.0
2 info using node@v16.13.0
3 timing npm:load:whichnode Completed in 0ms
4 timing config:load:defaults Completed in 0ms
5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 0ms
6 timing config:load:builtin Completed in 1ms
7 timing config:load:cli Completed in 0ms
8 timing config:load:env Completed in 0ms
9 timing config:load:project Completed in 1ms
10 timing config:load:file:/Users/stephenfox/.npmrc Completed in 0ms
11 timing config:load:user Completed in 0ms
12 timing config:load:file:/usr/local/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:validate Completed in 0ms
15 timing config:load:credentials Completed in 1ms
16 timing config:load:setEnvs Completed in 1ms
17 timing config:load Completed in 4ms
18 timing npm:load:configload Completed in 5ms
19 timing npm:load:setTitle Completed in 5ms
20 timing npm:load:setupLog Completed in 0ms
21 timing config:load:flatten 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 warn using --force Recommended protections disabled.
26 timing npm:load Completed in 13ms
27 timing arborist:ctor Completed in 0ms
28 timing command:audit Completed in 3ms
29 verbose stack Error: loadVirtual requires existing shrinkwrap file
29 verbose stack     at Arborist.loadVirtual (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/load-virtual.js:62:18)
29 verbose stack     at async Arborist.audit (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/audit.js:25:18)
29 verbose stack     at async Audit.audit (/usr/local/lib/node_modules/npm/lib/audit.js:66:5)
30 verbose cwd /Users/stephenfox
31 verbose Darwin 21.1.0
32 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "audit" "fix" "--force"
33 verbose node v16.13.0
34 verbose npm  v8.1.0
35 error code ENOLOCK
36 error audit This command requires an existing lockfile.
37 error audit Try creating one first with: npm i --package-lock-only
38 error audit Original error: loadVirtual requires existing shrinkwrap file
39 verbose exit 1

Configuration

{
    "bridge": {
        "name": "Homebridge 7E24",
        "username": "0E:A5:8C:B3:7E:24",
        "port": 51868,
        "pin": "191-69-099"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        }
    ]
}

Environment

• OS: 12.0.1
• Software: Homebridge 1.3.8
• Node: v16.13.0
• npm: 8.1.0

Process Supervisor

hb-service

Additional Context

I think Homebridge is working … submitting this as I’m installing …

Ответы
1

Другие вопросы по теме