How to force lock-file integrity checksum recalculations | Bun | Page 1

molten merlin Dec 25, 2024, 7:54 PM

#

I have created a script which migrates our Yarn Berry yarn.lock into a bun.lock. The only remaining challenge is the checksum. It seems Yarn's checksum is base64 vs Bun's SHA-512, but they're hashed on different things so a conversion cannot work.

Setting the Bun integrity checksum to "" gets an install to execute, but unfortunately I cannot find a way to force Bun to recalculate new checksums for all existing packages.

I do not wish to nuke my yarn.lock as we have quite a mature monorepo project and, quite frankly, a nuke introduces a seemingly endless list of bugs/regressions.

severe wave Dec 25, 2024, 8:46 PM

#

I can't imagine this is easier than to generate a new lock-file 😯

woven mason Dec 25, 2024, 8:53 PM

#

@molten merlin the lockfile's integrity values come directly from npm's registry API. We don't generate these ourselves. It's possible yarn berry is generating it on their end.

Fortunately, if the dependencies are on npm, you could copy paste the values from npm's registry api.

#

If you want to recalculate it, you could do --force but I think that would also invalidate versions in the lockfile

#

but it might get you closer

molten merlin Dec 25, 2024, 9:04 PM

#

severe wave I can't imagine this is easier than to generate a new lock-file 😯

We have a ~5 year old monorepo with many dozen workspace projects. Nuking the lock file causes a ton of type errors. Even if we resolve those, there is a worry around logical regressions that may be hard to pick-up.

#How to force lock-file integrity checksum recalculations