No ref/dr 3347/next 15 caching spike #272
Open
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Ticket:
This PR does the following:
install experimental version of next 15:
npm i next@canaryUpdate node version (requirement to run a node version greater than 18.17.1, which was what was I was running locally):
npm i n stablenvm use v19.9.0I'm Now using v19.9.9 on my local machine.
npm inpm run dev**Note !important: to go back to the other branches that aren't running next 15/next 15 canary, you need to switch your local node version back to 18.17 or whatever and reinstall the
node_modulesfolder.. otherwise you'll run into issues with building/running the app.Open Questions
How has this been tested? How should a reviewer test this?
Accessibility concerns or updates
Checklist: