| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-24 | 1.9 kB | |
| September 24, 2026 source code.tar.gz | 2026-09-24 | 2.6 MB | |
| September 24, 2026 source code.zip | 2026-09-24 | 3.1 MB | |
| Totals: 3 Items | 5.7 MB | 0 | |
@graphql-codegen/testing@5.0.4
Patch Changes
-
#10979
2052509Thanks @eddeee888! - dependencies updates:- Added dependency
vitest@^4.0.0↗︎ (topeerDependencies)
- Added dependency
-
#10979
2052509Thanks @eddeee888! - AnchorvalidateTs/compileTsmodule resolution at the directory of the test being run.The file these helpers type-check exists only in memory, but TypeScript still needs a real directory to anchor Node module resolution to. The compiler host reported
''as the current directory, so nothing resolved — and every resulting diagnostic was swallowed by the blanketCannot find modulefilter, leaving generics to silently degrade toneverwith only a confusing downstream overload error to show for it.process.cwd()is not a usable anchor either: it is the repo root, and under pnpm's isolated layout a package's dependencies live in that package's ownnode_modules. The directory of the running test file is, so it is taken fromexpect.getState().testPath; calling these helpers outside a vitest test now throws instead of silently resolving from the wrong place.vitestis now declared as a peer dependency rather than relied on as a phantom one —src/index.tsalready imported it, andvalidateTsnow does too.This is an internal test-utility fix; no exported signature changes.