[DEV-2561] Upgrade to Next.js 15 react 18 #1673
Conversation
- Upgrade Next.js from 14.2.30 to 15.1.6 - Update eslint-config-next to match Next.js version - Migrate all page components to use async params pattern required by Next.js 15 - Create ClientDynamicComponents wrapper for SSR-disabled components - Replace ssr: false usage in Server Components with client components - Update revalidate configuration to use numeric values instead of constants - Fix all page.tsx files to await params before usage - Update generateMetadata functions to handle Promise<Params> All builds now pass successfully with the new Next.js 15 architecture.
tommaso1
requested review from
a team,
MarcoPonchia and
marcobottaro
as code owners
🦋 Changeset detectedLatest commit: 8bec0d2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
apps/nextjs-website/package.json
Outdated
| "next": "^15.1.6", | ||
| "next-intl": "^2.20.2", | ||
| "qs": "^6.11.2", | ||
| "react": "^18.3.1", |
There was a problem hiding this comment.
Is there a reason why you are not upgrading to react 19? Could this next 15 upgrade be compatible with Stoplight Elements?
| }; | ||
| // TODO: remove when release notes metadata will be managed in strapi | ||
| export const revalidate = REVALIDATE_LONG_INTERVAL; | ||
| export const revalidate = 3600; // 1 hour |
There was a problem hiding this comment.
Why are you removing this const?
apps/nextjs-website/next.config.js
Outdated
| if (isServer) { | ||
| config.externals.push({ | ||
| '@aws-sdk/client-dynamodb': 'commonjs @aws-sdk/client-dynamodb', | ||
| '@aws-sdk/credential-providers': 'commonjs @aws-sdk/credential-providers', | ||
| }); | ||
| } |
There was a problem hiding this comment.
Why are you pushing these libraries conditionally?
* update cognito custom message funtion * + changeset
…1667) * script to update dynamodb item with expiresAt attribute * update script and readmefile * + requirements.txt file
* fix gemini models * fix missed var region in new module onenext + changeset * remplaced location with region as per requirement inside the module. * nope: location is still required
* removed action ListBucket in cloudront identity * + mchangeset * fix typo in changeset
Co-authored-by: marcobottaro <[email protected]>
Branch is not up to date with base branch@tommaso1 it seems this Pull Request is not updated with base branch. |
|
This PR exceeds the recommended size of 800 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
marcobottaro
changed the title
Jira Pull Request LinkThis Pull Request refers to the following Jira issue DEV-2561 |
|
This pull request is stale because it has been open for 14 days with no activity. If the pull request is still valid, please update it within 21 days to keep it open or merge it, otherwise it will be closed automatically. |
4 participants
List of Changes
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: