InfiniteXyy

I found a workaround here to use `jest` 28+, with `preact`, You can use `customExportConditions` option to force jest not to resolve the "browser" field. https://jestjs.io/docs/configuration#testenvironmentoptions-object ```json { "testEnvironmentOptions": {...

I also created a simple repo to try to reproduce this issue. https://github.com/InfiniteXyy/vitest-hang-issue In my experiment, I used the library `dompurify` and encountered the hanging issue. **What I'm sure that...

I am also looking forward to see trpc support structure only definition. The situation I encountered is: We don't use monorepo, but have many microservices. In order to avoid duplicated...

Hi, @arpowers I found that this issue might caused by `eslint-plugin-import` doesn't support flatConfig, see https://github.com/un-ts/eslint-plugin-import-x/issues/29 But we could use `@eslint/eslintrc` compact as a workaround 👇 I'm not sure if...

Hi @SukkaW You are right. Adding these settings into antfu config also makes the import/no-cycle rule work. ```ts { settings: { 'import-x/parsers': { '@typescript-eslint/parser': ['.ts'], }, 'import-x/resolver': { node: {...

> Adding `"types": ["@testing-library/jest-dom"]` to tsconfig solves this issue for me. Yes, I think it's working, but in the source code of `"@testing-library/jest-dom"` it's referencing jest, which is not so...