use lock file version 2 rather than 3 in latest deno version?

[alita-moore]

As is described here: supabase/cli#1584 the recent upgrade in lockfile version seems to be blocking me. Is there a way to tell deno to use version 2 instead for now? Downgrading deno seems to be more trouble than its worth.

[nayeemrmn]

It should auto update if you deno cache your project entrypoint.

[alita-moore]

I mean to use lockfile 2 instead of lockfile version 3. Is that possible? But if I run deno cache it does auto update to version 3, but I'd like to prevent that behavior as version 3 is causing bugs.

[nayeemrmn]

It's not possible to use v2. It's a shame to hear about the bugs, please report them. There's one related to stale npm dependencies that we know of: #20868 (comment)

[dsherret]

There's one related to stale npm dependencies that we know of: #20868 (comment)

That is unrelated to lockfile v3.

[dsherret]

@alita-moore sorry, no there's no way to do this and it would be infeasible to add an API for this. I believe supabase needs to update their deno_lockfile version (https://crates.io/crates/deno_lockfile), which should be an easy update. I'll comment on that other issue.