Viktor Luft

@WipeAir I see. This is then the root cause of the problem 🤔 Including the following CSS rule into our shipped CSS avoids these CSP issues. Maybe you can add...

Sure. - Number of spec files: 9 - Total tests: 12 - Cypress-Config (`cypress-audit` with version: 1.1.0) ```ts import { defineConfig } from 'cypress'; import { readFileSync } from 'fs';...

I've tested it now from my local machine (MacOS). Looking at the debug output, I cannot send you the output with good conscience, because it contains a lot of sensible...

@mjhenkes Yes, I can only reproduce this within GitHub Actions. Didn't try it within a docker container yet. Will try to find some time to test it within a container....

## Preparation `Dockerfile`: ``` FROM node:16 RUN apt-get update # see https://docs.cypress.io/guides/continuous-integration/introduction#Machine-requirements RUN apt-get install -y libgtk2.0-0 libgtk-3-0 libgbm-dev libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2 libxtst6 xauth xvfb RUN npm i...

In GitHub Actions we were running on Node > 16 running into these performance issues. And the used machine resources are pre-configured but very powerful 😥

I ran into exactly the same issue with ```js transform: { "\\.tsx?$": "@sucrase/jest-plugin" }, ``` in my Jest config and the default coverage provider being "babel". But I cannot tell...

I like the idea of just adding those comments here, but doesn't this require to update the source maps, too? 🤔 I guess, it requires some investigation 😅

I tested it again with - `"@sucrase/jest-plugin": "^3.0.0"` - `"sucrase": "^3.28.0"` The issue doesn't appear for me anymore 🙃

I would like to push for a build-in option here as well. My use case are "[Cypress Component Tests](https://docs.cypress.io/guides/component-testing/overview)", which runs using the Vite dev server. Since all test files...