Use MD5 hash for LQIP class name generation#2446
Conversation
🦋 Changeset detectedLatest commit: 625eff5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
simonihmig
left a comment
There was a problem hiding this comment.
Thanks for working on this!
Code looks good, but there are some CI failures to fix:
- a weird eslint error, but seems related to import order
- some test expectations here
- also found some vitest snapshots in the vite-plugin and webpack packages' tests referring to
ri-dyn-*classes which likely need to be updated
You can run the test suites of a package by calling pnpm turbo test.vitest inside the package folder. Let me know if you need help fixing those!
|
@simonihmig Things should work better now. That |
|
@jaroel thanks for updating the PR! After running CI again, some of the class names in the vitest snapshots are not matching the expected ones. I wonder, are the tests passing locally for you? Or do we have an "environment issue" maybe, that the hashes generated on one machine (your local one) don't match the ones on another machine (GH CI runners)? |
|
@simonihmig Using hex digest should be more stable across machines :) |
|
@simonihmig It would be great if you could try to run them tests locally on your machine. There's something really weird going on where I can't run some webpack tests related to failing withAssertionError: Target cannot be null or undefined..
|
I was able to reproduce, but also on I'll need to investigate this! For your PR, I still see some snapshot mismatches in the vite tests, both in CI and locally. Do the test pass for you locally? |
|
|
@simonihmig Yep, locally they work just fine. |



Fixes #2441