You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like other tools do it by having the user create the node_modules from the old packager first, and then run the tool to generate the new lockfile from the existing node_modules: https://github.com/imsnif/synp
I thought maybe deno install should just do that if there's a node_modules and no deno.lock, but I saw pnpm has a dedicated pnpm import subcommand to achieve it.
Discussed in #25814
Originally posted by alexgleason September 23, 2024
I have a node project with a lot of dependencies that I will finally move to Deno for 2.0.
But Deno creates a new deno.lock from my package.json, essentially upgrading 180 packages at once.
I have a yarn.lock. I can convert between yarn.lock and package-lock.json. Can I convert either to deno.lock?
The text was updated successfully, but these errors were encountered: