mx-space / kami

🍰 Kami is mx-space's web frontend theme. Colorful, flat, cute and comfortable.
https://kami.innei.ren
GNU General Public License v3.0
317 stars 54 forks source link

chore(deps): update nextjs monorepo to v13.3.3 (patch) - autoclosed #1672

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@next/bundle-analyzer 13.3.1 -> 13.3.3 age adoption passing confidence
next (source) 13.3.1 -> 13.3.3 age adoption passing confidence

Release Notes

vercel/next.js ### [`v13.3.3`](https://togithub.com/vercel/next.js/releases/tag/v13.3.3) [Compare Source](https://togithub.com/vercel/next.js/compare/v13.3.2...v13.3.3) ##### Core Changes - Fix duplicated Edge Runtime warnings: [#​48987](https://togithub.com/vercel/next.js/issues/48987) - Update type of preferredRegion: [#​49003](https://togithub.com/vercel/next.js/issues/49003) - Remove unused context providers: [#​48267](https://togithub.com/vercel/next.js/issues/48267) - Update TS plugin type for `preferredRegion`: [#​49011](https://togithub.com/vercel/next.js/issues/49011) - Fix CSS ordering issue with HMR: [#​49010](https://togithub.com/vercel/next.js/issues/49010) ##### Credits Huge thanks to [@​shuding](https://togithub.com/shuding), and [@​timneutkens](https://togithub.com/timneutkens) for helping! ### [`v13.3.2`](https://togithub.com/vercel/next.js/releases/tag/v13.3.2) [Compare Source](https://togithub.com/vercel/next.js/compare/v13.3.1...v13.3.2) ##### Core Changes - Refactor require hooks: [#​48506](https://togithub.com/vercel/next.js/issues/48506) - Use `decodeReplyFromBusboy` in node runtime: [#​48686](https://togithub.com/vercel/next.js/issues/48686) - Do not suggest adding "use client" if using next/router in app: [#​48680](https://togithub.com/vercel/next.js/issues/48680) - Reland "app-router: new client-side cache semantics": [#​48695](https://togithub.com/vercel/next.js/issues/48695) - fix: TS plugin showing warning for `global-error` file's `reset` prop: [#​48756](https://togithub.com/vercel/next.js/issues/48756) - Add support for draft mode: [#​48669](https://togithub.com/vercel/next.js/issues/48669) - Compile Next.js core client-side files using default target: [#​48750](https://togithub.com/vercel/next.js/issues/48750) - Lazy DevHtmlAsset chunk generation: [#​48768](https://togithub.com/vercel/next.js/issues/48768) - Update naming for Next.js Analytics: [#​48618](https://togithub.com/vercel/next.js/issues/48618) - Add support for async instrumentation register: [#​48575](https://togithub.com/vercel/next.js/issues/48575) - Prefer realpathSync.native over realpathSync: [#​48698](https://togithub.com/vercel/next.js/issues/48698) - Fix issue with instrumentation in a standalone build: [#​48615](https://togithub.com/vercel/next.js/issues/48615) - Polyfill `FormData` for Node.js < 18: [#​48783](https://togithub.com/vercel/next.js/issues/48783) - Error on legacy runtime config under app dir: [#​48774](https://togithub.com/vercel/next.js/issues/48774) - Fix Windows path in route join ([#​48603](https://togithub.com/vercel/next.js/issues/48603)): [#​48779](https://togithub.com/vercel/next.js/issues/48779) - Add missing `repository` prop to package.json: [#​48803](https://togithub.com/vercel/next.js/issues/48803) - fix: Update `@swc/helpers` to `v0.5.1`: [#​48808](https://togithub.com/vercel/next.js/issues/48808) - Fix hash apply after server-patch action: [#​48813](https://togithub.com/vercel/next.js/issues/48813) - Improve typing of resolve metadata: [#​48670](https://togithub.com/vercel/next.js/issues/48670) - Only track client entry modules in the client reference manifest: [#​48814](https://togithub.com/vercel/next.js/issues/48814) - Vendor `react@experimental`: [#​48697](https://togithub.com/vercel/next.js/issues/48697) - fix query for app dir in turbopack: [#​48828](https://togithub.com/vercel/next.js/issues/48828) - Polyfill FormData with edge-runtime primitives: [#​48826](https://togithub.com/vercel/next.js/issues/48826) - Add async context to server request handler: [#​48626](https://togithub.com/vercel/next.js/issues/48626) - Fix accessing `strict` of undefined in `writeConfigurationDefaults`: [#​48799](https://togithub.com/vercel/next.js/issues/48799) - update turbopack: [#​48846](https://togithub.com/vercel/next.js/issues/48846) - Fix issues where saving next.config.js too quickly could result in multiple dev servers running at once: [#​48857](https://togithub.com/vercel/next.js/issues/48857) - Fix scrolling on navigation in app: [#​48863](https://togithub.com/vercel/next.js/issues/48863) - Implement MutableRequestCookies in server entries: [#​48847](https://togithub.com/vercel/next.js/issues/48847) - refactor(next-swc): turbopack_ecmascript_plugins: [#​48671](https://togithub.com/vercel/next.js/issues/48671) - edge: expose Websocket constructor: [#​48870](https://togithub.com/vercel/next.js/issues/48870) - add missing aliases for next/dynamic and next/head: [#​48871](https://togithub.com/vercel/next.js/issues/48871) - Update the mutableCookies class to accept extra options: [#​48877](https://togithub.com/vercel/next.js/issues/48877) - Support generate dynamic sitemaps for dynamic routes: [#​48867](https://togithub.com/vercel/next.js/issues/48867) - refactor(next-core): emit unsupported package warning: [#​48837](https://togithub.com/vercel/next.js/issues/48837) - update turbopack: [#​48893](https://togithub.com/vercel/next.js/issues/48893) - External vercel og for nodejs runtime: [#​48844](https://togithub.com/vercel/next.js/issues/48844) - Make prefetch not async: [#​48897](https://togithub.com/vercel/next.js/issues/48897) - Ensure require-hook env is set properly on deploy: [#​48902](https://togithub.com/vercel/next.js/issues/48902) - add support for static implicit metadata in turbopack: [#​48823](https://togithub.com/vercel/next.js/issues/48823) - Update min Node.js version to v16: [#​48903](https://togithub.com/vercel/next.js/issues/48903) - Fix scrolling when invisible element is targeted: [#​48874](https://togithub.com/vercel/next.js/issues/48874) - Preload css: [#​48840](https://togithub.com/vercel/next.js/issues/48840) - Selectively load runtime CSS modules to avoid rule duplication: [#​48866](https://togithub.com/vercel/next.js/issues/48866) - Ensure **PAGE** is checked in all cases: [#​48862](https://togithub.com/vercel/next.js/issues/48862) - add missing exports for static generation bailout: [#​48910](https://togithub.com/vercel/next.js/issues/48910) - Change Server Reference creation on client: [#​48824](https://togithub.com/vercel/next.js/issues/48824) - Upgrade Edge Runtime: [#​46818](https://togithub.com/vercel/next.js/issues/46818) - fix: explicit undefined typecheck: [#​48920](https://togithub.com/vercel/next.js/issues/48920) - fix: Enable CJS annotations for next.js files: [#​48811](https://togithub.com/vercel/next.js/issues/48811) - turbopack: parse and propagate `output: 'export'`: [#​48046](https://togithub.com/vercel/next.js/issues/48046) - fixes [#​48794](https://togithub.com/vercel/next.js/issues/48794) : When using pageExtensions like "page.jsx", global css import not working: [#​48795](https://togithub.com/vercel/next.js/issues/48795) - chore: expose `globalThis.crypto` when not available: [#​48941](https://togithub.com/vercel/next.js/issues/48941) - Fix dynamic routes for generateImageMetadata: [#​48928](https://togithub.com/vercel/next.js/issues/48928) - Correct some jest types: [#​48923](https://togithub.com/vercel/next.js/issues/48923) - Error for missing dynamic generated id and refactor metadata image url: [#​48953](https://togithub.com/vercel/next.js/issues/48953) - fix: bump minimum Node.js version to 16.8.0: [#​48957](https://togithub.com/vercel/next.js/issues/48957) - allow using the `nodejs` runtime for route handlers when using turbopack: [#​48791](https://togithub.com/vercel/next.js/issues/48791) - fix(turbopack): ignore underscore_started path: [#​48792](https://togithub.com/vercel/next.js/issues/48792) - Use ProxiedAsset instead of css_chunk_root_path to expose RSC CSS chunks: [#​48946](https://togithub.com/vercel/next.js/issues/48946) - Remove un-necessary undici warnings: [#​48970](https://togithub.com/vercel/next.js/issues/48970) - Ensure WebSocket is polyfilled for node runtime as well: [#​48924](https://togithub.com/vercel/next.js/issues/48924) - Support preferredRegion and Support runtime/preferredRegion on layouts: [#​48959](https://togithub.com/vercel/next.js/issues/48959) - preload fonts using ReactDOM.preload: [#​48931](https://togithub.com/vercel/next.js/issues/48931) - Cleanup "started server on" message: [#​48972](https://togithub.com/vercel/next.js/issues/48972) - add image metadata for svg: [#​48947](https://togithub.com/vercel/next.js/issues/48947) - fix: error when image `width={Infinity}`: [#​48855](https://togithub.com/vercel/next.js/issues/48855) - add test case for esm commonjs interop: [#​48940](https://togithub.com/vercel/next.js/issues/48940) - Update resolve rule for `@swc/helpers`: [#​48980](https://togithub.com/vercel/next.js/issues/48980) - Update google fonts: [#​48984](https://togithub.com/vercel/next.js/issues/48984) - Fix scroll when loading.js/ts is used: [#​48986](https://togithub.com/vercel/next.js/issues/48986) - Add test case for [#​48506](https://togithub.com/vercel/next.js/issues/48506): [#​48696](https://togithub.com/vercel/next.js/issues/48696) - Add npm package provenance on publish: [#​48693](https://togithub.com/vercel/next.js/issues/48693) - Revert "Add npm package provenance on publish ([#​48693](https://togithub.com/vercel/next.js/issues/48693))" - fix: npm publish provenance permissions: [#​48757](https://togithub.com/vercel/next.js/issues/48757) - Add missing `repository` prop to package.json in swc-wasm: [#​48805](https://togithub.com/vercel/next.js/issues/48805) - test: disable client cache flaky test: [#​48890](https://togithub.com/vercel/next.js/issues/48890) ##### Documentation Changes - typo: [#​48716](https://togithub.com/vercel/next.js/issues/48716) - docs: update Image props: [#​48726](https://togithub.com/vercel/next.js/issues/48726) - Fix typo in `errors/version-staleness.md`: [#​48797](https://togithub.com/vercel/next.js/issues/48797) - Add missing word to getStaticProps documentation: [#​48854](https://togithub.com/vercel/next.js/issues/48854) - update example Deploy button URLs: [#​48842](https://togithub.com/vercel/next.js/issues/48842) - Start recommending gRPC with otel: [#​48915](https://togithub.com/vercel/next.js/issues/48915) ##### Credits Huge thanks to [@​shuding](https://togithub.com/shuding), [@​huozhi](https://togithub.com/huozhi), [@​wyattfry](https://togithub.com/wyattfry), [@​styfle](https://togithub.com/styfle), [@​sreetamdas](https://togithub.com/sreetamdas), [@​afonsojramos](https://togithub.com/afonsojramos), [@​timneutkens](https://togithub.com/timneutkens), [@​alexkirsz](https://togithub.com/alexkirsz), [@​chriswdmr](https://togithub.com/chriswdmr), [@​jankaifer](https://togithub.com/jankaifer), [@​pn-code](https://togithub.com/pn-code), [@​kdy1](https://togithub.com/kdy1), [@​sokra](https://togithub.com/sokra), [@​kwonoj](https://togithub.com/kwonoj), [@​martin-wahlberg](https://togithub.com/martin-wahlberg), [@​Kikobeats](https://togithub.com/Kikobeats), [@​JTaylor0196](https://togithub.com/JTaylor0196), [@​sebmarkbage](https://togithub.com/sebmarkbage), [@​ijjk](https://togithub.com/ijjk), [@​gnoff](https://togithub.com/gnoff), [@​jridgewell](https://togithub.com/jridgewell), [@​sagarpreet-xflowpay](https://togithub.com/sagarpreet-xflowpay), [@​balazsorban44](https://togithub.com/balazsorban44), [@​cprussin](https://togithub.com/cprussin), [@​ForsakenHarmony](https://togithub.com/ForsakenHarmony), and [@​li-jia-nan](https://togithub.com/li-jia-nan) for helping!

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.



This PR has been generated by Mend Renovate. View repository job log here.

github-actions[bot] commented 1 year ago

📦 Next.js Bundle Analysis for mx-kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 195.24 KB (🟢 -873 B)
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!

Twenty 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 (350 KB)
/ 36 KB 231.24 KB 66.07% (🟡 +0.06%)
/[page] 18.23 KB 213.47 KB 60.99% (🟡 +0.06%)
/_error 740 B 195.96 KB 55.99% (+/- <0.01%)
/categories/[slug] 6.23 KB 201.47 KB 57.56% (🟡 +0.07%)
/favorite/bangumi 1.26 KB 196.5 KB 56.14% (+/- <0.01%)
/favorite/music 4.21 KB 199.44 KB 56.98% (+/- <0.01%)
/friends 18.44 KB 213.68 KB 61.05% (🟢 -0.01%)
/login 4.21 KB 199.44 KB 56.98% (+/- <0.01%)
/notes 355 B 195.58 KB 55.88% (+/- <0.01%)
/notes/[id] 40.11 KB 235.34 KB 67.24% (🟡 +0.06%)
/notes/topics 5.04 KB 200.28 KB 57.22% (🟡 +0.06%)
/notes/topics/[topicSlug] 7.42 KB 202.66 KB 57.90% (🟡 +0.06%)
/posts 23.71 KB 218.94 KB 62.56% (🟡 +0.06%)
/posts/[category]/[slug] 40.79 KB 236.03 KB 67.44% (🟡 +0.05%)
/preview 20.43 KB 215.66 KB 61.62% (🟢 -0.01%)
/projects 3.75 KB 198.99 KB 56.85% (🟡 +0.07%)
/projects/[id] 14.55 KB 209.78 KB 59.94% (🟢 -0.01%)
/recently 63.25 KB 258.49 KB 73.85% (🟡 +0.05%)
/says 10.47 KB 205.71 KB 58.77% (+/- <0.01%)
/timeline 15.79 KB 211.02 KB 60.29% (🟡 +0.06%)
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.

github-actions[bot] commented 1 year ago

📦 Next.js Bundle Analysis for mx-kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 195.24 KB (🟢 -873 B)
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!

Twenty 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 (350 KB)
/ 36 KB 231.24 KB 66.07% (🟡 +0.06%)
/[page] 18.23 KB 213.47 KB 60.99% (🟡 +0.06%)
/_error 740 B 195.96 KB 55.99% (+/- <0.01%)
/categories/[slug] 6.23 KB 201.47 KB 57.56% (🟡 +0.07%)
/favorite/bangumi 1.26 KB 196.5 KB 56.14% (+/- <0.01%)
/favorite/music 4.21 KB 199.44 KB 56.98% (+/- <0.01%)
/friends 18.44 KB 213.68 KB 61.05% (🟢 -0.01%)
/login 4.21 KB 199.44 KB 56.98% (+/- <0.01%)
/notes 355 B 195.58 KB 55.88% (+/- <0.01%)
/notes/[id] 40.11 KB 235.34 KB 67.24% (🟡 +0.06%)
/notes/topics 5.04 KB 200.28 KB 57.22% (🟡 +0.06%)
/notes/topics/[topicSlug] 7.42 KB 202.66 KB 57.90% (🟡 +0.06%)
/posts 23.71 KB 218.94 KB 62.56% (🟡 +0.06%)
/posts/[category]/[slug] 40.79 KB 236.03 KB 67.44% (🟡 +0.05%)
/preview 20.43 KB 215.66 KB 61.62% (🟢 -0.01%)
/projects 3.75 KB 198.99 KB 56.85% (🟡 +0.07%)
/projects/[id] 14.55 KB 209.78 KB 59.94% (🟢 -0.01%)
/recently 63.25 KB 258.49 KB 73.85% (🟡 +0.05%)
/says 10.47 KB 205.71 KB 58.77% (+/- <0.01%)
/timeline 15.79 KB 211.02 KB 60.29% (🟡 +0.06%)
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.

github-actions[bot] commented 1 year ago

📦 Next.js Bundle Analysis for mx-kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 195.3 KB (🟢 -869 B)
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!

Twenty 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 (350 KB)
/ 36 KB 231.3 KB 66.09% (🟡 +0.05%)
/[page] 18.23 KB 213.53 KB 61.01% (🟡 +0.05%)
/_error 740 B 196.02 KB 56.01% (+/- <0.01%)
/categories/[slug] 6.23 KB 201.53 KB 57.58% (🟡 +0.06%)
/favorite/bangumi 1.26 KB 196.56 KB 56.16% (+/- <0.01%)
/favorite/music 4.21 KB 199.5 KB 57.00% (+/- <0.01%)
/friends 18.44 KB 213.74 KB 61.07% (🟢 -0.01%)
/login 4.21 KB 199.51 KB 57.00% (+/- <0.01%)
/notes 355 B 195.65 KB 55.90% (+/- <0.01%)
/notes/[id] 40.11 KB 235.41 KB 67.26% (🟡 +0.05%)
/notes/topics 5.04 KB 200.34 KB 57.24% (🟡 +0.06%)
/notes/topics/[topicSlug] 7.42 KB 202.72 KB 57.92% (🟡 +0.06%)
/posts 23.71 KB 219.01 KB 62.57% (🟡 +0.07%)
/posts/[category]/[slug] 40.79 KB 236.09 KB 67.45% (🟡 +0.06%)
/preview 20.43 KB 215.73 KB 61.64% (🟢 -0.01%)
/projects 3.75 KB 199.05 KB 56.87% (🟡 +0.06%)
/projects/[id] 14.55 KB 209.85 KB 59.96% (🟢 -0.01%)
/recently 63.25 KB 258.55 KB 73.87% (🟡 +0.05%)
/says 10.47 KB 205.77 KB 58.79% (+/- <0.01%)
/timeline 15.79 KB 211.08 KB 60.31% (🟡 +0.06%)
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.

github-actions[bot] commented 1 year ago

📦 Next.js Bundle Analysis for mx-kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 195.3 KB (🟢 -871 B)
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!

Twenty 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 (350 KB)
/ 36 KB 231.29 KB 66.08% (🟡 +0.06%)
/[page] 18.23 KB 213.53 KB 61.01% (🟡 +0.05%)
/_error 740 B 196.02 KB 56.01% (+/- <0.01%)
/categories/[slug] 6.23 KB 201.53 KB 57.58% (🟡 +0.06%)
/favorite/bangumi 1.26 KB 196.56 KB 56.16% (+/- <0.01%)
/favorite/music 4.21 KB 199.5 KB 57.00% (+/- <0.01%)
/friends 18.44 KB 213.74 KB 61.07% (🟢 -0.01%)
/login 4.21 KB 199.5 KB 57.00% (+/- <0.01%)
/notes 355 B 195.64 KB 55.90% (+/- <0.01%)
/notes/[id] 40.11 KB 235.4 KB 67.26% (🟡 +0.05%)
/notes/topics 5.04 KB 200.34 KB 57.24% (🟡 +0.06%)
/notes/topics/[topicSlug] 7.42 KB 202.72 KB 57.92% (🟡 +0.06%)
/posts 23.71 KB 219 KB 62.57% (🟡 +0.07%)
/posts/[category]/[slug] 40.79 KB 236.09 KB 67.45% (🟡 +0.06%)
/preview 20.43 KB 215.72 KB 61.64% (🟢 -0.01%)
/projects 3.75 KB 199.05 KB 56.87% (🟡 +0.06%)
/projects/[id] 14.55 KB 209.84 KB 59.96% (🟢 -0.01%)
/recently 63.25 KB 258.55 KB 73.87% (🟡 +0.05%)
/says 10.47 KB 205.77 KB 58.79% (+/- <0.01%)
/timeline 15.79 KB 211.08 KB 60.31% (🟡 +0.06%)
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.

github-actions[bot] commented 1 year ago

📦 Next.js Bundle Analysis for mx-kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 195.23 KB (🟢 -940 B)
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!

Nineteen 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 (350 KB)
/ 36 KB 231.22 KB 66.06% (🟡 +0.06%)
/[page] 18.23 KB 213.46 KB 60.99% (🟡 +0.05%)
/categories/[slug] 6.22 KB 201.45 KB 57.56% (🟡 +0.06%)
/favorite/bangumi 1.26 KB 196.49 KB 56.14% (+/- <0.01%)
/favorite/music 4.21 KB 199.44 KB 56.98% (+/- <0.01%)
/friends 18.44 KB 213.67 KB 61.05% (🟢 -0.01%)
/login 4.21 KB 199.44 KB 56.98% (+/- <0.01%)
/notes 355 B 195.58 KB 55.88% (+/- <0.01%)
/notes/[id] 40.08 KB 235.31 KB 67.23% (🟡 +0.05%)
/notes/topics 5.05 KB 200.27 KB 57.22% (🟡 +0.06%)
/notes/topics/[topicSlug] 7.42 KB 202.65 KB 57.90% (🟡 +0.06%)
/posts 23.7 KB 218.93 KB 62.55% (🟡 +0.06%)
/posts/[category]/[slug] 40.77 KB 236 KB 67.43% (🟡 +0.05%)
/preview 20.42 KB 215.64 KB 61.61% (🟢 -0.01%)
/projects 3.75 KB 198.97 KB 56.85% (🟡 +0.06%)
/projects/[id] 14.55 KB 209.78 KB 59.94% (🟢 -0.01%)
/recently 63.26 KB 258.49 KB 73.85% (🟡 +0.06%)
/says 10.47 KB 205.7 KB 58.77% (+/- <0.01%)
/timeline 15.78 KB 211.01 KB 60.29% (🟡 +0.06%)
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.