[Bug]: wrong tsconfig.json#paths output when bundle: false

[carlosmfreitas2409]

Version

Rslib 0.0.16

Details

When using bundle: false, the TS path aliases are not being correctly generated in the build.
When using bundle: true, it generates correctly, but it is not what I want.

• tsconfig.json

{
  "extends": "@repo/tsconfig/react.json",
  "include": ["src", "stories"],
  "compilerOptions": {
    "paths": {
      "@/*": ["./src/*"]
    }
  }
}

• rslib config
  

• rslib output
  

• build script
  rslib build

[fi3ework]

Since the request is externalized, it won't follow Rsbuild's default alias behavior(https://rsbuild.dev/guide/advanced/alias). It's better to be aligned.

[carlosmfreitas2409]

Hi @fi3ework.

Sorry, I didn't quite understand what you meant.
Are you saying to use source.alias and source.aliasStrategy in rslib config?
If so, I've tried using them too, but it didn't change anything.

[fi3ework]

source.alias or source.aliasStraategy won't make it work. The alias to an source path (which means it's dynamic after resolved) need getResolve function #238 (comment).

[Timeless0911]

web-infra-dev/rspack#7348 external function getResolve will be supported after this pr merged.

[yf-yang]

Sorry, I cannot keep up with your terminology. Does this mean that when using path aliases and building bundless DTS, the aliases would be replaced with the correct relative paths after web-infra-dev/rspack#7348 is done?

[Timeless0911]

Does this mean that when using path aliases and building bundless DTS, the aliases would be replaced with the correct relative paths after web-infra-dev/rspack#7348 is done?

For bundleless DTS, the alias redirect should be another issue, tracking in #409. You can use tsc-alias currently.