NPM5 generate package-lock from existing node_modules? (migrating from Yarn, using @types)

[dwasyluk]

We're migrating a project from using Yarn for deterministic dependency locking back to pure NPM now that lockfiles are supported in a more deterministic manner. Is there a way to generate package-lock.json from an existing node_modules? npm install which auto-gens the lockfile is pulling down new versions which the existing Yarn.lock file prevents, but I can't find any good material on how to migrate back to pure npm while maintaining the locked versions.

I was thinking using npm shrinkwrap would do it but I ran into npm/npm#16812; installed canary and now npmc shrinkwrap generates a file without errors but none of the @types entries are present (listed under devDependencies in package.json). How can I generate a complete package-lock.json with all @types etc?

[gibfahn]

I don't think that's possible currently. Seems like it'd have to be a feature request for npm/npm.

[vkozubal]

Have you tried to npm shrinkwrap and then just rename npm-shrinkwrap.json to package-lock.json?

[boazrymland]

What @vkozubal worked for me. In fact, you don't really need to rename since npm-shrinkwrap.json share the same syntax as package-lock.json and will take precedence over it.
Just do:

• Have a working tree, with working node_nodules.
• Delete all lock files: package-lock.json and npm-shrinkwrap.json
• Run "npm shrinkwrap". This will create the shrinkwrap file.

Now you're done. To check it, simply move aside the node_modules tree. Then run npm install and it will use the newly created shrinkwrap file (produced in the last step above) to recreate the same node_modules tree.

[gireeshpunathil]

closing as answered, please re-open if the proposed solution does not work for you, thanks!

[IgorDePaula]

Its not working for me =/

[adyz]

Renaming npm-shrinkwrap.json to package-lock.json does not work in all cases!

[michau-krakow]

Can you give examples, please?

[alvaropaco]

@adyz is right! The npm-shrinkwrap.json miss integrity, for example.

[Bassem95]

them same problem in 2020

[vkurlyan]

The same problem in 2021. Could somebody reopen this ticket?

[Piturnah]

Same problem in 2022