6.1.0 @adobe/css-tools crashing
envgap__testing-library__jest-dom-524
01 / FAILURE SIGNATURE
As reported upstream
SyntaxError: Named export 'parse' not found. The requested module '@adobe/css-tools' is a CommonJS module, which may not support all module.exports as named exports.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
853a3e51ba6757a34780e32953525b6142eadcf9- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
testing-library/jest-dom #524 · read the original issue
- `@testing-library/jest-dom` version: 6.1.0
- `node` version: 18
- `npm` (or `yarn`) version: yarn 3.6.0
### Relevant code or config:
n/a
### What you did:
Ran basic React tests, working fine with jest-dom@5, after updating to jest-dom@6 (this is important - NOT a clear install).
### What happened:
```
SyntaxError: Named export 'parse' not found. The requested module '@adobe/css-tools' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from '@adobe/css-tools';
const { parse } = pkg;
```
### Problem description:
The required version of @adobe/css-tools jest-dom declares, ^4.0.1, is NOT correct. In my lockfile, it has already been resolved to 4.2.0. This hasn't changed with jest-dom@6 update, because ^4.0.1 is still the desired version range. This produced the error above.
After investigation, it turned out @adobe/css-tools 4.3.0 is the first release with ESM support.
### Suggested solution:
Bump minimum @adobe/css-tools dependency to ^4.3.0.04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]