Deno 1.43.0 fails hard upon encountering lockfile with no integrity field.

[nberlette]

Attempting to use the REPL on v1.43.0 in a subfolder of a project that I just ran tests on using Deno v1.40.0. I'm greeted with the following error:

error: Unable to parse contents of lockfile. /Users/nb/work/.../deno.lock: missing field `integrity`

Seems rather brittle and backwards-incompatible :/

[bartlomieju]

Thanks for the report. How did you get that Deno version? Did you compile from source?

[dsherret]

@nberlette was the lockfile generated with jsr specifiers several months ago? That was a purposeful breaking change because JSR specifiers hadn't really landed yet and the data in the lockfile wasn't properly locked. You'll have to recreate the lockfile in this case.

[dsherret]

Ah, I just re-read the details. Yeah, that's just because JSR specifiers were in 1.40, but still under development. I wouldn't recommend using jsr specifiers with an older deno version.

[nberlette]

@bartlomieju I just ran deno upgrade --version 1.40.0 so I could temporarily benchmark some differences in decorator behavior between the current version and the version they first landed in.

@dsherret I didn't even think about that aspect that 1.40.0 landed prior to the JSR launch... thank you for pointing that out! Funnily enough, the lockfile didn't even exist before the tests I ran, and it actually never should have as the deno.json file has lock: false in it. For some reason the older version generated one anyways, and that's how I stumbled upon this issue. I haven't inspected the file, but it almost certainly would have JSR specifiers in it.

[nberlette]

Well, this seems to be quite an edge case now 😅 I can't imagine too many other people running into this scenario.

I'll wait a little bit (in case anyone has more to add) before I close this out. Thanks guys.