-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Fix for 3 vulnerabilities #161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -81,12 +81,12 @@ | |||||
| "jss": "^10.0.3", | ||||||
| "jss-plugin-template": "^10.0.3", | ||||||
| "jss-rtl": "^0.3.0", | ||||||
| "lodash": "^4.17.15", | ||||||
| "lodash": "^4.17.23", | ||||||
| "lz-string": "^1.4.4", | ||||||
| "markdown-to-jsx": "^7.0.0", | ||||||
| "marked": "^1.0.0", | ||||||
| "material-ui-popup-state": "^1.4.1", | ||||||
| "next": "^9.5.0", | ||||||
| "next": "^10.0.6", | ||||||
| "notistack": "^1.0.0", | ||||||
| "nprogress": "^0.2.0", | ||||||
| "postcss": "^8.0.6", | ||||||
|
|
@@ -117,7 +117,7 @@ | |||||
| "stylis-plugin-rtl": "^1.0.0", | ||||||
| "stylis": "^3.5.4", | ||||||
| "webfontloader": "^1.6.28", | ||||||
| "webpack": "^4.41.0", | ||||||
| "webpack": "^5.0.0", | ||||||
|
||||||
| "webpack": "^5.0.0", | |
| "webpack": "^4.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrading Next.js from version 9.5 to 10.0 is a major version upgrade with breaking changes. Next.js 10 introduced changes to the build output, image optimization, and other features. While Next.js 10 does support webpack 5, it requires opting in via the
future.webpack5: trueconfiguration option in next.config.js. Without this configuration or without migrating to the default webpack 5 settings when they became default in later versions, the build may fail. Additionally, the PR description indicates that yarn.lock failed to update, which means dependencies may not be properly resolved.