Philzen

Just for the lols i ran your project against the current main branch at dcfb07738, which gives: ```shell FAIL web web/src/components/ProjectCard/ProjectCard.test.tsx ● Test suite failed to run TypeError: Cannot read...

As it so happens, this started surfacing in my own project now as well. Shows up as red squiggles in VSCode *and* also in `yarn rw typecheck` – weirdly the...

Relates to #1673 (fixed via #1740)

Looks to be also related to #4834 and #4717. Maybe this could all be solved in one PR.

> paths.ts uses a different path for the new location, the old location can be removed. This had now been solved via #11864 being fixed. Will tackle the other issues...

So i found a different workaround to get rid of the error > Error: Error while loading rule '@typescript-eslint/consistent-type-imports': You have used a rule which requires parserServices to be generated....

I just added the rule `"@typescript-eslint/no-import-type-side-effects": "error"` to my project and was expecting it to also throw the error when not included in the "overrides" array. But no: it works...

~~Hooray! Just ran `rw lint` in my project with the unaltered `.eslintrc.json` against my fix branch for #11878 – and it ran w/o any hiccups :rocket:~~ ~~So this apparently was...

Not sure, but may be worth checking first if this isn't the result of a race condition due to re-instantiated apollo clients as described in #11602, so first check out...

As a thought – is pino logger output actually useful when running jest or merely a general disturbance (following the [comment here](https://github.com/pinojs/pino-pretty/issues/65#issuecomment-495664752))? Then a different approach could be to disable...