feat: add support for next.js v15 #894
Conversation
🦋 Changeset detectedLatest commit: 958983e The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 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 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for @10up/wp-nextjs-appThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! One Page Changed SizeThe following page changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
📦 Next.js Bundle Analysis for @10up/headstartwpThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
125.99 KB (🟡 +2.03 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Ten Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (145 KB) |
|---|---|---|---|
/ |
9.64 KB |
135.63 KB | 93.54% (🟢 -0.08%) |
/404 |
412 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/500 |
417 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/[...path] |
6.58 KB |
132.58 KB | 91.43% (🟢 -0.04%) |
/_error |
190 B |
126.18 KB | 87.02% (🟡 +0.01%) |
/author/[...path] |
5.93 KB |
131.92 KB | 90.98% (🟢 -0.05%) |
/blog/[[...path]] |
10.07 KB |
136.07 KB | 93.84% (🟢 -0.08%) |
/category/[...path] |
5.7 KB |
131.7 KB | 90.82% (🟢 -0.04%) |
/search/[[...path]] |
3.72 KB |
129.72 KB | 89.46% (🟢 -0.04%) |
/tag/[...path] |
5.69 KB |
131.69 KB | 90.82% (🟢 -0.05%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
📦 Next.js Bundle Analysis for @10up/wp-nextjs-appThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! One Page Changed SizeThe following page changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
📦 Next.js Bundle Analysis for @10up/headstartwpThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
125.99 KB (🟡 +2.03 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Ten Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (145 KB) |
|---|---|---|---|
/ |
9.64 KB |
135.63 KB | 93.54% (🟢 -0.08%) |
/404 |
412 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/500 |
417 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/[...path] |
6.58 KB |
132.58 KB | 91.43% (🟢 -0.04%) |
/_error |
190 B |
126.18 KB | 87.02% (🟡 +0.01%) |
/author/[...path] |
5.93 KB |
131.92 KB | 90.98% (🟢 -0.05%) |
/blog/[[...path]] |
10.07 KB |
136.07 KB | 93.84% (🟢 -0.08%) |
/category/[...path] |
5.7 KB |
131.7 KB | 90.82% (🟢 -0.04%) |
/search/[[...path]] |
3.72 KB |
129.72 KB | 89.46% (🟢 -0.04%) |
/tag/[...path] |
5.69 KB |
131.69 KB | 90.82% (🟢 -0.05%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
📦 Next.js Bundle Analysis for @10up/wp-nextjs-appThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! One Page Changed SizeThe following page changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
📦 Next.js Bundle Analysis for @10up/headstartwpThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
125.99 KB (🟡 +2.03 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Ten Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (145 KB) |
|---|---|---|---|
/ |
9.64 KB |
135.63 KB | 93.54% (🟢 -0.08%) |
/404 |
412 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/500 |
417 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/[...path] |
6.58 KB |
132.58 KB | 91.43% (🟢 -0.04%) |
/_error |
190 B |
126.18 KB | 87.02% (🟡 +0.01%) |
/author/[...path] |
5.93 KB |
131.92 KB | 90.98% (🟢 -0.05%) |
/blog/[[...path]] |
10.07 KB |
136.07 KB | 93.84% (🟢 -0.08%) |
/category/[...path] |
5.7 KB |
131.7 KB | 90.82% (🟢 -0.04%) |
/search/[[...path]] |
3.72 KB |
129.72 KB | 89.46% (🟢 -0.04%) |
/tag/[...path] |
5.69 KB |
131.69 KB | 90.82% (🟢 -0.05%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
| @@ -1,8 +1,8 @@ | |||
| export type HeadstartWPRoute<Params extends { [k: string]: unknown } = {}> = { | |||
| params: { path: string[]; site?: string; lang?: string }; | |||
| params: Promise<{ path: string[]; site?: string; lang?: string }>; | |||
There was a problem hiding this comment.
Do we need to account for searchParams here? And does this force users to use path instead of slug for their route segments? Can we include a generic here?
There was a problem hiding this comment.
We do have a generic already:
type RouteProps = {
params: Promise<{slug: string}>;
searchParams: Promise<{page: number}>;
}
const Single = async ({ params, searchParams }: HeadstartWPRoute<RoutePropos>) => {
const p = await params;
const s = await searchParams;
// p.slug, p.path, p.lang
// s.page
}
jacobdubail
left a comment
jacobdubail
left a comment
There was a problem hiding this comment.
I left one comment for you about route params.
📦 Next.js Bundle Analysis for @10up/wp-nextjs-appThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! One Page Changed SizeThe following page changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
📦 Next.js Bundle Analysis for @10up/headstartwpThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
125.99 KB (🟡 +2.03 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Ten Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (145 KB) |
|---|---|---|---|
/ |
9.64 KB |
135.63 KB | 93.54% (🟢 -0.08%) |
/404 |
412 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/500 |
417 B |
126.4 KB | 87.17% (🟡 +0.01%) |
/[...path] |
6.58 KB |
132.58 KB | 91.43% (🟢 -0.04%) |
/_error |
190 B |
126.18 KB | 87.02% (🟡 +0.01%) |
/author/[...path] |
5.93 KB |
131.92 KB | 90.98% (🟢 -0.05%) |
/blog/[[...path]] |
10.07 KB |
136.07 KB | 93.84% (🟢 -0.08%) |
/category/[...path] |
5.7 KB |
131.7 KB | 90.82% (🟢 -0.04%) |
/search/[[...path]] |
3.72 KB |
129.72 KB | 89.46% (🟢 -0.04%) |
/tag/[...path] |
5.69 KB |
131.69 KB | 90.82% (🟢 -0.05%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
2 participants
Description of the Change
This PR adds supports for Next.js 15. Note that this is sort of a breaking change, however since we never release 1.5.0 stable we don't need a major here.
This is only a breaking change for those using the
nextnpm dist tag.How to test the Change
Checklist: