-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency next to v15 #148
base: main
Are you sure you want to change the base?
Conversation
📦 Next.js Bundle Analysis for www.napochaan.comThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
77.73 KB (🟡 +701 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!
One Page Changed Size
The following page changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load | % of Budget (350 KB ) |
---|---|---|---|
/_error |
189 B |
77.92 KB | 22.26% (+/- <0.01%) |
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.
2743e92
to
0106366
Compare
📦 Next.js Bundle Analysis for www.napochaan.comThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
78.7 KB (🟡 +1.66 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
One Page Changed Size
The following page changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load | % of Budget (350 KB ) |
---|---|---|---|
/_error |
190 B |
78.89 KB | 22.54% (+/- <0.01%) |
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.
0106366
to
2208efd
Compare
📦 Next.js Bundle Analysis for www.napochaan.comThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
78.7 KB (🟡 +1.66 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
One Page Changed Size
The following page changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load | % of Budget (350 KB ) |
---|---|---|---|
/_error |
190 B |
78.89 KB | 22.54% (+/- <0.01%) |
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.
This PR contains the following updates:
^14.1.4
->^15.0.0
Release Notes
vercel/next.js (next)
v15.1.0
Compare Source
Core Changes
server-source-maps
scenarios to cover Edge runtime: #72288swc_css
: #72602rc
from URL: #72599no-img-element
lint error message: #72410"use cache"
closure args into a single parameter: #72587"use cache"
functions: #72506clientSegmentCache
flag: #72626compiler.define
option: #71802getting-started/react-essentials
path: #722505.6.3
: #72625@capsizecss/metrics
to 3.4.0 for Geist Google Font: #72746enabled
config from server actions transforms: #72755eslint-plugin-react
to 7.37.0: #727595c56b873-20241107
to7ac8e612-20241113
: #72768"use cache"
is used withoutdynamicIO
enabled: #72781legacy-js-api
warning: #726327ac8e612-20241113
to380f5d67-20241113
: #72819revalidate(Tag|Path)
toexpire(Tag|Path)
: #72826prefetch
API: #72861next-size-adjust
meta tag: #72994typedEnv
: #70951next start
: #73105380f5d6
-20241113 tob01722d
-20241114: #73107exactOptionalPropertyTypes
: #72936revalidate(Tag|Path)
toexpire(Tag|Path)
": #73269notFound()
work in"use cache"
page: #73210@swc/core
to 1.9.3: #73420warnOnce()
: #73483b01722d5-20241114
to1b1283ad-20241203
: #735061b1283ad-20241203
tode68d2f4-20241204
: #73525@types/react
: #73563de68d2f4-20241204
to1c9b1387-20241204
: #73565unstable_after
: #736051c9b1387-20241204
to7283a213-20241206
: #73608warnOnce()
lru: #73742Example Changes
playwright
.gitignore: #72447await
params when dynamic routing: #72896app-dir
ini18n-routing
directory name: #73453examples/**
Eslint to v9: #73560next-env.d.ts
files: #73673with-sass
README.md: #73668next-offline
example: #73675with-postgres
: #73587with-emotion-*
directories: #73674with-styletron
README.md: #73411with-babel-macros
README.md: #73410with-plausible
README: #73305image-legacy-component
: #73414with-styled-components-babel
: #73229with-storybook-styled-jsx-scss
: #73228Misc Changes
next.config.js
API pages under aconfig
folder, fix headings in TS and ESLint config pages: #72465return Err(anyhow!())
withanyhow::bail!()
: #7248766855b96-20241106
to5c56b873-20241107
: #72469swc_core
tov5.0.4
fromv5.0.1
: #72604patchFileDelay
flag: #72439function
to page component examples: #72620ResolvedVc
forturbopack
crate: #72791@container
: #72607emit_error
function: #72811ResolvedVc
forturbopack-ecmascript
: #72564rootDir
doc: #72893frameborder
, adjustallowFullScreen
and update the demo: #72644customServer
flag from custom server docs: #72962FnExpr
andFnDecl
server function transforms: #72960debug
script in test directories: #72992all_modules_and_affecting_sources
helper function: #73016retry
aroundbrowser.eval
: #72999await
when using params: #73044params.id
: #73045Redirecting
fix route handler path: #72617waitForAndOpenRuntimeError
toopenRedbox
: #72996expirePath
andexpireTag
: #73096"use memo"
: #73053this
andarguments
in server functions: #73059lightningcss
tov1.0.0-alpha.61
: #73161forbidden
,unauthorized
, andauthInterrupts
: #73039.eslintrc.json
witheslint.config.mjs
: #73162ResolvedVc
forturbopack-css
: #73172ResolvedVc
forturbopack-core
: #73065ResolvedVc
forturbopack
,turbopack-tests
,turbopack-wasm
: #73196ResolvedVc
forturbopack-nodejs
: #73200ResolvedVc
forturbopack-env
: #73202forbidden
andunauthorized
nits: #73213turbopack
API Reference: #73215super
in static class methods with server function directives: #73061ResolvedVc
fornext-api
, part 1: #73234ResolvedVc
fornext-api
, part 2: #73235params
toawait params
: #73254Layouts and Pages
: #73268ResolvedVc
fornext-api
, part 3: #73236ResolvedVc
fornext-api
, part 4: #73237ResolvedVc
forturbopack-browser
: #73198ResolvedVc
fornext-core
: #73177ResolvedVc
fornext-api
, part 5: #73238Vc<T>
in turbo-tasks types: #73298nwsapi
(revert later): #73351nwsapi
(revert later)": #73353ResolvedVc<T>
for struct fields innext-core
: #73310ResolvedVc<T>
for struct fields inturbopack-ecmascript
: #73302ResolvedVc<T>
for struct fields inturbopack-css
: #73300ResolvedVc<T>
for struct fields innext-api
, part 1: #73366default
to page component examples: #73233.gitignore
to ignore all.env
files: #73415swcMinify
flag: #73281file conventions
,functions
, anderrors
: #73376Images and Fonts
feedback: #73470ResolvedVc<T>
for struct fields inturbopack-core
: #73301ResolvedVc<T>
for struct fields inturbo-tasks
: #73371ResolvedVc<T>
for trivial struct fields: #73372check
toretry
in hmr.test.ts: #73590unoptimized
: #73604ResolvedVc<T>
for struct fields in extra crates: #73451ResolvedVc<T>
for struct fields innext-api
, final part: #73367.to_resolved()
calls: #73631canary
page to upgrade guides: #73518with-next-sass
towith-sass
: #73670turbopack-dev-examples-manifest
: #73230build_and_deploy
on docs-only changes: #73659after
: #73692forbidden
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone Asia/Tokyo, 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.