Upgraded the @adobe/css-tools dependency to include the fix for parsing the @starting-style CSS feature, which was causing a missing '}' error.
Why:
The current version of @adobe/css-tools used by testing-library/jest-dom fails to parse the @starting-style CSS feature, resulting in a parsing error. The upgrade includes a fix for this issue, allowing for the correct parsing of CSS files using @starting-style.
How:
The changes were implemented by updating the package.json file to use the latest version of @adobe/css-tools which includes the fix from the PR I submitted to @adobe/css-tools (https://github.com/adobe/css-tools/pull/323).
Checklist:
[ ] Documentation
[ ] Tests (N/A due to dependency on jsdom and CSSOM updates)
What:
Upgraded the
@adobe/css-tools
dependency to include the fix for parsing the@starting-style
CSS feature, which was causing amissing '}'
error.Why:
The current version of
@adobe/css-tools
used bytesting-library/jest-dom
fails to parse the@starting-style
CSS feature, resulting in a parsing error. The upgrade includes a fix for this issue, allowing for the correct parsing of CSS files using@starting-style
.How:
The changes were implemented by updating the
package.json
file to use the latest version of@adobe/css-tools
which includes the fix from the PR I submitted to@adobe/css-tools
(https://github.com/adobe/css-tools/pull/323).Checklist:
jsdom
andCSSOM
updates)Additional Comments:
Unfortunately, I could not add a test case for the
@starting-style
feature becausejsdom 20
uses CSSOM 0.6.0 for CSS parsing, which also has a similar issue. I fixed that already in this PR (https://github.com/rrweb-io/CSSOM/pull/1), but the latest version ofjsdom
cannot be merged intojest
. See https://github.com/jestjs/jest/pull/14846#issuecomment-1885785901 for details