Fix recent build failures due to Webpack version conflicts #571
Conversation
This file contains 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
- Force use of `0.2.1-alpha.2` to prevent Webpack dependency conflicts in Cheveron and handleRichTextBoxKeyEventNavigation (we downgraded Webpack in the latest version to prevent Live Apps from breaking) - Regenerate `package-lock.json` files because it was still referencing `0.2.1-alpha.3` which has a newer version of Webpack
hao2018
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We recently updated Webpack but this is causing downstream packages to fail to build. As a result we decided to downgrade Webpack in the next release. However some packages are referencing the latest release, causing build failures due to Webpack versioning conflicts
Changes:
0.2.1-alpha.2to prevent Webpack dependency conflicts in Cheveron and handleRichTextBoxKeyEventNavigation (we downgraded Webpack in the latest version to prevent Live Apps from breaking)package-lock.jsonfiles because it was still referencing0.2.1-alpha.3which has a newer version of WebpackTested locally via
npm ci && npm test && npm run build