Skip to content
This repository was archived by the owner on Mar 19, 2026. It is now read-only.

feat: add resolve.tsconfigPaths option to resolve with tsconfig paths#277

Merged
sapphi-red merged 12 commits into
rolldown-vitefrom
feat/support-tsconfig-paths
Jun 27, 2025
Merged

feat: add resolve.tsconfigPaths option to resolve with tsconfig paths#277
sapphi-red merged 12 commits into
rolldown-vitefrom
feat/support-tsconfig-paths

Conversation

@sapphi-red
Copy link
Copy Markdown
Member

@sapphi-red sapphi-red commented Jun 19, 2025

Description

Adds resolve.tsconfigPaths option that enables tsconfig paths resolution. This option requires experimental.enableNativePlugin to be set to 'resolver' or true.

Currently this feature only supports basic cases. If the tsconfig.json uses references/include/exclude, it won't work as expected.

refs rolldown/rolldown#5004

@sapphi-red
Copy link
Copy Markdown
Member Author

@sapphi-red
Copy link
Copy Markdown
Member Author

sapphi-red commented Jun 19, 2025

  • rakkas, nuxt fails with native resolver

@sapphi-red
Copy link
Copy Markdown
Member Author

Run with native resolver + tsconfig paths support: https://github.com/vitejs/vite-ecosystem-ci/actions/runs/15748739254

@sapphi-red
Copy link
Copy Markdown
Member Author

  • unocss, vitest, vuepress fails with tsconfig paths support

@sapphi-red

This comment was marked as resolved.

@sapphi-red
Copy link
Copy Markdown
Member Author

@sapphi-red
Copy link
Copy Markdown
Member Author

@sapphi-red sapphi-red changed the title feat!: enable resolver native plugin by default feat: add resolve.tsconfigPaths option to resolve with tsconfig paths Jun 26, 2025
@sapphi-red sapphi-red marked this pull request as ready for review June 27, 2025 07:42
@sapphi-red sapphi-red merged commit 5f3ce8b into rolldown-vite Jun 27, 2025
50 of 52 checks passed
@sapphi-red sapphi-red deleted the feat/support-tsconfig-paths branch June 27, 2025 07:54
@sapphi-red sapphi-red mentioned this pull request Jun 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant