Skip to content
forked from vitejs/vite

docs: document resolve.alias[].customResolver deprecation in migration guide#14

Merged
sapphi-red merged 2 commits intorefactor/deprecate-customResolver-in-resolve-aliasfrom
copilot/add-migration-guide-change
Feb 3, 2026
Merged

docs: document resolve.alias[].customResolver deprecation in migration guide#14
sapphi-red merged 2 commits intorefactor/deprecate-customResolver-in-resolve-aliasfrom
copilot/add-migration-guide-change

Conversation

Copy link
Copy Markdown

Copilot AI commented Feb 3, 2026

The customResolver option in resolve.alias[] was deprecated in the codebase but not documented in the migration guide.

Changes

  • Added deprecation entry to "Other Related Deprecations" section noting that resolve.alias[].customResolver will be removed in a future version
  • Included migration path: use a custom plugin with resolveId hook instead

This aligns the documentation with the existing runtime warning and TypeScript deprecation annotations.

Original prompt

add this change to migration guide


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: sapphi-red <49056869+sapphi-red@users.noreply.github.com>
Copilot AI changed the title [WIP] Add change to migration guide docs: document resolve.alias[].customResolver deprecation in migration guide Feb 3, 2026
Copilot AI requested a review from sapphi-red February 3, 2026 02:42
@sapphi-red sapphi-red marked this pull request as ready for review February 3, 2026 02:48
@sapphi-red sapphi-red merged commit 9c0078e into refactor/deprecate-customResolver-in-resolve-alias Feb 3, 2026
@sapphi-red sapphi-red deleted the copilot/add-migration-guide-change branch February 3, 2026 02:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants