-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Next.js: Support v14.0.0 #24593
Merged
valentinpalkovic
merged 5 commits into
storybookjs:next
from
nikospapcom:support-next-14
Oct 27, 2023
Merged
Next.js: Support v14.0.0 #24593
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3fa771c
feat: Support next@14.0.0
nikospapcom 83f4ef0
chore: Remove package-lock file
nikospapcom a27e789
chore: Revert node engine to 16
nikospapcom 715381c
Fix next/legacy/image imports for Next.js v14
valentinpalkovic c91523f
Merge branch 'next' into support-next-14
valentinpalkovic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
We cannot drop support for Node v16 with a minor release. This has to stay with v16 until we release a new major version, because we will still support Next.js 12 and 13
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.
Right, it also doesn't make sense to out of nowhere drop Node.js v16, major libraries are only now adding minimum requirement to Node.js v16; Even tho it is technically EOL. (Downstream != Upstream 🤷)
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.
@valentinpalkovic @ovflowd Thanks for the comments, totally understand this, I reverted it back to 16 🙂