docs(guides): add tsconfig-paths-webpack-plugin migration diff#8191
Merged
alexander-akait merged 2 commits intowebpack:mainfrom Apr 14, 2026
Merged
docs(guides): add tsconfig-paths-webpack-plugin migration diff#8191alexander-akait merged 2 commits intowebpack:mainfrom
alexander-akait merged 2 commits intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexander-akait
approved these changes
Apr 14, 2026
Contributor
Author
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a brief migration diff to the TypeScript guide showing how to switch from tsconfig-paths-webpack-plugin to the native resolve.tsconfig option. The docs previously mentioned that the plugin was replaced, but didn't actually show users how to update their webpack config or remind them to uninstall the package.
What kind of change does this PR introduce?
Documentation improvement.
Did you add tests for your changes?
N/A (Documentation update only).
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
The migration path for resolve.tsconfig is now fully documented in the TypeScript guide as a result of this PR.
Use of AI
NO