-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downgrade lrucache #36
Comments
Also add |
Fix #36 * Downgrade lru-cache * Add exports.default * Remove exports.browser * Remove bundle-browser
@Evertvdw @heidfeld @Bladesheng @consultor5aluiz Hi, all. Pre-published a beta version for testing. npm: "overrides": {
"@asamuzakjp/css-color": "^2.8.3-b.1"
}, yarn: "resolutions": {
"@asamuzakjp/css-color": "^2.8.3-b.1"
}, |
or pnpm: "pnpm": {
"overrides": {
"@asamuzakjp/css-color": "^2.8.3-b.1"
}
} Works great 👍. I'm no longer getting the original error |
And please let me know the results. |
Thanks for your contribution |
Checklist
|
@asamuzaK Yes I can confirm that with that beta version the error I initially reported no longer occurs. |
@asamuzaK I can also confirm the beta resolves the issue reported in jsdom/cssstyle#181 for me in Vitest |
Someone please check with jest? |
@Evertvdw @heidfeld @Bladesheng @consultor5aluiz @NicoPennec @crutchcorn @aryaemami59 Hi, all again. Released a new beta version for testing.
Add the following fields to package.json, run tests and/or anything else you want to check, and see if it works as expected. npm: "overrides": {
"@asamuzakjp/css-color": "^2.8.3-b.2"
} yarn: "resolutions": {
"@asamuzakjp/css-color": "^2.8.3-b.2"
} pnpm: "pnpm": {
"overrides": {
"@asamuzakjp/css-color": "^2.8.3-b.2"
}
} And please, please someone confirm with jest. Thanks. |
Works fine in our case with |
Released v3.0.0 |
Released v2.8.3 for backport. I have already submitted a PR to cssstyle, but if you really can't wait until jsdom and cssstyle to be updated, you can uninstall jsdom and reinstall it, then v2.8.3 will be applied. |
see jsdom/cssstyle#181
The text was updated successfully, but these errors were encountered: