`graphql-codegen-client-preset` doesn't work with absolute path aliases in Vite on Windows

[nathan-knight]

Describe the bug
Configuring Vite with a path alias (and TypeScript) causes it to create an invalid relative path.
For instance, setting this in vite.config.ts

  resolve: {
    alias: [
      {
        find: "@test/ui",
        replacement: path.resolve(import.meta.dirname, "./src"),
      },
    ],
  },

And this in tsconfig.json:

    "paths": {
      "@test/ui/*": ["src/*"]
    },

Then importing import { graphql } from '@test/ui/gql'; causes it to throw errors like:

Failed to resolve import "./../../../../../src/gql/graphql" from "src/App.tsx". Does the file exist?

If it must internally transform it to a relative import, it should become ./gql/graphql in this case since App.tsx is in the src directory.

I created a CodeSandbox but it ends up working there while doing the equivalent locally on Windows does not.
https://codesandbox.io/p/devbox/swc-graphql-plugin-path-alias-issue-repro-2v6j8d

If I switch it to use a relative import, it works.

Expected behavior
It should work on Windows like it does on other platforms

Additional context
If I had to guess the cause, it would be that it doesn't handle Windows paths like C:\\workspace\project correctly.

[vudsen]

After studying the source code, I found using absolute path could solve this problem:

export default defineConfig({
  plugins: [
    react({
      plugins: [
        [
          '@swc-contrib/plugin-graphql-codegen-client-preset',
          {
            artifactDirectory: path
              .resolve(__dirname, './src/graphql/generated')
              .replaceAll('\\', '/'),
            gqlTagName: 'graphql',
          },
        ],
      ],
    })
  ],
  // ...
})

BTW, it's not caused by path aliases but the double backslash

[kdy1]

@claude fix it

[claude]

Claude finished @kdy1's task in 4m 58s —— View job • claude/issue-524-20260321-0029 • Create PR ➔

---

Fixing Windows path handling in graphql-codegen-client-preset

• Gather context
• Locate relevant source files (contrib/graphql-codegen-client-preset/src/lib.rs)
• Understand path handling code
• Implement fix
• Add test for Windows-style paths
• Commit and push

Root cause: The SWC plugin runs as WASM (Unix path semantics), but on Windows receives paths with backslashes like C:\Users\user\project\src\gql. Two problems:

1. PathBuf in WASM doesn't treat \ as a path separator → wrong paths
2. Path::is_absolute() returns false for Windows drive-letter paths under WASM/Unix semantics → double-prepends cwd

Fix (lib.rs):

1. Normalize all input paths (cwd, filename, artifactDirectory) by replacing \ → / before any PathBuf usage
2. Added is_absolute_path() helper that also recognises C:/... / C:\... as absolute paths

The new test (windows_absolute_paths_produce_valid_relative_import) confirms that src\App.tsx with artifactDirectory = C:\Users\user\project\src\gql correctly produces ./gql/graphql (not a broken ../../../../../src/gql/graphql). All 7 tests pass.