Closed renovate[bot] closed 1 year ago
vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| kami | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 19, 2023 10:39pm |
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
189.47 KB (🟡 +769 B) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
49.44 KB |
238.91 KB | 68.26% (+/- <0.01%) |
/[page] |
47.95 KB |
237.42 KB | 67.83% (+/- <0.01%) |
/_error |
737 B |
190.19 KB | 54.34% (+/- <0.01%) |
/categories/[slug] |
6.53 KB |
196 KB | 56.00% (🟡 +0.01%) |
/favorite/bangumi |
7.96 KB |
197.43 KB | 56.41% (+/- <0.01%) |
/favorite/music |
5.38 KB |
194.85 KB | 55.67% (+/- <0.01%) |
/friends |
50.69 KB |
240.16 KB | 68.62% (🟢 -0.01%) |
/login |
5.29 KB |
194.76 KB | 55.65% (+/- <0.01%) |
/notes |
354 B |
189.82 KB | 54.23% (+/- <0.01%) |
/notes/[id] |
70.51 KB |
259.98 KB | 74.28% (🟡 +0.01%) |
/notes/topics |
4.51 KB |
193.98 KB | 55.42% (🟡 +0.01%) |
/notes/topics/[topicSlug] |
14.13 KB |
203.6 KB | 58.17% (🟡 +0.01%) |
/posts |
26.02 KB |
215.49 KB | 61.57% (🟡 +0.01%) |
/posts/[category]/[slug] |
72.18 KB |
261.65 KB | 74.76% (+/- <0.01%) |
/preview |
49.33 KB |
238.8 KB | 68.23% (🟢 -0.01%) |
/projects |
16.36 KB |
205.83 KB | 58.81% (🟡 +0.01%) |
/projects/[id] |
44.71 KB |
234.18 KB | 66.91% (🟢 -0.01%) |
/recently |
96.78 KB |
286.25 KB | 81.79% (🟢 -0.01%) |
/says |
16.82 KB |
206.29 KB | 58.94% (+/- <0.01%) |
/timeline |
16.99 KB |
206.46 KB | 58.99% (+/- <0.01%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.12 KB (🟡 +1.92 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.04 KB |
234.16 KB | 66.90% (🟡 +0.07%) |
/[page] |
18.24 KB |
216.36 KB | 61.82% (🟡 +0.06%) |
/_error |
736 B |
198.84 KB | 56.81% (+/- <0.01%) |
/categories/[slug] |
6.24 KB |
204.36 KB | 58.39% (🟡 +0.06%) |
/favorite/music |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/friends |
18.44 KB |
216.56 KB | 61.88% (🟢 -0.02%) |
/login |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/notes/[id] |
40.1 KB |
238.22 KB | 68.06% (🟡 +0.05%) |
/notes/topics |
5.06 KB |
203.18 KB | 58.05% (🟡 +0.07%) |
/notes/topics/[topicSlug] |
7.43 KB |
205.55 KB | 58.73% (🟡 +0.06%) |
/posts |
23.72 KB |
221.84 KB | 63.38% (🟡 +0.07%) |
/posts/[category]/[slug] |
40.79 KB |
238.91 KB | 68.26% (🟡 +0.06%) |
/preview |
20.42 KB |
218.55 KB | 62.44% (🟢 -0.01%) |
/projects |
3.76 KB |
201.88 KB | 57.68% (🟡 +0.07%) |
/projects/[id] |
14.55 KB |
212.67 KB | 60.76% (🟢 -0.01%) |
/recently |
63.27 KB |
261.39 KB | 74.68% (🟡 +0.06%) |
/says |
10.47 KB |
208.59 KB | 59.60% (+/- <0.01%) |
/timeline |
15.79 KB |
213.91 KB | 61.12% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.12 KB (🟡 +1.92 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.04 KB |
234.16 KB | 66.90% (🟡 +0.07%) |
/[page] |
18.24 KB |
216.36 KB | 61.82% (🟡 +0.05%) |
/_error |
736 B |
198.84 KB | 56.81% (+/- <0.01%) |
/categories/[slug] |
6.24 KB |
204.35 KB | 58.39% (🟡 +0.06%) |
/favorite/music |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/friends |
18.44 KB |
216.56 KB | 61.87% (🟢 -0.01%) |
/login |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/notes/[id] |
40.1 KB |
238.22 KB | 68.06% (🟡 +0.05%) |
/notes/topics |
5.06 KB |
203.17 KB | 58.05% (🟡 +0.06%) |
/notes/topics/[topicSlug] |
7.43 KB |
205.55 KB | 58.73% (🟡 +0.06%) |
/posts |
23.72 KB |
221.83 KB | 63.38% (🟡 +0.07%) |
/posts/[category]/[slug] |
40.79 KB |
238.91 KB | 68.26% (🟡 +0.05%) |
/preview |
20.42 KB |
218.54 KB | 62.44% (🟢 -0.01%) |
/projects |
3.76 KB |
201.88 KB | 57.68% (🟡 +0.06%) |
/projects/[id] |
14.55 KB |
212.67 KB | 60.76% (🟢 -0.01%) |
/recently |
63.26 KB |
261.38 KB | 74.68% (🟡 +0.05%) |
/says |
10.47 KB |
208.59 KB | 59.60% (+/- <0.01%) |
/timeline |
15.79 KB |
213.91 KB | 61.12% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.12 KB (🟡 +1.92 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.04 KB |
234.16 KB | 66.90% (🟡 +0.07%) |
/[page] |
18.24 KB |
216.36 KB | 61.82% (🟡 +0.05%) |
/_error |
736 B |
198.84 KB | 56.81% (+/- <0.01%) |
/categories/[slug] |
6.24 KB |
204.35 KB | 58.39% (🟡 +0.06%) |
/favorite/music |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/friends |
18.44 KB |
216.56 KB | 61.87% (🟢 -0.01%) |
/login |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/notes/[id] |
40.1 KB |
238.22 KB | 68.06% (🟡 +0.05%) |
/notes/topics |
5.06 KB |
203.17 KB | 58.05% (🟡 +0.06%) |
/notes/topics/[topicSlug] |
7.43 KB |
205.55 KB | 58.73% (🟡 +0.06%) |
/posts |
23.72 KB |
221.83 KB | 63.38% (🟡 +0.07%) |
/posts/[category]/[slug] |
40.79 KB |
238.91 KB | 68.26% (🟡 +0.05%) |
/preview |
20.42 KB |
218.54 KB | 62.44% (🟢 -0.01%) |
/projects |
3.76 KB |
201.88 KB | 57.68% (🟡 +0.06%) |
/projects/[id] |
14.55 KB |
212.67 KB | 60.76% (🟢 -0.01%) |
/recently |
63.26 KB |
261.38 KB | 74.68% (🟡 +0.05%) |
/says |
10.47 KB |
208.59 KB | 59.60% (+/- <0.01%) |
/timeline |
15.79 KB |
213.91 KB | 61.12% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.12 KB (🟡 +1.91 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.05 KB |
234.17 KB | 66.90% (🟡 +0.07%) |
/[page] |
18.22 KB |
216.34 KB | 61.81% (🟡 +0.05%) |
/categories/[slug] |
6.23 KB |
204.35 KB | 58.39% (🟡 +0.06%) |
/favorite/bangumi |
1.25 KB |
199.37 KB | 56.96% (+/- <0.01%) |
/friends |
18.44 KB |
216.55 KB | 61.87% (🟢 -0.01%) |
/login |
4.21 KB |
202.33 KB | 57.81% (+/- <0.01%) |
/notes |
353 B |
198.46 KB | 56.70% (+/- <0.01%) |
/notes/[id] |
40.09 KB |
238.21 KB | 68.06% (🟡 +0.05%) |
/notes/topics |
5.06 KB |
203.17 KB | 58.05% (🟡 +0.06%) |
/notes/topics/[topicSlug] |
7.42 KB |
205.54 KB | 58.73% (🟡 +0.06%) |
/posts |
23.71 KB |
221.83 KB | 63.38% (🟡 +0.07%) |
/posts/[category]/[slug] |
40.79 KB |
238.91 KB | 68.26% (🟡 +0.06%) |
/preview |
20.42 KB |
218.54 KB | 62.44% (+/- <0.01%) |
/projects |
3.75 KB |
201.87 KB | 57.68% (🟡 +0.06%) |
/projects/[id] |
14.53 KB |
212.65 KB | 60.76% (🟢 -0.01%) |
/recently |
63.24 KB |
261.36 KB | 74.67% (🟡 +0.05%) |
/says |
10.46 KB |
208.58 KB | 59.59% (+/- <0.01%) |
/timeline |
15.79 KB |
213.91 KB | 61.12% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.32 KB (🟡 +1.9 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.11 KB |
234.44 KB | 66.98% (🟡 +0.07%) |
/[page] |
18.22 KB |
216.55 KB | 61.87% (🟡 +0.05%) |
/categories/[slug] |
6.23 KB |
204.56 KB | 58.44% (🟡 +0.07%) |
/favorite/bangumi |
1.25 KB |
199.58 KB | 57.02% (+/- <0.01%) |
/friends |
18.48 KB |
216.8 KB | 61.94% (+/- <0.01%) |
/login |
4.21 KB |
202.53 KB | 57.87% (+/- <0.01%) |
/notes |
353 B |
198.67 KB | 56.76% (+/- <0.01%) |
/notes/[id] |
40.09 KB |
238.42 KB | 68.12% (🟡 +0.05%) |
/notes/topics |
5.06 KB |
203.38 KB | 58.11% (🟡 +0.06%) |
/notes/topics/[topicSlug] |
7.42 KB |
205.75 KB | 58.79% (🟡 +0.06%) |
/posts |
23.77 KB |
222.09 KB | 63.46% (🟡 +0.06%) |
/posts/[category]/[slug] |
40.8 KB |
239.12 KB | 68.32% (🟡 +0.06%) |
/preview |
20.42 KB |
218.75 KB | 62.50% (+/- <0.01%) |
/projects |
3.75 KB |
202.08 KB | 57.74% (🟡 +0.06%) |
/projects/[id] |
14.53 KB |
212.86 KB | 60.82% (🟢 -0.01%) |
/recently |
63.3 KB |
261.63 KB | 74.75% (🟡 +0.05%) |
/says |
10.46 KB |
208.79 KB | 59.65% (+/- <0.01%) |
/timeline |
15.79 KB |
214.12 KB | 61.18% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.32 KB (🟡 +1.89 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.11 KB |
234.44 KB | 66.98% (🟡 +0.07%) |
/[page] |
18.22 KB |
216.55 KB | 61.87% (🟡 +0.05%) |
/categories/[slug] |
6.23 KB |
204.56 KB | 58.44% (🟡 +0.07%) |
/favorite/bangumi |
1.25 KB |
199.58 KB | 57.02% (+/- <0.01%) |
/friends |
18.48 KB |
216.8 KB | 61.94% (+/- <0.01%) |
/login |
4.21 KB |
202.53 KB | 57.87% (+/- <0.01%) |
/notes |
353 B |
198.67 KB | 56.76% (+/- <0.01%) |
/notes/[id] |
39.18 KB |
237.5 KB | 67.86% (🟡 +0.05%) |
/notes/topics |
5.06 KB |
203.38 KB | 58.11% (🟡 +0.06%) |
/notes/topics/[topicSlug] |
7.42 KB |
205.75 KB | 58.79% (🟡 +0.06%) |
/posts |
23.77 KB |
222.09 KB | 63.46% (🟡 +0.06%) |
/posts/[category]/[slug] |
39.91 KB |
238.23 KB | 68.07% (🟡 +0.05%) |
/preview |
20.42 KB |
218.75 KB | 62.50% (+/- <0.01%) |
/projects |
3.75 KB |
202.08 KB | 57.74% (🟡 +0.06%) |
/projects/[id] |
14.54 KB |
212.86 KB | 60.82% (🟢 -0.01%) |
/recently |
63.31 KB |
261.63 KB | 74.75% (🟡 +0.05%) |
/says |
10.46 KB |
208.79 KB | 59.65% (+/- <0.01%) |
/timeline |
15.79 KB |
214.12 KB | 61.18% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.35 KB (🟡 +1.91 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.1 KB |
234.45 KB | 66.99% (🟡 +0.06%) |
/[page] |
18.24 KB |
216.59 KB | 61.88% (🟡 +0.06%) |
/_error |
741 B |
199.07 KB | 56.88% (+/- <0.01%) |
/categories/[slug] |
6.24 KB |
204.58 KB | 58.45% (🟡 +0.07%) |
/favorite/music |
4.21 KB |
202.56 KB | 57.87% (+/- <0.01%) |
/friends |
18.49 KB |
216.83 KB | 61.95% (+/- <0.01%) |
/login |
4.21 KB |
202.55 KB | 57.87% (+/- <0.01%) |
/notes/[id] |
39.2 KB |
237.55 KB | 67.87% (🟡 +0.06%) |
/notes/topics |
5.05 KB |
203.4 KB | 58.11% (🟡 +0.07%) |
/notes/topics/[topicSlug] |
7.43 KB |
205.78 KB | 58.79% (🟡 +0.07%) |
/posts |
23.77 KB |
222.12 KB | 63.46% (🟡 +0.07%) |
/posts/[category]/[slug] |
39.91 KB |
238.26 KB | 68.07% (🟡 +0.06%) |
/preview |
20.44 KB |
218.78 KB | 62.51% (+/- <0.01%) |
/projects |
3.75 KB |
202.1 KB | 57.74% (🟡 +0.06%) |
/projects/[id] |
14.56 KB |
212.91 KB | 60.83% (+/- <0.01%) |
/recently |
63.33 KB |
261.67 KB | 74.76% (🟡 +0.06%) |
/says |
10.47 KB |
208.81 KB | 59.66% (+/- <0.01%) |
/timeline |
15.79 KB |
214.13 KB | 61.18% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
198.35 KB (🟡 +1.91 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
36.1 KB |
234.45 KB | 66.99% (🟡 +0.06%) |
/[page] |
18.24 KB |
216.59 KB | 61.88% (🟡 +0.06%) |
/_error |
741 B |
199.07 KB | 56.88% (+/- <0.01%) |
/categories/[slug] |
6.24 KB |
204.58 KB | 58.45% (🟡 +0.07%) |
/favorite/music |
4.21 KB |
202.56 KB | 57.87% (+/- <0.01%) |
/friends |
18.49 KB |
216.83 KB | 61.95% (+/- <0.01%) |
/login |
4.21 KB |
202.55 KB | 57.87% (+/- <0.01%) |
/notes/[id] |
39.2 KB |
237.55 KB | 67.87% (🟡 +0.06%) |
/notes/topics |
5.05 KB |
203.4 KB | 58.11% (🟡 +0.07%) |
/notes/topics/[topicSlug] |
7.43 KB |
205.78 KB | 58.79% (🟡 +0.07%) |
/posts |
23.77 KB |
222.12 KB | 63.46% (🟡 +0.07%) |
/posts/[category]/[slug] |
39.91 KB |
238.26 KB | 68.07% (🟡 +0.06%) |
/preview |
20.44 KB |
218.78 KB | 62.51% (+/- <0.01%) |
/projects |
3.75 KB |
202.1 KB | 57.74% (🟡 +0.06%) |
/projects/[id] |
14.56 KB |
212.91 KB | 60.83% (+/- <0.01%) |
/recently |
63.33 KB |
261.67 KB | 74.76% (🟡 +0.06%) |
/says |
10.47 KB |
208.81 KB | 59.66% (+/- <0.01%) |
/timeline |
15.79 KB |
214.13 KB | 61.18% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
190.96 KB (🟡 +1.92 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
49.24 KB |
240.2 KB | 68.63% (🟡 +0.06%) |
/[page] |
49.82 KB |
240.78 KB | 68.79% (🟡 +0.06%) |
/_error |
738 B |
191.68 KB | 54.77% (+/- <0.01%) |
/categories/[slug] |
6.53 KB |
197.49 KB | 56.43% (🟡 +0.06%) |
/favorite/bangumi |
7.96 KB |
198.92 KB | 56.83% (🟡 +0.01%) |
/favorite/music |
5.37 KB |
196.33 KB | 56.10% (🟢 -0.01%) |
/friends |
52.55 KB |
243.52 KB | 69.58% (🟢 -0.01%) |
/login |
5.29 KB |
196.25 KB | 56.07% (+/- <0.01%) |
/notes/[id] |
71.76 KB |
262.72 KB | 75.06% (🟡 +0.05%) |
/notes/topics |
4.51 KB |
195.47 KB | 55.85% (🟡 +0.06%) |
/notes/topics/[topicSlug] |
14.13 KB |
205.09 KB | 58.60% (🟡 +0.06%) |
/posts |
25.67 KB |
216.64 KB | 61.90% (🟡 +0.06%) |
/posts/[category]/[slug] |
73.79 KB |
264.75 KB | 75.64% (🟡 +0.05%) |
/preview |
50.64 KB |
241.61 KB | 69.03% (🟢 -0.01%) |
/projects |
16.35 KB |
207.31 KB | 59.23% (🟡 +0.06%) |
/projects/[id] |
46.57 KB |
237.53 KB | 67.87% (🟢 -0.01%) |
/recently |
98.25 KB |
289.22 KB | 82.63% (🟡 +0.06%) |
/says |
16.82 KB |
207.78 KB | 59.37% (+/- <0.01%) |
/timeline |
17.01 KB |
207.97 KB | 59.42% (🟡 +0.06%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
190.97 KB (🟡 +2.8 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
49.24 KB |
240.21 KB | 68.63% (+/- <0.01%) |
/[page] |
49.82 KB |
240.79 KB | 68.80% (+/- <0.01%) |
/_error |
738 B |
191.69 KB | 54.77% (+/- <0.01%) |
/categories/[slug] |
6.53 KB |
197.5 KB | 56.43% (+/- <0.01%) |
/favorite/bangumi |
7.96 KB |
198.92 KB | 56.84% (+/- <0.01%) |
/favorite/music |
5.37 KB |
196.34 KB | 56.10% (+/- <0.01%) |
/friends |
52.55 KB |
243.52 KB | 69.58% (+/- <0.01%) |
/login |
5.29 KB |
196.26 KB | 56.07% (+/- <0.01%) |
/notes |
354 B |
191.31 KB | 54.66% (+/- <0.01%) |
/notes/[id] |
71.76 KB |
262.73 KB | 75.07% (+/- <0.01%) |
/notes/topics |
4.51 KB |
195.48 KB | 55.85% (+/- <0.01%) |
/notes/topics/[topicSlug] |
14.13 KB |
205.1 KB | 58.60% (+/- <0.01%) |
/posts |
25.67 KB |
216.64 KB | 61.90% (+/- <0.01%) |
/posts/[category]/[slug] |
73.79 KB |
264.75 KB | 75.64% (🟡 +0.01%) |
/preview |
50.64 KB |
241.61 KB | 69.03% (+/- <0.01%) |
/projects |
16.35 KB |
207.31 KB | 59.23% (+/- <0.01%) |
/projects/[id] |
46.57 KB |
237.54 KB | 67.87% (🟢 -0.01%) |
/recently |
98.26 KB |
289.22 KB | 82.64% (🟢 -0.01%) |
/says |
16.82 KB |
207.78 KB | 59.37% (+/- <0.01%) |
/timeline |
17.01 KB |
207.98 KB | 59.42% (🟡 +0.01%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
190.73 KB (🟡 +2.8 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
49.25 KB |
239.98 KB | 68.56% (🟡 +0.01%) |
/_error |
738 B |
191.45 KB | 54.70% (+/- <0.01%) |
/categories/[slug] |
6.53 KB |
197.26 KB | 56.36% (🟡 +0.01%) |
/favorite/bangumi |
7.96 KB |
198.69 KB | 56.77% (+/- <0.01%) |
/favorite/music |
5.37 KB |
196.1 KB | 56.03% (+/- <0.01%) |
/friends |
50.73 KB |
241.46 KB | 68.99% (+/- <0.01%) |
/login |
5.29 KB |
196.02 KB | 56.01% (+/- <0.01%) |
/notes |
354 B |
191.08 KB | 54.59% (+/- <0.01%) |
/notes/[id] |
69.94 KB |
260.67 KB | 74.48% (+/- <0.01%) |
/notes/topics |
4.51 KB |
195.24 KB | 55.78% (🟡 +0.01%) |
/notes/topics/[topicSlug] |
14.13 KB |
204.86 KB | 58.53% (🟡 +0.01%) |
/posts |
25.68 KB |
216.41 KB | 61.83% (🟡 +0.01%) |
/posts/[category]/[slug] |
71.95 KB |
262.68 KB | 75.05% (+/- <0.01%) |
/preview |
48.81 KB |
239.54 KB | 68.44% (+/- <0.01%) |
/projects |
16.35 KB |
207.08 KB | 59.16% (🟡 +0.01%) |
/projects/[id] |
44.74 KB |
235.47 KB | 67.28% (🟢 -0.01%) |
/recently |
96.43 KB |
287.16 KB | 82.05% (🟢 -0.01%) |
/says |
16.82 KB |
207.55 KB | 59.30% (+/- <0.01%) |
/timeline |
17.01 KB |
207.74 KB | 59.35% (🟡 +0.01%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
190.76 KB (🟡 +2.8 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
49.25 KB |
240 KB | 68.57% (+/- <0.01%) |
/_error |
738 B |
191.48 KB | 54.71% (+/- <0.01%) |
/categories/[slug] |
6.53 KB |
197.29 KB | 56.37% (+/- <0.01%) |
/favorite/bangumi |
7.96 KB |
198.71 KB | 56.78% (+/- <0.01%) |
/favorite/music |
5.37 KB |
196.13 KB | 56.04% (+/- <0.01%) |
/friends |
50.73 KB |
241.49 KB | 69.00% (🟢 -0.01%) |
/login |
5.29 KB |
196.05 KB | 56.01% (+/- <0.01%) |
/notes |
354 B |
191.1 KB | 54.60% (+/- <0.01%) |
/notes/[id] |
69.94 KB |
260.7 KB | 74.48% (+/- <0.01%) |
/notes/topics |
4.51 KB |
195.27 KB | 55.79% (+/- <0.01%) |
/notes/topics/[topicSlug] |
14.13 KB |
204.89 KB | 58.54% (🟡 +0.01%) |
/posts |
25.68 KB |
216.44 KB | 61.84% (+/- <0.01%) |
/posts/[category]/[slug] |
71.95 KB |
262.71 KB | 75.06% (+/- <0.01%) |
/preview |
48.81 KB |
239.57 KB | 68.45% (🟢 -0.01%) |
/projects |
16.35 KB |
207.11 KB | 59.17% (🟡 +0.01%) |
/projects/[id] |
44.74 KB |
235.5 KB | 67.28% (+/- <0.01%) |
/recently |
96.43 KB |
287.19 KB | 82.05% (+/- <0.01%) |
/says |
16.82 KB |
207.58 KB | 59.31% (+/- <0.01%) |
/timeline |
17.01 KB |
207.77 KB | 59.36% (🟡 +0.01%) |
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.
github-actions[bot]
commented
1 year ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
190.8 KB (🟡 +2.81 KB) |
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!
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
49.24 KB |
240.05 KB | 68.59% (+/- <0.01%) |
/[page] |
47.98 KB |
238.79 KB | 68.23% (+/- <0.01%) |
/_error |
738 B |
191.53 KB | 54.72% (+/- <0.01%) |
/categories/[slug] |
6.53 KB |
197.33 KB | 56.38% (🟡 +0.01%) |
/favorite/bangumi |
7.96 KB |
198.76 KB | 56.79% (+/- <0.01%) |
/favorite/music |
5.37 KB |
196.18 KB | 56.05% (+/- <0.01%) |
/friends |
50.72 KB |
241.53 KB | 69.01% (+/- <0.01%) |
/login |
5.29 KB |
196.1 KB | 56.03% (+/- <0.01%) |
/notes |
354 B |
191.15 KB | 54.61% (+/- <0.01%) |
/notes/[id] |
69.94 KB |
260.74 KB | 74.50% (+/- <0.01%) |
/notes/topics |
4.51 KB |
195.31 KB | 55.80% (🟡 +0.01%) |
/notes/topics/[topicSlug] |
14.13 KB |
204.94 KB | 58.55% (🟡 +0.01%) |
/posts |
25.68 KB |
216.48 KB | 61.85% (🟡 +0.01%) |
/posts/[category]/[slug] |
71.95 KB |
262.75 KB | 75.07% (+/- <0.01%) |
/preview |
48.81 KB |
239.61 KB | 68.46% (🟢 -0.01%) |
/projects |
16.35 KB |
207.15 KB | 59.19% (+/- <0.01%) |
/projects/[id] |
44.74 KB |
235.54 KB | 67.30% (🟢 -0.01%) |
/recently |
96.43 KB |
287.23 KB | 82.07% (🟢 -0.01%) |
/says |
16.82 KB |
207.62 KB | 59.32% (+/- <0.01%) |
/timeline |
17.01 KB |
207.81 KB | 59.38% (+/- <0.01%) |
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.
This PR contains the following updates:
0.9.10->0.10.00.9.11->0.10.08.40.0->8.41.013.3.4->13.4.38.3.2->8.4.1Release Notes
eslint/eslint
### [`v8.41.0`](https://togithub.com/eslint/eslint/releases/tag/v8.41.0) [Compare Source](https://togithub.com/eslint/eslint/compare/v8.40.0...v8.41.0) #### Features - [`880a431`](https://togithub.com/eslint/eslint/commit/880a4317b949e575a4a6c5e8baaba1eea7674cc6) feat: change default ignore pattern to `**/node_modules/` in flat config ([#17184](https://togithub.com/eslint/eslint/issues/17184)) (Milos Djermanovic) - [`8bf5505`](https://togithub.com/eslint/eslint/commit/8bf550594fca6d29fab1a3453e701c1a457767e1) feat: expose `shouldUseFlatConfig` ([#17169](https://togithub.com/eslint/eslint/issues/17169)) (Connor Prussin) #### Bug Fixes - [`4f5440d`](https://togithub.com/eslint/eslint/commit/4f5440db631707b17140c4e5cc7beb223afbd2b9) fix: incorrect warning message for ignored dotfiles ([#17196](https://togithub.com/eslint/eslint/issues/17196)) (Milos Djermanovic) - [`94da96c`](https://togithub.com/eslint/eslint/commit/94da96cbf0fb2bb6694fa2e757eb1b3e74c40db7) fix: unify `LintMessage` type ([#17076](https://togithub.com/eslint/eslint/issues/17076)) (Brandon Mills) - [`0c415cd`](https://togithub.com/eslint/eslint/commit/0c415cda5d76dbe5120ab9f3c4c81320538e35f0) fix: validate `ignorePatterns` constructor option in `FlatESLint` class ([#17139](https://togithub.com/eslint/eslint/issues/17139)) (Milos Djermanovic) - [`9682d66`](https://togithub.com/eslint/eslint/commit/9682d669e4ee8641293914e21679f40fee8bc354) fix: switch `grapheme-splitter` to `graphemer` ([#17160](https://togithub.com/eslint/eslint/issues/17160)) (fisker Cheung) #### Documentation - [`7709b14`](https://togithub.com/eslint/eslint/commit/7709b14e18ad4e11c1119ed6575454243b8e7084) docs: Update README (GitHub Actions Bot) - [`7f183e0`](https://togithub.com/eslint/eslint/commit/7f183e020579380fa57473caaf9ed154470c25b3) docs: Update triage process description ([#17157](https://togithub.com/eslint/eslint/issues/17157)) (Nicholas C. Zakas) - [`b68346b`](https://togithub.com/eslint/eslint/commit/b68346b290d55324e73868ca42b3854157b27375) docs: fix license to reflect relicensing of jshint ([#17165](https://togithub.com/eslint/eslint/issues/17165)) (Stefan Bischof) #### Chores - [`f43216a`](https://togithub.com/eslint/eslint/commit/f43216a8c77ab6cf1d0823978e8c728786b4cba7) chore: upgrade [@eslint/js](https://togithub.com/eslint/js)[@8](https://togithub.com/8).41.0 ([#17200](https://togithub.com/eslint/eslint/issues/17200)) (Milos Djermanovic) - [`95c3007`](https://togithub.com/eslint/eslint/commit/95c300780a1cfd9ad680bc78850542eb55d7fbf4) chore: package.json update for [@eslint/js](https://togithub.com/eslint/js) release (ESLint Jenkins) - [`ddc5291`](https://togithub.com/eslint/eslint/commit/ddc5291debd90ff476e17c532af7577e26720b91) chore: don't use deprecated `context` methods in `ast-utils` tests ([#17194](https://togithub.com/eslint/eslint/issues/17194)) (Milos Djermanovic) - [`b1516db`](https://togithub.com/eslint/eslint/commit/b1516db51514032ed06e1425c4b1f955238dc682) chore: Fix return type of `findFlatConfigFile` ([#17161](https://togithub.com/eslint/eslint/issues/17161)) (Milos Djermanovic) - [`918b0fd`](https://togithub.com/eslint/eslint/commit/918b0fd21723e84bd7acb17942a36606f1d8360a) perf: Store indent descriptors in a plain array ([#17148](https://togithub.com/eslint/eslint/issues/17148)) (Francesco Trotta) - [`4caa344`](https://togithub.com/eslint/eslint/commit/4caa34449555d8a680222ec2049d97c59476c11e) refactor: locateConfigFileToUse returns an Error object ([#17159](https://togithub.com/eslint/eslint/issues/17159)) (唯然)vercel/next.js
### [`v13.4.3`](https://togithub.com/vercel/next.js/releases/tag/v13.4.3) [Compare Source](https://togithub.com/vercel/next.js/compare/v13.4.2...v13.4.3) ##### Core Changes - Optimize trace span relationships: [#49697](https://togithub.com/vercel/next.js/issues/49697) - refactor(next-core): deprecate custom_ecmascript_transforms: [#49629](https://togithub.com/vercel/next.js/issues/49629) - Remove old-space-size filtering from dev server: [#49727](https://togithub.com/vercel/next.js/issues/49727) - Rework client router filter handling: [#49741](https://togithub.com/vercel/next.js/issues/49741) - fix(image): preload should respect referrerPolicy: [#49584](https://togithub.com/vercel/next.js/issues/49584) - Fix cookies().set missing in types: [#49806](https://togithub.com/vercel/next.js/issues/49806) - fix: Disable `tracing/release_max_level_off` for wasm, too: [#49639](https://togithub.com/vercel/next.js/issues/49639) - Apply user-defined PostCSS transforms to foreign code: [#49463](https://togithub.com/vercel/next.js/issues/49463) - add [@swc/core](https://togithub.com/swc/core) to server external packages: [#49721](https://togithub.com/vercel/next.js/issues/49721) - `turbo-binding` -> `turbopack-binding`: [#49816](https://togithub.com/vercel/next.js/issues/49816) - refactor(next-core): consolidate react_refresh options: [#49822](https://togithub.com/vercel/next.js/issues/49822) - add support for globally providing mdx components to turbopack: [#49818](https://togithub.com/vercel/next.js/issues/49818) - Refactor pages structure: [#49802](https://togithub.com/vercel/next.js/issues/49802) - Fix conflict when re-exporting multiple Client References: [#49468](https://togithub.com/vercel/next.js/issues/49468) - refactor(next-core): move transforms to plugin: [#49621](https://togithub.com/vercel/next.js/issues/49621) - Fix chained `.bind` of Server Actions: [#49874](https://togithub.com/vercel/next.js/issues/49874) - Fix port value for metadataBase: [#49924](https://togithub.com/vercel/next.js/issues/49924) - Introduce NextMode: [#49852](https://togithub.com/vercel/next.js/issues/49852) - Port sorted-routes.ts to Rust: [#48334](https://togithub.com/vercel/next.js/issues/48334) - Move build workers count change behind flag: [#49937](https://togithub.com/vercel/next.js/issues/49937) - Update default for appDocumentPreloading config for minimalMode: [#49952](https://togithub.com/vercel/next.js/issues/49952) - Add [@vercel/og](https://togithub.com/vercel/og) to external server packages: [#49944](https://togithub.com/vercel/next.js/issues/49944) - Fix custom server React resolution with app dir and pages both presented: [#49805](https://togithub.com/vercel/next.js/issues/49805) - Error in `next export` when `serverActions` is enabled: [#49959](https://togithub.com/vercel/next.js/issues/49959) - Reset not-found and error boundary when navigating: [#49855](https://togithub.com/vercel/next.js/issues/49855) - Revert "Error in `next export` when `serverActions` is enabled": [#50019](https://togithub.com/vercel/next.js/issues/50019) - fix: warning fetch for `[object Request]` specified: [#50003](https://togithub.com/vercel/next.js/issues/50003) - Remove custom handling for prebundled react env: [#49954](https://togithub.com/vercel/next.js/issues/49954) - fix: set cookies followed by `redirect()`: [#49965](https://togithub.com/vercel/next.js/issues/49965) ##### Example Changes - chore: update examples to use draft mode: [#49720](https://togithub.com/vercel/next.js/issues/49720) - Add mdx page example to examples/app-dir-mdx: [#47082](https://togithub.com/vercel/next.js/issues/47082) - Update with-supertokens example: [#49804](https://togithub.com/vercel/next.js/issues/49804) - with-clerk example updated to app router: [#49717](https://togithub.com/vercel/next.js/issues/49717) - Upgrading react-ga to react-ga4: [#48932](https://togithub.com/vercel/next.js/issues/48932) - update with-turbopack example: [#49332](https://togithub.com/vercel/next.js/issues/49332) ##### Misc Changes - Add trace-to-jaeger to workspace: [#49692](https://togithub.com/vercel/next.js/issues/49692) - refactor(scripts): apply fmt: [#49716](https://togithub.com/vercel/next.js/issues/49716) - refactor(scripts): fix clippy errors: [#49719](https://togithub.com/vercel/next.js/issues/49719) - chore(turbopack): Update `swc_core` to `v0.76.6`: [#49792](https://togithub.com/vercel/next.js/issues/49792) - Fix going back to page after applying hash link: [#50006](https://togithub.com/vercel/next.js/issues/50006) - build(cargo): update turbopack: [#50013](https://togithub.com/vercel/next.js/issues/50013) - Suggest a replay in the bug issue template: [#50022](https://togithub.com/vercel/next.js/issues/50022) ##### Credits Huge thanks to [@timneutkens](https://togithub.com/timneutkens), [@kwonoj](https://togithub.com/kwonoj), [@styfle](https://togithub.com/styfle), [@ijjk](https://togithub.com/ijjk), [@alexanderbluhm](https://togithub.com/alexanderbluhm), [@Fonger](https://togithub.com/Fonger), [@shuding](https://togithub.com/shuding), [@kdy1](https://togithub.com/kdy1), [@alexkirsz](https://togithub.com/alexkirsz), [@souporserious](https://togithub.com/souporserious), [@ForsakenHarmony](https://togithub.com/ForsakenHarmony), [@rishabhpoddar](https://togithub.com/rishabhpoddar), [@devagrawal09](https://togithub.com/devagrawal09), [@DevEsteves](https://togithub.com/DevEsteves), [@huozhi](https://togithub.com/huozhi), and [@padmaia](https://togithub.com/padmaia) for helping! ### [`v13.4.2`](https://togithub.com/vercel/next.js/releases/tag/v13.4.2) [Compare Source](https://togithub.com/vercel/next.js/compare/v13.4.1...v13.4.2) ##### Core Changes - make sure server component externals only apply to files resolvable by node: [#49147](https://togithub.com/vercel/next.js/issues/49147) - Fix link not being GC'd sometimes: [#49318](https://togithub.com/vercel/next.js/issues/49318) - Fix issue where nextP is not replaced in searchParams: [#49315](https://togithub.com/vercel/next.js/issues/49315) - Add typescript version to next-info: [#49346](https://togithub.com/vercel/next.js/issues/49346) - Upgrade React to 18.3.0-canary-16d053d59-20230506: [#49402](https://togithub.com/vercel/next.js/issues/49402) - Remove empty config warning: [#49435](https://togithub.com/vercel/next.js/issues/49435) - app-router: add startTransition call to revalidate dispatcher: [#49453](https://togithub.com/vercel/next.js/issues/49453) - Inline static data buffer instead of using fs read: [#49323](https://togithub.com/vercel/next.js/issues/49323) - Revert "Temporarily disable app dir export integration test": [#49311](https://togithub.com/vercel/next.js/issues/49311) - Add link to Server Actions docs.: [#49384](https://togithub.com/vercel/next.js/issues/49384) - Replace metadata clone with custom handler in dev: [#49343](https://togithub.com/vercel/next.js/issues/49343) - Add request-async-storage to the shared layer: [#49470](https://togithub.com/vercel/next.js/issues/49470) - Fix revalidate: false detection in app: [#49473](https://togithub.com/vercel/next.js/issues/49473) - Fix metadata image route encoding: [#49482](https://togithub.com/vercel/next.js/issues/49482) - Fix actions redirect handling: [#49483](https://togithub.com/vercel/next.js/issues/49483) - Restrict `useOptimistic` and `useFormStatus` APIs on the server layer: [#49331](https://togithub.com/vercel/next.js/issues/49331) - Fix external rewrite with body: [#49487](https://togithub.com/vercel/next.js/issues/49487) - fix: better error message with an invalid assetPrefix: [#49403](https://togithub.com/vercel/next.js/issues/49403) - Fix Node Crypto polyfill: [#49288](https://togithub.com/vercel/next.js/issues/49288) - Fix: Router.query contains \_next when using middleware with dynamic routes: [#48753](https://togithub.com/vercel/next.js/issues/48753) - type: update React.CSSProperties type to Record: [#49186](https://togithub.com/vercel/next.js/issues/49186) - Fix server CSS imports and HMR not working properly in specific conditions: [#49462](https://togithub.com/vercel/next.js/issues/49462) - Fix HMR support for server layer imported SASS and SCSS: [#49534](https://togithub.com/vercel/next.js/issues/49534) - Support `.bind` syntax with Action functions: [#49422](https://togithub.com/vercel/next.js/issues/49422) - ci(test): enable turbopack test: [#49466](https://togithub.com/vercel/next.js/issues/49466) - feat(next-core): relay transform plugin: [#48899](https://togithub.com/vercel/next.js/issues/48899) - Fix canonical url for dynamic routes: [#49512](https://togithub.com/vercel/next.js/issues/49512) - Add experimental compile/generate handling: [#49491](https://togithub.com/vercel/next.js/issues/49491) - chore: cross-platform `rm -rf` script: [#49529](https://togithub.com/vercel/next.js/issues/49529) - refactor(next-core): remove ast cloning in custom transform: [#49560](https://togithub.com/vercel/next.js/issues/49560) - fix: a11y issues in react-dev-overlay: [#49460](https://togithub.com/vercel/next.js/issues/49460) - Add tests for HMR: [#49206](https://togithub.com/vercel/next.js/issues/49206) - Add stub Route type for typedRoutes: [#48099](https://togithub.com/vercel/next.js/issues/48099) - Add test for appdir referenced images: [#49242](https://togithub.com/vercel/next.js/issues/49242) - feat: Allow trace-level logging for non-published release builds: [#49564](https://togithub.com/vercel/next.js/issues/49564) - Fix unexpected object mutation while resolving Open Graph: [#49514](https://togithub.com/vercel/next.js/issues/49514) - actions: forward fetch rejections to the action handler: [#49577](https://togithub.com/vercel/next.js/issues/49577) - actions: make cookies.set revalidate: [#49582](https://togithub.com/vercel/next.js/issues/49582) - interception route: fix route groups breaking the referrer computation: [#49602](https://togithub.com/vercel/next.js/issues/49602) - Allow export decl with any init value in the actions compiler: [#49600](https://togithub.com/vercel/next.js/issues/49600) - Handle unstable_cache in pages: [#49624](https://togithub.com/vercel/next.js/issues/49624) - Update cache method handling during build: [#49633](https://togithub.com/vercel/next.js/issues/49633) - Fix fetchCache and no-store handling: [#49638](https://togithub.com/vercel/next.js/issues/49638) - interception routes: fix rewrites order: [#49615](https://togithub.com/vercel/next.js/issues/49615) - Ensure initialHeaders are normalized: [#49643](https://togithub.com/vercel/next.js/issues/49643) - app-router: add support for parallel routes in useParams: [#49595](https://togithub.com/vercel/next.js/issues/49595) - Add puppeteer to external packages list: [#49597](https://togithub.com/vercel/next.js/issues/49597) - Add playwright to external package list: [#49649](https://togithub.com/vercel/next.js/issues/49649) - actions: fill prefetchCache with revalidation payload: [#49576](https://togithub.com/vercel/next.js/issues/49576) - Rename Turbopack/tasks crates to common prefixes: [#49446](https://togithub.com/vercel/next.js/issues/49446) - chore(jest): Simplify isServer expression: [#48330](https://togithub.com/vercel/next.js/issues/48330) - Add missing config vars into Webpack cache key: [#49663](https://togithub.com/vercel/next.js/issues/49663) - misc: Apply PR comments from [#49206](https://togithub.com/vercel/next.js/issues/49206): [#49647](https://togithub.com/vercel/next.js/issues/49647) - fix: Standalone node http server starts accepting requests before next handler is ready: [#49548](https://togithub.com/vercel/next.js/issues/49548) - Update links from beta to stable docs.: [#49349](https://togithub.com/vercel/next.js/issues/49349) ##### Documentation Changes - Fix error message about `preconnect` 📝: [#40360](https://togithub.com/vercel/next.js/issues/40360) - \[docs] Add iOS hydration mismatch details to error page: [#43584](https://togithub.com/vercel/next.js/issues/43584) - Add note about custom distDir to standalone build docs: [#48592](https://togithub.com/vercel/next.js/issues/48592) - Add `--use-yarn` flag to `create-next-app`: [#49407](https://togithub.com/vercel/next.js/issues/49407) ##### Misc Changes - Add test case for client sourcemaps: [#49308](https://togithub.com/vercel/next.js/issues/49308) - Update start release workflow inputs: [#49492](https://togithub.com/vercel/next.js/issues/49492) - Fix failing actions e2e deploy test: [#49497](https://togithub.com/vercel/next.js/issues/49497) - Replace var with const: [#49379](https://togithub.com/vercel/next.js/issues/49379) - test: pages react version with react hook in deployment: [#48907](https://togithub.com/vercel/next.js/issues/48907) - Add test case for [#49235](https://togithub.com/vercel/next.js/issues/49235): [#49488](https://togithub.com/vercel/next.js/issues/49488) - chore: fix flaky middleware matcher test: [#49555](https://togithub.com/vercel/next.js/issues/49555) - Avoid skipping the required Test Codemods job: [#49589](https://togithub.com/vercel/next.js/issues/49589) - Update flakey app-actions deploy tests: [#49667](https://togithub.com/vercel/next.js/issues/49667) ##### Credits Huge thanks to [@shuding](https://togithub.com/shuding), [@ijjk](https://togithub.com/ijjk), [@ForsakenHarmony](https://togithub.com/ForsakenHarmony), [@timneutkens](https://togithub.com/timneutkens), [@huozhi](https://togithub.com/huozhi), [@sanjaiyan-dev](https://togithub.com/sanjaiyan-dev), [@acdlite](https://togithub.com/acdlite), [@feedthejim](https://togithub.com/feedthejim), [@styfle](https://togithub.com/styfle), [@leerob](https://togithub.com/leerob), [@koba04](https://togithub.com/koba04), [@g12i](https://togithub.com/g12i), [@cesarkohl](https://togithub.com/cesarkohl), [@darshkpatel](https://togithub.com/darshkpatel), [@josh](https://togithub.com/josh), [@li-jia-nan](https://togithub.com/li-jia-nan), [@kwonoj](https://togithub.com/kwonoj), [@gabschne](https://togithub.com/gabschne), [@alexkirsz](https://togithub.com/alexkirsz), [@karlhorky](https://togithub.com/karlhorky), [@jridgewell](https://togithub.com/jridgewell), [@sokra](https://togithub.com/sokra), [@kdy1](https://togithub.com/kdy1), [@akd-io](https://togithub.com/akd-io), [@runjuu](https://togithub.com/runjuu), [@jocarrd](https://togithub.com/jocarrd), [@nnnnoel](https://togithub.com/nnnnoel), and [@ferdingler](https://togithub.com/ferdingler) for helping! ### [`v13.4.1`](https://togithub.com/vercel/next.js/releases/tag/v13.4.1) [Compare Source](https://togithub.com/vercel/next.js/compare/v13.4.0...v13.4.1) ##### Core Changes - actions: update location header: [#49223](https://togithub.com/vercel/next.js/issues/49223) - Fix serving images referenced from app directory: [#49236](https://togithub.com/vercel/next.js/issues/49236) - Update dev logs to include request timings: [#49191](https://togithub.com/vercel/next.js/issues/49191) - Support incrementalCacheHandlerPath for standalone output: [#48694](https://togithub.com/vercel/next.js/issues/48694) - Apply basePath for metadata image: [#49226](https://togithub.com/vercel/next.js/issues/49226) - Fix Server Actions defined in both layers in one entry: [#49248](https://togithub.com/vercel/next.js/issues/49248) - Update tags handling during server action redirect: [#49227](https://togithub.com/vercel/next.js/issues/49227) - Add experimental verboseRequestLogs flag: [#49250](https://togithub.com/vercel/next.js/issues/49250) - Fix require-hook with just pages on deploy: [#49274](https://togithub.com/vercel/next.js/issues/49274) ##### Misc Changes - Upgrade react types: [#49222](https://togithub.com/vercel/next.js/issues/49222) - Remove experimental config from create-next-app: [#49241](https://togithub.com/vercel/next.js/issues/49241) ##### Credits Huge thanks to [@feedthejim](https://togithub.com/feedthejim), [@jridgewell](https://togithub.com/jridgewell), [@ijjk](https://togithub.com/ijjk), [@ikryvorotenko](https://togithub.com/ikryvorotenko), [@huozhi](https://togithub.com/huozhi), [@shuding](https://togithub.com/shuding), and [@timneutkens](https://togithub.com/timneutkens) for helping! ### [`v13.4.0`](https://togithub.com/vercel/next.js/releases/tag/v13.4.0) [Compare Source](https://togithub.com/vercel/next.js/compare/v13.3.4...v13.4.0) ##### Core Changes - More fluent GraphTraversal API: [#49028](https://togithub.com/vercel/next.js/issues/49028) - fix GlobalError interop and add test case: [#49033](https://togithub.com/vercel/next.js/issues/49033) - Add flag to switch to the experimental channel: [#48896](https://togithub.com/vercel/next.js/issues/48896) - Fix extra block element in body: [#49034](https://togithub.com/vercel/next.js/issues/49034) - Fixed `next-types-plugin` causing Typescript errors when `"type": "module"` is set: [#49027](https://togithub.com/vercel/next.js/issues/49027) - Fixed middleware's edge-chunks not being copied in copyTracedFiles: [#48723](https://togithub.com/vercel/next.js/issues/48723) - Rename `experimentalReact`: [#49046](https://togithub.com/vercel/next.js/issues/49046) - app router: don't unmount/remount on search param changes: [#49047](https://togithub.com/vercel/next.js/issues/49047) - style: remove useless React.Fragment tag on `next/image`: [#48997](https://togithub.com/vercel/next.js/issues/48997) - feat: add draft mode to `next/headers`: [#48789](https://togithub.com/vercel/next.js/issues/48789) - Fix `next dev` failing for app when `__NEXT_DISABLE_MEMORY_WATCHER` is set: [#49056](https://togithub.com/vercel/next.js/issues/49056) - fix(next-core): interop non string record values in env: [#49057](https://togithub.com/vercel/next.js/issues/49057) - feat(next-core): support capsize for google font fallback: [#48967](https://togithub.com/vercel/next.js/issues/48967) - chore: use includes replace indexOf: [#48901](https://togithub.com/vercel/next.js/issues/48901) - feat: make `enableUndici: true` default and remove `node-fetch`: [#49061](https://togithub.com/vercel/next.js/issues/49061) - fix(next_core): do not apply user config to internal assets: [#48210](https://togithub.com/vercel/next.js/issues/48210) - update turbopack: [#49071](https://togithub.com/vercel/next.js/issues/49071) - allow to use different blur placeholder modes: [#49070](https://togithub.com/vercel/next.js/issues/49070) - Use route metadata to trace in node-file-trace: [#49080](https://togithub.com/vercel/next.js/issues/49080) - fix quoted env vars from next config: [#49090](https://togithub.com/vercel/next.js/issues/49090) - find and handle not-found page in app dir: [#49095](https://togithub.com/vercel/next.js/issues/49095) - Update revalidate handling for app: [#49062](https://togithub.com/vercel/next.js/issues/49062) - Update turbopack warning: [#49051](https://togithub.com/vercel/next.js/issues/49051) - Add validation to server methods: [#49104](https://togithub.com/vercel/next.js/issues/49104) - use ws instead of undici.WebSocket: [#49100](https://togithub.com/vercel/next.js/issues/49100) - chore: rename draft mode enabled to isEnabled: [#49096](https://togithub.com/vercel/next.js/issues/49096) - add test cases for error handling: [#49093](https://togithub.com/vercel/next.js/issues/49093) - improve test case stability: [#49036](https://togithub.com/vercel/next.js/issues/49036) - Optimize non-dynamic metadata routes to static in production build: [#49109](https://togithub.com/vercel/next.js/issues/49109) - Allow setting `runtime` in layouts in type declarations: [#49117](https://togithub.com/vercel/next.js/issues/49117) - Tweak app cache handling for paths: [#49108](https://togithub.com/vercel/next.js/issues/49108) - add test case for non-enumerable exports: [#49106](https://togithub.com/vercel/next.js/issues/49106) - Skip handler for POST requests when no action ID is found: [#49119](https://togithub.com/vercel/next.js/issues/49119) - Fix edge runtime detection from layouts: [#49126](https://togithub.com/vercel/next.js/issues/49126) - Fix cross-worker revalidate API: [#49101](https://togithub.com/vercel/next.js/issues/49101) - app router: Fix infinite redirect loop in MPA navigation: [#49058](https://togithub.com/vercel/next.js/issues/49058) - Only read digest from error instance: [#49132](https://togithub.com/vercel/next.js/issues/49132) - Static generate dynamic sitemaps: [#49114](https://togithub.com/vercel/next.js/issues/49114) - Remove writing vscode config: [#49133](https://togithub.com/vercel/next.js/issues/49133) - Revert "Fix cross-worker revalidate API": [#49138](https://togithub.com/vercel/next.js/issues/49138) - Revert "Revert "Fix cross-worker revalidate API" ([#49138](https://togithub.com/vercel/next.js/issues/49138))": [#49141](https://togithub.com/vercel/next.js/issues/49141) - fix(ts): make `ReadonlyHeaders` more compatible with `Headers`: [#49075](https://togithub.com/vercel/next.js/issues/49075) - app-router: update prefetch heuristic to traverse until until we hit a loading boundary: [#49077](https://togithub.com/vercel/next.js/issues/49077) - Forward response to edge runtime for response modification: [#49145](https://togithub.com/vercel/next.js/issues/49145) - Polyfill `Blob` for Node.js < 18: [#49156](https://togithub.com/vercel/next.js/issues/49156) - Update compilation target of [@next/react-dev-overlay](https://togithub.com/next/react-dev-overlay): [#49153](https://togithub.com/vercel/next.js/issues/49153) - Fix CSS module imports not included in root not-found file: [#49155](https://togithub.com/vercel/next.js/issues/49155) - app-router: fix stale cache handling: [#49160](https://togithub.com/vercel/next.js/issues/49160) - Add support for app global and segment 404 pages: [#49085](https://togithub.com/vercel/next.js/issues/49085) - Tests for Sass warnings: [#49151](https://togithub.com/vercel/next.js/issues/49151) - Ensure latest react-dom types for experimental release channel are used: [#49049](https://togithub.com/vercel/next.js/issues/49049) - Update cache methods for app dir: [#49165](https://togithub.com/vercel/next.js/issues/49165) - Search for lockfiles to find Turbopack root: [#49110](https://togithub.com/vercel/next.js/issues/49110) - Allow webpack config, but warn if no turbo config: [#49170](https://togithub.com/vercel/next.js/issues/49170) - Add a generic type for unstable_cache: [#49166](https://togithub.com/vercel/next.js/issues/49166) - Upgrade React to 18.3.0-canary-b7972822b-20230503: [#49158](https://togithub.com/vercel/next.js/issues/49158) - Fix server component transforms: [#49135](https://togithub.com/vercel/next.js/issues/49135) - Fix React channel env missing in custom server: [#49168](https://togithub.com/vercel/next.js/issues/49168) - app router: support side effects on server requests: [#48939](https://togithub.com/vercel/next.js/issues/48939) - Fix multipart/form-data handling in the Edge runtime: [#49177](https://togithub.com/vercel/next.js/issues/49177) - Upgrade React to 18.3.0-canary-aef7ce554-20230503: [#49181](https://togithub.com/vercel/next.js/issues/49181) - remove startup message by default: [#49157](https://togithub.com/vercel/next.js/issues/49157) - add test case for bindings in member props: [#49134](https://togithub.com/vercel/next.js/issues/49134) - Add test case for App Route cookies: [#49124](https://togithub.com/vercel/next.js/issues/49124) - Fix standalone mode with appDir running in a single process: [#49116](https://togithub.com/vercel/next.js/issues/49116) - Enable progressive enhanced form actions through decodeAction: [#49187](https://togithub.com/vercel/next.js/issues/49187) - Use special annotation for `$$bound` if no closure argument is attached: [#49188](https://togithub.com/vercel/next.js/issues/49188) - Add warning for missing metadataBase in social images: [#49180](https://togithub.com/vercel/next.js/issues/49180) - Allow override icon rel: [#49194](https://togithub.com/vercel/next.js/issues/49194) - actions: fix redirect on the edge: [#49197](https://togithub.com/vercel/next.js/issues/49197) - update turbopack: [#49196](https://togithub.com/vercel/next.js/issues/49196) - Fix incorrect React env in particular case: [#49202](https://togithub.com/vercel/next.js/issues/49202) - Add SWC test cases: [#49189](https://togithub.com/vercel/next.js/issues/49189) - action: add Readable.toWeb "polyfill" for node 16: [#49201](https://togithub.com/vercel/next.js/issues/49201) - add missing alias for next/dynamic in app dir: [#49199](https://togithub.com/vercel/next.js/issues/49199) - render app pages with original url: [#49198](https://togithub.com/vercel/next.js/issues/49198) - action: support not found: [#49209](https://togithub.com/vercel/next.js/issues/49209) - types: upgrade react/react-dom types: [#49213](https://togithub.com/vercel/next.js/issues/49213) - Fix metadata routes prerender cache for standalone mode: [#49208](https://togithub.com/vercel/next.js/issues/49208) - Turbopack alpha -> beta: [#49103](https://togithub.com/vercel/next.js/issues/49103) - Enable App Router for all applications: [#49088](https://togithub.com/vercel/next.js/issues/49088) ##### Documentation Changes - fix: wrong link in docs: [#49001](https://togithub.com/vercel/next.js/issues/49001) - Simplify CNA prompts a bit: [#49063](https://togithub.com/vercel/next.js/issues/49063) - Update create-next-app App Router question: [#49111](https://togithub.com/vercel/next.js/issues/49111) - chore(docs): update next-image-unconfigured-host.md: [#49175](https://togithub.com/vercel/next.js/issues/49175) ##### Example Changes - docs: Fix path of '.env.template': [#49012](https://togithub.com/vercel/next.js/issues/49012) - chore: simplify repo templates: [#49073](https://togithub.com/vercel/next.js/issues/49073) ##### Misc Changes - chore: Update `swc_core` to `v0.75.41`: [#48982](https://togithub.com/vercel/next.js/issues/48982) - Fix failing test on `canary` branch: [#49038](https://togithub.com/vercel/next.js/issues/49038) - Remove unused font from tailwind `app/page.tsx`: [#49035](https://togithub.com/vercel/next.js/issues/49035) - Add test case for file uploads: [#49048](https://togithub.com/vercel/next.js/issues/49048) - chore(cli): remove Route Handlers from App Router templates: [#49076](https://togithub.com/vercel/next.js/issues/49076) - Fix flaky test: [#49178](https://togithub.com/vercel/next.js/issues/49178) - disable optimistic_updates: [#49211](https://togithub.com/vercel/next.js/issues/49211) - test: temporary disable flaky checking: [#49217](https://togithub.com/vercel/next.js/issues/49217) ##### Credits Huge thanks to [@kdy1](https://togithub.com/kdy1), [@alexkirsz](https://togithub.com/alexkirsz), [@sokra](https://togithub.com/sokra), [@shuding](https://togithub.com/shuding), [@dciug](https://togithub.com/dciug), [@albertothedev](https://togithub.com/albertothedev), [@DuCanhGH](https://togithub.com/DuCanhGH), [@feedthejim](https://togithub.com/feedthejim), [@li-jia-nan](https://togithub.com/li-jia-nan), [@styfle](https://togithub.com/styfle), [@kwonoj](https://togithub.com/kwonoj), [@patrick91](https://togithub.com/patrick91), [@timneutkens](https://togithub.com/timneutkens), [@balazsorban44](https://togithub.com/balazsorban44), [@ijjk](https://togithub.com/ijjk), [@padmaia](https://togithub.com/padmaia), [@Kikobeats](https://togithub.com/Kikobeats), [@huozhi](https://togithub.com/huozhi), [@sophiebits](https://togithub.com/sophiebits), [@eps1lon](https://togithub.com/eps1lon), [@reconbot](https://togithub.com/reconbot), [@acdlite](https://togithub.com/acdlite), [@jridgewell](https://togithub.com/jridgewell), and [@sebmarkbage](https://togithub.com/sebmarkbage) for helping!csstools/postcss-plugins
### [`v8.4.1`](https://togithub.com/csstools/postcss-plugins/blob/HEAD/plugin-packs/postcss-preset-env/CHANGELOG.md#841-May-19-2023) [Compare Source](https://togithub.com/csstools/postcss-plugins/compare/bc2c60b656f47ad0ab35a429d0ce8ee12601966a...c151f79e38a58a933988483c3a03f5840f392854) - Added `@csstools/postcss-relative-color-syntax` [Check the plugin README](https://togithub.com/csstools/postcss-plugins/tree/main/plugins/postcss-relative-color-syntax#readme) for usage details (really this time). ### [`v8.4.0`](https://togithub.com/csstools/postcss-plugins/blob/HEAD/plugin-packs/postcss-preset-env/CHANGELOG.md#840-May-19-2023) [Compare Source](https://togithub.com/csstools/postcss-plugins/compare/edb8cae6b10fd5eb2df29a23f223fcbcd48d7ea0...bc2c60b656f47ad0ab35a429d0ce8ee12601966a) - Added `@csstools/postcss-relative-color-syntax` [Check the plugin README](https://togithub.com/csstools/postcss-plugins/tree/main/plugins/postcss-relative-color-syntax#readme) for usage details. - Updated `cssdb` to `7.6.0.` (minor) - Updated `@csstools/postcss-progressive-custom-properties` to `2.2.0` (minor) - Updated `@csstools/postcss-ic-unit` to `2.0.3` (patch) - Updated `@csstools/postcss-text-decoration-shorthand` to `2.2.4` (patch) - Updated `postcss-double-position-gradients` to `4.0.3` (patch) - Updated `@csstools/postcss-color-function` to `2.2.2` (patch) - Updated `@csstools/postcss-color-mix-function` to `1.0.2` (patch) - Updated `@csstools/postcss-gradients-interpolation-method` to `3.0.5` (patch) - Updated `@csstools/postcss-hwb-function` to `2.2.2` (patch) - Updated `@csstools/postcss-oklab-function` to `2.2.2` (patch) - Updated `postcss-lab-function` to `5.2.2` (patch) ### [`v8.3.3`](https://togithub.com/csstools/postcss-plugins/blob/HEAD/plugin-packs/postcss-preset-env/CHANGELOG.md#833-May-19-2023) [Compare Source](https://togithub.com/csstools/postcss-plugins/compare/7a0d2dd22a92b026fd31e9604fb0b358ac52ccfc...edb8cae6b10fd5eb2df29a23f223fcbcd48d7ea0) - Update plugin order to preserve more original values. - Fix exception on unknown features [#969](https://togithub.com/csstools/postcss-plugins/issues/969) - Updated `@csstools/postcss-is-pseudo-class` to `3.2.1` (patch) - Updated `postcss-logical` to `6.2.0` (minor)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.