Christian Schulz

But this would not fix the issue with ESM only libraries like we would have. I am trying to create a repro the next days.

After some digging I can confirm the issue is similar to the node-fetch import with most recent version. As long an imported library is ESM, it is not supported yet.

This doesn't work for the appdata folder. We are already using `export CYPRESS_CACHE_FOLDER="/var/lib/jenkins/.cache/cypress"`

``` Platform: linux-x64 (Red Hat Linux - 8.8) Cypress Version: 12.17.0 ```

Yes I can confim the paths are based on the HOME variable. I would like to suggest that there should be also an environment variable to override this behavior because...

After some research by my collegue it should be `Cypress.WaitXHR` instead of HTMLElement.

It works for me, but it doesn't satisfy my need for a second tsconfig.json file. At local development we are building everything from scratch even the shared cypress parts. On...

Even it won't be part of the framework itself, it would be nice to have an extension point that we can maintain such rules in community hand, see #48117

Just my two cents about this issue, the `Event` type is part of the router package and furthermore it could be possible you need also a type guard to be...

I have tried it with lodash-es and there is the same issue. My adjusted jest.config.js: ``` const { pathsToModuleNameMapper } = require('ts-jest'); const { paths } = require('./tsconfig.json').compilerOptions; // eslint-disable-next-line...