`jsc.paths` transform produces absolute paths (Windows only)

[colin969]

Describe the bug

jsc.paths transformation produces absolute paths instead of relative paths. This only occurs on Windows, the paths are relative when run on Linux.

Example project: https://github.com/colin969/swc-issue-01-colin969

npm run build for building

Input code

No response

Config

{
  "exclude": [
    "node_modules/**"
  ],
  "module": {
    "type": "commonjs",
    "strict": true,
    "noInterop": true
  },
  "jsc": {
    "target": "es2018",
    "baseUrl": ".",
    "paths": {
      "@modules/import": ["./src/import.ts"]
    },
    "parser": {
      "syntax": "typescript",
      "decorators": true
    },
    "transform": {
      "decoratorMetadata": true
    }
  }
}

Playground link

No response

Expected behavior

./build/main.js output of

"use strict";
const _import = require("./import");
console.log(_import.test);

Actual behavior

./build/main.js output of

"use strict";
const _import = require("C:/Data/Projects/swc-bug/src/import");
console.log(_import.test);

Where C:/Data/Projects/swc-bug is the project path

Version

1.2.211

Additional context

No response

[tiavina-mika]

Facing the same issue. Have you found a solution?

[colin969]

Nope, had to go back to ttypescript and only use SWC for the frontend w/ webpack.

[kdy1]

Seems like this is fixed. I bought a Windows device and could reproduce this, but I couldn't reproduce it with a latest @swc/core. I'll close this issue with a PR adding a test for it

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.