[Bug]: Jest tests failing in a NX project with Angular 19 + Openlayers 10 + Typescript 5.6

[ricardojbertolin]

Version

29.7.0

Steps to reproduce

1. Clone my repo at https://github.com/ricardojbertolin/angular-19-demo
2. npm install
3. npx nx test angular-demo
4. You should see the error come up

Expected behavior

Tests should be fine

Actual behavior

The repository I provided is just an out-of-the-box Nx project with angular. I followed this instructions: https://nx.dev/getting-started/tutorials/angular-standalone-tutorial.

I've only added the following stuff:

1. Install the latest Openlayers dependency
2. Instantiate a "DragPan" interaction on the main component constructor.

And that's it. You can see here the commit details: ricardojbertolin/angular-19-demo@4029b4c

After that, tests for this main component started to fail.
In older versions of Angular this didn't break down and worked as expected.

Additional context

No response

Environment

System:
    OS: Windows 11 10.0.22621
    CPU: (12) x64 13th Gen Intel(R) Core(TM) i7-1365U
  Binaries:
    Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: 29.7.0 => 29.7.0

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[geomatikkolga]

No solution, but I've got the same issue, commenting to keep this alive.

[huehnerlady]

Yes I have a similar issue as well, all was fine but since update to Angular 19 the tests fail with Error: Could not parse CSS stylesheet when running MatDialog.open() (@angular/material/dialog)

[aalbericio]

We are stuck at TypeScript 5.5.4 until this issue is resolved. Could you prioritize it, please?

[angelo-v]

We are also seeing the error Error: Could not parse CSS stylesheet in some tests. Using typescript 5.5.4 did not solve these.

We are also seeing generic errors like this:

Error: thrown: "ERROR"

    at _getError (/path/to/project/node_modules/jest-circus/build/utils.js:432:18)
    at Array.map (<anonymous>)
    at makeSingleTestResult (/path/to/project/node_modules/jest-circus/build/utils.js:385:38)
    at /path/to/project/node_modules/jest-circus/build/testCaseReportHandler.js:24:58
    at dispatch (/path/to/project/node_modules/jest-circus/build/state.js:67:11)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async _runTest (/path/to/project/node_modules/jest-circus/build/run.js:264:3)
    at async _runTestsForDescribeBlock (/path/to/project/node_modules/jest-circus/build/run.js:126:9)
    at async _runTestsForDescribeBlock (/path/to/project/node_modules/jest-circus/build/run.js:121:9)
    at async run (/path/to/project/node_modules/jest-circus/build/run.js:71:3)
    at async runAndTransformResultsToJestFormat (/path/to/project/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:122:21)

[rcunico]

I'm experiencing the same issue as well, and am hoping the Jest team will take a look soon!