fix: ensure TsconfigPathsPlugin is only added if tsconfig.json exists #643
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.
The release of 14.4.0 to make Webpack and ESlint aware of
pathsdefined intsconfig.jsonbreaks MFEs that have not yet adopted TypeScript, as described here. If a project does't definetsconfig.json,tsconfig-paths-webpack-pluginwill unexpectedly throw an error due to the missing file.This PR ensures
tsconfig-paths-webpack-pluginis only included inwebpack.common.config.jsif a roottsconfig.jsonfile exists for a project.Testing Instructions
npm run buildfor the example MFE app included with this project with the included./example/tsconfig.jsonfile../example/tsconfig.jsonfile, and change the@src/Appimport to./App.npm run buildfor the example MFE.