@graphql-codegen/cli

#10956 cec9c1c Thanks @eddeee888! - Fix dynamically-loaded plugins/presets in ESM builds. Previously, ESM used the bare module specifier without resolving it relative to the consuming project first, so a plugin only loaded if it happened to be reachable from the CLI package's own node_modules. Resolving it the same way the CJS build already does (relativeRequire.resolve(mod)) fixes that, but the resolved absolute path also has to be converted to a file:// URL (pathToFileURL(...).href) before being passed to import() — otherwise, on Windows, the loader misparses a raw path like C:\... as a c: protocol scheme and throws ERR_UNSUPPORTED_ESM_URL_SCHEME.

#10966 3029b60 Thanks @eddeee888! - Fix lifecycle hook scripts (e.g. hooks: { afterAllFileWrite: ['prettier --write'] } }) failing on Windows when the file paths passed to them contain a backslash or other POSIX shell-special character. Hook arguments were always quoted using POSIX single-quoting, but child_process.exec() runs through cmd.exe on Windows by default, which doesn't strip single quotes — so the hook script received the literal quote characters as part of its argument and failed to find the file. Arguments are now quoted per-platform: POSIX quoting stays unchanged elsewhere, and Windows arguments are wrapped in double quotes only when they actually need it, matching cmd.exe's own convention.

#10959 7dffaae Thanks @eddeee888! - Fix the CLI reporting success (exit code 0) when a generates output's preset can't be resolved. The error was shown in the terminal but never counted toward the run's failure state, so allowPartialOutputs: false (the default) never took effect for this case.

#10935 fb1a7c4 Thanks @eddeee888! - dependencies updates:

• Updated dependency @graphql-tools/code-file-loader@^8.1.39 ↗︎ (from ^8.1.28, in dependencies)

#10942 57c3e7b Thanks @eddeee888! - dependencies updates:

• Updated dependency @graphql-tools/merge@^9.2.4 ↗︎ (from ^9.0.6, in dependencies)

#10942 57c3e7b Thanks @eddeee888! - Bump @graphql-tools/merge from ^9.0.6 to ^9.2.4.

#10935 fb1a7c4 Thanks @eddeee888! - Fix a Windows-specific import() failure on absolute paths when loading a schema/document from a .js/.cjs/.mjs file (via @graphql-tools/code-file-loader), and when loading modules passed to that loader's own require option. Node's dynamic import() rejects raw absolute Windows paths (the drive letter is parsed as a URL scheme). Fixed by bumping @graphql-tools/code-file-loader to 8.1.39, which contains the upstream fix (ardatan/graphql-tools#8421).

#10936 9521c0c Thanks @eddeee888! - Fix watch mode's generated ignore glob patterns using the platform path separator (\ on Windows), which @parcel/watcher never matched, so generated output files were watched (and could re-trigger builds) instead of being ignored. Ignore patterns are now always forward-slash, as @parcel/watcher expects.

Also fixes the test suite's TempDir.clean() helper on Windows, where rimraf.sync() rejected its own glob-style cleanup pattern as containing illegal path characters; now passes { glob: true }. This is a test-only change (tests/utils.ts is not part of the published package) included here since it was needed to get the suite green on Windows alongside the watch-mode fix.