jsc.paths didnt work when file is not on root

[aelbore]

Describe the bug
jsc.paths didnt work when file is not on root folder

Input code
File => packages/a/src/index.ts
code =>

export function displayA() {
  return 'Display A'
}

File => src/index.ts

import { displayA } from '@print/a'

console.log(
  `${displayA()}`
)

File => package.json

{
  "name": "swc-tsconfig-paths",
  "main": "index.ts",
  "scripts": {
    "swc": "swc-node ./src/index.ts",
  },
  "devDependencies": {
    "@swc/core": "^1.2.80",
    "@swc/register": "^0.1.7"
  }
}

Error

Config

{
  "jsc": {
    "parser": {
      "syntax": "typescript"
    },
    "target": "es2020",
    "paths": {
      "@print/a": [ "packages/a/src/index.ts" ],
    }
  },
  "module": {
    "type": "commonjs"
  }
}

Expected behavior
A clear and concise description of what you expected to happen.
Should work properly and recognise the paths

Version
The version of @swc/core: 1.2.80

Additional context
Add any other context about the problem here.

[kdy1]

Seems like duplicate of #2050

[aelbore]

@kdy1 sure thanks apologies i didnt see it,
by the way if you put the src/index.ts to root folder index.ts in your package.json swc-node index.ts >>> it works as expected

[aelbore]

@kdy1 this works if you set baseUrl to src then adjust the paths
Maybe its a matter of adjusting the baseUrl

by the way uses swc: 1.2.88

This does not work

{
  "jsc": {
    "parser": {
      "syntax": "typescript"
    },
    "target": "es2020",
    "baseUrl": ".",
    "paths": {
      "@print/a": [ "./packages/a/src/index.ts" ]
    }
  },
  "module": {
    "type": "commonjs"
  }
}

This will works

{
  "jsc": {
    "parser": {
      "syntax": "typescript"
    },
    "target": "es2020",
    "baseUrl": "./src",
    "paths": {
      "@print/a": [ "../packages/a/src/index.ts" ]
    }
  },
  "module": {
    "type": "commonjs"
  }
}

[aelbore]

@kdy1 another thing is if you set the type to module in the package.json it will not work

[aelbore]

@kdy1 I know now, the baseUrl should be where the code will use, then the paths should adjust to the baseUrl dynamically

for example
if i add a folder in the src/folder-b the baseUrl should be src/folder-b

[kdy1]

@aelbore Current implementation uses baseUrl, and paths is adjusted based on it.
It sounds like the current implementation is correct, but I don't think it's the case.

[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.