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:
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
Tested locally via npm ci && npm test && npm run build
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