Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`fix className normalization` (#2774) causes regression removing some class names
See original GitHub issueHi! I think #2774 is causing a regression, which results in some class names, specifically for Material Icons/RMWC, being removed, and some JS functionality seems broken, too(?). I also verified that reverting to v10.5.2 resolves the regression.
Reproduction
Repo (specific commit): https://github.com/4cm4k1/personal-website/tree/2d4d593ba366b85baa33e05819678491897e776c Deployment (specific commit): https://personal-website-neqqptm34.vercel.app/ Versions:
├── preact@10.5.3
├── preact-render-to-string@5.1.10
Steps to reproduce
- Checkout repo at
2d4d593ba366b85baa33e05819678491897e776c yarn installyarn dev(exists on prod deployments, too, see above)- Check
localhost:3000(or deployment)
Expected Behavior
Material Icons/RMWC class names are outputted and display properly.
Actual Behavior
Material Icons/RMWC class names are omitted, causing improper display and possibly(?) stops JS.
Thank you!!!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’ve just published
10.5.4which includes a fix for this issue. Can’t reproduce it anymore 🎉I ended up just reverting to 10.5.2 in the meantime, which doesn’t seem to have the bug. I guess I must not be fully understanding the initial issue, but 10.5.3 introduces a “fix” for classnames in
preact/compat, but from what I can see classnames were working in 10.5.2 and are broken in 10.5.3.