-
Notifications
You must be signed in to change notification settings - Fork 245
chore(deps): update dependency nuxt to v4 #605
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-nuxtjs-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1e9a33e
to
3a4fd0f
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #605 +/- ##
=======================================
Coverage 88.67% 88.67%
=======================================
Files 1 1
Lines 53 53
Branches 29 29
=======================================
Hits 47 47
Misses 6 6 ☔ View full report in Codecov by Sentry. |
31b20e9
to
d74d3fb
Compare
4031359
to
f107be7
Compare
f107be7
to
18f8ca5
Compare
18f8ca5
to
14fcfc5
Compare
14fcfc5
to
9def38b
Compare
9def38b
to
021fcdd
Compare
021fcdd
to
844ade4
Compare
844ade4
to
df1a63b
Compare
12c93c1
to
7485d43
Compare
a7d315b
to
fbb8142
Compare
fbb8142
to
0acbed5
Compare
0acbed5
to
d4fa629
Compare
4bb22d6
to
bd8d276
Compare
bd8d276
to
367173e
Compare
699241a
to
5458097
Compare
5458097
to
9e24fa9
Compare
9e24fa9
to
cd24b07
Compare
cd24b07
to
358105c
Compare
358105c
to
f05878b
Compare
f05878b
to
30a1bd3
Compare
30a1bd3
to
0adc771
Compare
0adc771
to
ca600d2
Compare
ca600d2
to
2f7d508
Compare
2f7d508
to
2ca1887
Compare
2ca1887
to
88742f5
Compare
88742f5
to
342a181
Compare
bc4f82c
to
0c5e31e
Compare
0c5e31e
to
0067bee
Compare
0067bee
to
f21f5bd
Compare
f21f5bd
to
cabe318
Compare
4f8d29a
to
250668c
Compare
250668c
to
cf91180
Compare
cf91180
to
df7fb25
Compare
df7fb25
to
66e5aeb
Compare
66e5aeb
to
e84934b
Compare
e84934b
to
54363f5
Compare
7c1a196
to
39fa534
Compare
39fa534
to
3bcaa0f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.15.8
->^4.0.1
Release Notes
nuxt/nuxt (nuxt)
v4.0.1
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🩹 Fixes
nuxt.schema
files to node tsconfig context (#32644)nitropack
(ed5ad64ad)shared/
dir (#32676)💅 Refactors
📖 Documentation
-t v4
tag from getting started (343f59235)noUncheckedIndexedAccess
rule change in v4 guide (#32643)📦 Build
nitropack
types as external (39be1b3a9)🏡 Chore
🤖 CI
❤️ Contributors
v4.0.0
Compare Source
Nuxt 4.0 is here! 🎉
After a year of real-world testing, we're excited to announce the official release of Nuxt 4. This is a stability-focused major release, introducing a few thoughtful breaking changes in order to improve development experience.
If you've been following along, you'll recognize many of these features and changes — and if you're new to them, we hope you'll welcome them.
🔥 What's new?
Nuxt 4 is all about making your development experience smoother:
app/
directory structureshared/
folder, and configurationWhy these features in particular? Mostly because these kind of improvements have required making changes that are technically breaking.
In general, we aim for a hype-free approach to releases. Rather than save up features for a big release, we've been shipping improvements in Nuxt 3 minor releases.
We've also spent a lot of time figuring out how to implement these changes in a backwards-compatible way, and I hope that means that most Nuxt 3 projects can upgrade with a minimum of effort.
I'd advise reading through the upgrade guide before you start, to understand what areas of your app might be affected.
🗂️ New project structure
The biggest visible change is how projects are organized. Your application code now lives in an
app/
directory by default:This helps keep your code separate from
node_modules/
and.git/
, which makes file watchers faster (especially on Windows and Linux). It also gives your IDE better context about whether you're working with client or server code.🎨 Updated UI templates
Nuxt’s starter templates have an all new look, with improved accessibility, default titles, and template polish (#27843).
🔄 Smarter data fetching
We've made
useAsyncData
anduseFetch
work better. Multiple components using the same key now share their data automatically. There's also automatic cleanup when components unmount, and you can use reactive keys to refetch data when needed. Plus, we've given you more control over when cached data gets used.Some of these features have already been made available in Nuxt v3 minor releases, because we've been rolling this out gradually. Nuxt v4 brings different defaults, and we expect to continue to work on this data layer in the days to come.
🔧 Better TypeScript experience
Nuxt now creates separate TypeScript projects for your app code, server code,
shared/
folder, and builder code. This should mean better autocompletion, more accurate type inference and fewer confusing errors when you're working in different contexts.This is probably the single issue that is most likely to cause surprises when upgrading, but it should also make your TypeScript experience much smoother in the long run. Please report any issues you encounter. 🙏
⚡ Faster CLI and development
In parallel with the release of v4, we've been working on speeding up
@nuxt/cli
.fs.watch
APIs for fewer system resourcesThese improvements combined can make a really noticeable difference in your day-to-day development experience, and we have more planned.
🚀 How to upgrade
Although any major release brings breaking changes, one of our main aims for this release is to ensure that the upgrade path is as smooth as possible. Most of the breaking changes have been testable with a compatibility flag for over a year.
Most projects should upgrade smoothly, but there are a few things to be aware of:
@nuxt/kit
. (This will particularly affect module authors.)Don't worry though — for most breaking changes, there are configuration options to revert to the old behavior while you adjust.
1. Update Nuxt
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
2. Optional: use migration tools
We’ve also partnered with Codemod to automate many, though not all, migration steps:
3. Test and adjust
Run your tests, check that everything builds correctly, and fix any issues that come up. The upgrade guide has detailed migration steps for specific scenarios.
We'd recommend reading through it in full before starting your upgrade, to understand what areas of your app might be affected.
🗺️ What's next?
We're planning quick patch releases to address any issues that come up. Nuxt 3 will continue to receive maintenance updates (both bug fixes and backports of features from Nuxt 4) until the end of January 2026, so there's no rush if you need time to migrate.
Looking ahead, we plan to release Nuxt 5 on the sooner side, which will bring Nitro v3 and h3 v2 for even better performance, as well as adopting the Vite Environment API for an improved (and faster!) development experience. And there's a lot more in the works too!
And, quite apart from major releases, we have a lot of exciting features planned to make their way into Nuxt 3.x and 4.x release branches, including support for SSR streaming (#4753), a first-party accessibility module (#23255), built-in fetch caching strategies (#26017), more strongly typed fetch calls (landing in Nitro v3), dynamic route discovery (#32196), multi-app support (#21635) and more.
❤️ Thank you
This release is credit to so many people, particularly those who have been testing v4 compatibility mode over the past year. I'm really grateful — thank you for all your help!
Happy coding with Nuxt 4! 🚀
👉 Changelog
compare changes
🚀 Enhancements
mlly
(#28012)addServerImports
(#32289)onWatcherCleanup
to imports presets (#32396)<NuxtTime>
prop types (#32547)🔥 Performance
render:html
for server islands (#27889)🩹 Fixes
compatibilityVersion: 4
(#27710)builder:watch
hook (#27709)asyncData
value behaviour (#27718)__NUXT__
after hydration (#27745)4
(7aae4033b)resolvePath
utils as sync (655e1473d)tryResolveModule
(2d136e04c)requireModule
andtryRequireModule
(#28013)useScriptCrisp
scripts stub (0c3cc4cf3)globalName
property (#28391)updateAppConfig
in HMR (#28349)ssr: false
(#28488)window
access (d874726ff)resolveId
fromvite-node
to resolve deps (#30922)isEqual
from mainohash
export (3ec1a1e5e)output.preserveModules
(ce49734aa)#app-manifest
import in dev mode (#31539)purgeCachedData
until v4 (7aa3a01ae)purgeCachedData
by default (06745604c).execute
(d79e14612)compatibilityVersion: 3
(#32255)useAsyncData
(#32170)errorValue
/value
to be undefined (7e4eac655)srcDir
(#32487)@nuxt/cli
(#32488)tsConfig
doesn't exclude too many types (#32528)app/
andserver/
folders into tsconfigs (#32592)typescript.hoist
(#32601)tsconfig.server.json
(#32594)compatibilityDate
to2025-07-15
(e35e1ccb9)scrollBehaviorType
for hash scrolling (#32622)💅 Refactors
#app/components/layout
->#app/components/nuxt-layout
(209e81b60)dedupe
option (#28151)installNuxtModule
(501ccc375)oxc-walker
(#32250)onPrehydrate
transform (#32045)📖 Documentation
useAsyncData
must return (#28259)deep
default foruseAsyncData
&useFetch
(#28564)deep
option (bec85dfcd).nuxtignore
examples for v4 structure (#32489)useNuxtData
in data fetching composable pages (#32589)📦 Build
🏡 Chore
vite-plugin-checker
separately (02d46dd3d)engines.node
compatibility (a26322f5f)nuxi
(9aa4c7c3b)nuxi
version again (#30547)oxc-parser
updates temporarily (1cd0fb5cb)nitro/templates
directory (e531477f8)✅ Tests
attw
test for built packages (#30206)configResolved
(8d3bd4f9f)🤖 CI
render:html
for server islands (#27889)compatibilityVersion: 4
(#27710)builder:watch
hook (#27709)asyncData
value behaviour (#27718)__NUXT__
after hydration (#27745)4
(7aae4033b)globalName
property (#28391)compatibilityVersion: 3
(#32255)useAsyncData
(#32170)compatibilityDate
to2025-07-15
(e35e1ccb9)#app/components/layout
->#app/components/nuxt-layout
(209e81b60)❤️ Contributors
v3.17.7
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🩹 Fixes
extraPageMetaExtractionKeys
(#32510)loadBuilder
error cause (8f13ce3c2)null
values (c1b83eab5)semver.satisfies
returns true for pre-release versions (#32574)execute being passed to
watch` (#32591)📖 Documentation
NUXT_
(#32223)useAsyncData
anduseFetch
migration (#32560)undefined
tonull
in v3 docs (#32562)async
keyword (#32587)✅ Tests
generateTypes
(c0855439d)<NuxtTime>
test (#32558)❤️ Contributors
v3.17.6
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
nuxt.config
(#32324)nuxt:chunk-reload-immediate
(#32382)set-cookie
headers in error handler (#32483)asyncData
runs if changing key while fetcher is running (#32466)navigateTo
(#32393)<NuxtLink>
's custom on click handler (#32499)inheritAttrs: false
increateClientOnly
fn (#32323)output.generatedCode.symbols
for nitro build (#32358)💅 Refactors
📖 Documentation
h3js
(#32243)clear
function description (#32287)defineNuxtPlugin
function documentation (#32328)<NuxtLink>
encodes query params (#32361)bun.lock
for lockfile (#32427)🏡 Chore
workspace
toprojects
(#32388)✅ Tests
immediate: false
(#32473)🤖 CI
❤️ Contributors
v3.17.5
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
globby
(#31688)🩹 Fixes
useScriptRybbitAnalytics
from script stubs (d275ae1a0)appConfig
sources are not duplicated (#32216)h()
in ClientOnly (#30664)asyncData
state from nuxt app instance (#32232)srcDir
inbuildCache
(#32260)asyncData
watcher (#32247)📖 Documentation
addRouteMiddleware
path in example (#32171)--env-file
(29f6392cd)nuxt
command consistently (#32237)alert
withwarning
in/guide/pages
(#32270)📦 Build
🏡 Chore
✅ Tests
❤️ Contributors
v3.17.4
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
shallowRef
for primitive values (#32152)Intl.Collator
instead oflocaleCompare
(#32167)🩹 Fixes
<ClientOnly>
(#32101)useLazyAsyncData
(#32092)ts-checker-rspack-plugin
(#32115)/
(#32129)DeepPartial
(#31990)<ClientOnly>
(#32131)global
withglobalThis
(#32130)<NuxtLayout>
first renders (#24673)srcDir
to parcel strategy (#32139)📖 Documentation
useNuxtData
default return toundefined
(#32054)imports.dirs
with alias (0dbf314d9)🏡 Chore
✅ Tests
setTimeout
mock (#32142)🤖 CI
❤️ Contributors
v3.17.3
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
FormData
(#32013)ignore
patterns (#32020)useFetch
withwatch: false
(#32019)getCachedData
is provided (#32003)nuxtApp
for asyncData functions run on server (#32038)💅 Refactors
asyncData
(e779d6cd5)📖 Documentation
🤖 CI
bug
/enhancement
labels to issue types (3ff743fe0)❤️ Contributors
v3.17.2
Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
handleHotUpdate
in production (#31971)🩹 Fixes
transition
(#31945)useFetch
(#31963)scrollToTop
(#31914)vfs
even if a file exists inbuildDir
(#31969)useAsyncData
reactive tokey
changes whenimmediate: false
(#31987)WarningFilter
type (2a79dbd68)warningIgnoreFilters
(a62e808ac)📖 Documentation
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.
🔕 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.