Overview - Query

query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
4a3275c1 fix(build): exclude config files from production DTS rollup (#10358) * fix(build): exclude config files from production DTS rollup The `experimentalDts` option in tsup respects the tsconfig `include` array to determine which files are in scope for DTS generation. Each package's `tsconfig.json` includes `*.config.*` for IDE support, and `tsconfig.prod.json` inherited this without overriding it. This caused `vite.config.ts` and `tsup.config.ts` to be swept into the DTS rollup, leaking `import { UserConfig } from 'vite'` into published types. Since vite references `@types/node`, this globally overrides the DOM `setTimeout` return type from `number` to `NodeJS.Timeout` for all consumers. Add `"include": ["src"]` (and `"exclude": ["src/__tests__"]` where applicable) to all `tsconfig.prod.json` files that were missing it, matching the pattern already used by query-core, react-query, preact-query, and solid-query. * chore: add changeset for DTS type pollution fix * test(build): add regression test for build tool type leaks in .d.ts files Adds scripts/verify-dts-imports.ts that scans all published .d.ts files for forbidden imports from build tools (vite, tsup, vitest) and `/// <reference types="node" />`. Wired into test:pr and test:ci to run after the build completes. * fix(build): fail fast when no .d.ts files found in verify-dts-imports * chore: add exclude for consistency in react-query-next-experimental * chore: fix log message to mention both .d.ts and .d.cts files * ci: apply automated fixes * chore: remove verify-dts-imports script and related package.json changes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: Dominik Dorfmeister 🔮 <office@dorfmeister.cc>
2 days ago by Marc-André...
Succeeded
main
4a3275c1 fix(build): exclude config files from production DTS rollup (#10358) * fix(build): exclude config files from production DTS rollup The `experimentalDts` option in tsup respects the tsconfig `include` array to determine which files are in scope for DTS generation. Each package's `tsconfig.json` includes `*.config.*` for IDE support, and `tsconfig.prod.json` inherited this without overriding it. This caused `vite.config.ts` and `tsup.config.ts` to be swept into the DTS rollup, leaking `import { UserConfig } from 'vite'` into published types. Since vite references `@types/node`, this globally overrides the DOM `setTimeout` return type from `number` to `NodeJS.Timeout` for all consumers. Add `"include": ["src"]` (and `"exclude": ["src/__tests__"]` where applicable) to all `tsconfig.prod.json` files that were missing it, matching the pattern already used by query-core, react-query, preact-query, and solid-query. * chore: add changeset for DTS type pollution fix * test(build): add regression test for build tool type leaks in .d.ts files Adds scripts/verify-dts-imports.ts that scans all published .d.ts files for forbidden imports from build tools (vite, tsup, vitest) and `/// <reference types="node" />`. Wired into test:pr and test:ci to run after the build completes. * fix(build): fail fast when no .d.ts files found in verify-dts-imports * chore: add exclude for consistency in react-query-next-experimental * chore: fix log message to mention both .d.ts and .d.cts files * ci: apply automated fixes * chore: remove verify-dts-imports script and related package.json changes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: Dominik Dorfmeister 🔮 <office@dorfmeister.cc>
2 days ago by Marc-André...
Succeeded
10358
3f0e4a57 chore: fix log message to mention both .d.ts and .d.cts files
3 days ago by Marc-André...