-
Notifications
You must be signed in to change notification settings - Fork 176
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
feat(next-drupal, starters-*) - Add Next 15 support #824
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
@yobottehg is attempting to deploy a commit to the Chapter Three Team on Vercel. A member of the Team first needs to authorize it. |
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.
Thanks for the contribution @yobottehg! Provided some inline feedback, but this is most of the way there from my perspective.
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.
Just about there! From my perspective this just needs to go back to using the custom link component (see comments inline) and also needs to have a merge conflict resolved, and then it is good to go.
All requested changes addressed |
# Conflicts: # yarn.lock
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.
Thanks for all the work on this @yobottehg !
This pull request is for: (mark with an "x")
examples/*
modules/next
packages/next-drupal
starters/basic-starter
starters/graphql-starter
starters/pages-starter
GitHub Issue: #811
Describe your changes
After reading through https://nextjs.org/docs/app/building-your-application/upgrading/version-15#async-request-apis-breaking-change I decided to not add the "workaround" to also support Next.js 14 because:
The Changes for<Link>
inside the Pages router starter is because the types did not work anymore with the pages router and react 19. I could not find a workaround. Therefore I just removed the custom "non-prefetch" link as I think this an implementation detail which is not required inside a starter / example.