Clarify Next.js example #5
Closed
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
|
Thanks @leerob! I've been working on a rework of the landing page (which included this older version). I'll go ahead and drop it from the references list to align with your PR shortly. |
addyosmani
added a commit
that referenced
this pull request
Nov 3, 2023
This drops the older Next 12.x version. It's primary deltas to the current more up to date version are that it features authentication and more features.
|
Closed in 3c3b3a9 |
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.
Thanks for updating with that new example! We can help review that one to make sure it's showing the correct patterns. It's already much better than the previously very outdated one which I would not recommend. I don't think it's worth including there here, as it will start folks on the wrong foot and not represent Next.js well.