使用rolldown-vite 时,无法使用带别名的导入

[nailfar]

Describe the bug

在vite.config.ts 中使用别名无效;

tsconfig 配置无效

添加rolldown.config.js 无效

在源码中添加 alias 有效

Reproduction

demo

Steps to reproduce

No response

System Info

System:
    OS: Linux 6.6 Deepin 23.1 23.1
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 5.80 GB / 31.23 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 22.16.0 - ~/.config/nvm/versions/node/v22.16.0/bin/node
    Yarn: 1.22.22 - ~/.config/nvm/versions/node/v22.16.0/bin/yarn
    npm: 10.9.2 - ~/.config/nvm/versions/node/v22.16.0/bin/npm
    pnpm: 10.14.0 - ~/.config/nvm/versions/node/v22.16.0/bin/pnpm
  Browsers:
    Chrome: 138.0.7204.92
  npmPackages:
    @vitejs/plugin-basic-ssl: ^2.1.0 => 2.1.0 
    @vitejs/plugin-vue: ^6.0.1 => 6.0.1 
    @vitejs/plugin-vue-jsx: 5.0.0 => 5.0.0 
    rolldown-vite:  7.1.13

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs and the Rolldown-related guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

• This is not a bug since the behavior is same with the non-rolldown Vite. When loading the config, (non-rolldown) Vite does not use tsconfig paths so the behavior is expected.
• Adding rolldown.config.ts does not change the behavior because Vite's config loader doesn't read that. If Vite automatically uses that, it will be a surprising behavior because I don't think most users would control the behavior of loading the config via a config. (What would you do if you want to configure the behavior for the rolldown config?)
• Since "paths should only be used to inform TypeScript that another tool has this mapping and will use it at runtime or when bundling", I don't think respecting paths automatically should be the default behavior. That causes the problem of "how can user enable the feature?".

[sapphi-red]

I'm closing this for now, as I don't think there's a way to achieve this.