chore(deps): update nuxt framework to ^3.6.1 #42
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
f970cb8
to
247bb61
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
247bb61
to
dd5781d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^3.5.3->^3.6.1^3.5.3->^3.6.1^3.5.3->^3.6.1Release Notes
nuxt/nuxt (@nuxt/kit)
v3.6.1Compare Source
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🩹 Fixes
typescriptdep (#21729)falseto disable spa loading template (#21739)pathfrom SPA payload (#21732)ssr: falseroute rule (#21763)#imports(#21796)📖 Documentation
defineNuxtRouteMiddlewaremigration (#21718)✅ Tests
❤️ Contributors
v3.6.0Compare Source
📣 Upcoming news
In the coming week you can expect two announcements:
nuxt/cliby @pi0 - a new, drop-in replacement fornuxifeaturing more extensibility and better DX. We are aiming to release this alongside Nuxt 3.7, but you would be very welcome to test and contribute tonuxi-ngbefore then!👀 Highlights
This minor release contains quite a lot, and we have big plans
If your site is served with
ssr: falseor you have disabled server-rendering on some of your pages, you might be particularly interested in the new built-in SPA loading indicator.You can now place an HTML file in
~/app/spa-loading-template.htmlwith some HTML you would like to use to render a loading screen that will be rendered until your app is hydrated on these pages.👉 By default an animated Nuxt icon is rendered. You can completely disable this indicator by setting
spaLoadingTemplate: falsein your nuxt configuration file.⚡️ Performance improvements
The first thing that happens when your app is hydrated is that your plugins run, and so we now perform build-time optimisations on your plugins, meaning they do not need to be normalised or reordered at runtime.
We also include your error component JS in your main entrypoint, meaning that if an error occurs when a user has no connectivity, you can still handle it with your
~/error.vue. (This also should decrease your total bundle size.)👉 Compared to Nuxt 3.5.3, the minimal client bundle has decreased by ~0.7kB. Let's keep this up!
🔥 Fully static server components
It has been possible to use server components on static pages, but until now they would increase the payload size of your application. That is no longer true. We now store rendered server components as separate files, which are preloaded before navigation.
👉 This does rely on the new, richer JSON payload format, so make sure you have not disabled this by setting
experimental.renderJsonPayloadsto false.🎨 Better style inlining
If you're monitoring your metrics closely and have not turned off
experimental.inlineSSRStyles, you should see more CSS inlined in your page, and a significantly external CSS file. We're now better at deduplicating global CSS, particularly added by libraries like tailwind or unocss.🎬 Animation controls
To give you more fine-grained control over your page/layout components, for example to create custom transitions with GSAP or other libraries, we now allow you to set
pageRefon<NuxtPage>andlayoutRefon<NuxtLayout. These will get passed through to the underlying DOM elements.✨ Automatic 'static' preset detection
Up to now, running
nuxt generateproduced the same output on every deployment provider, but with Nuxt 3.6 we now enable static provider presets automatically. That means if you are deploying a static build (produced withnuxt generate) to a supported provider (currently vercel and netlify with cloudflare and github pages coming soon) we'll prerender your pages with special support for that provider.This means we can configure any route rules (redirects/headers/etc) that do not require a server function. So you should get the best of both worlds when deploying a site that doesn't require runtime SSR. It also unblocks use of Nuxt Image on Vercel (with more potential for automatic provider integration coming soon).
💪 Increased type safety
We now have better support for server-specific
#importsand augmentations if you are using the new~/server/tsconfig.jsonwe shipped in Nuxt 3.5. So when importing from#importsin your server directory, you'll get IDE auto-completion for the right import locations in Nitro, and won't see Vue auto-imports likeuseFetchthat are unavailable within your server routes.You should now also have type support for runtime Nitro hooks.
Finally, we have removed more locations where objects had a default
anytype. This should improve type safety within Nuxt in a number of locations where unspecified types fell back to any:RuntimeConfigPageMetaNuxtApp['payload'](accessible now fromNuxtPayloadinterface)ModuleMetaYou can find out more about how to update your code if this affects you in the original PR.
⚗️ Nitro 2.5 built-in
This release ships with new Nitro 2.5, which has a whole list of exciting improvements that are worth checking out.
Of particular note is experimental support for streaming, which is also enabled by a couple of changes in Nuxt itself.
🛠️ New tools for module authors
This release brings a number of utilities for modules authors to easily add type templates and assert compatibility with a given version of another module.
In addition, this release will finally unlock a new
nuxt/module-buildermode that should improve type support for module authors. If you're a module author, you might consider following these migration steps to try it out in the coming days.✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
useCookiestate between tabs (#20970)renderResulttoapp:rendered(#18610)esbuild-loaderoptions (#21436)openoption innavigateTohelper (#21333)clearNuxtStatecomposable (#21409)addTypeTemplatehelper with auto-registration (#21331)statusfromuseAsyncData(#21045)NuxtPageref viapageRef(#19403)NuxtLayoutref vialayoutRef(#19465)ssr-errorevent (#21547)defineNuxtModule(#20763)useNuxtAppto window for convenience (#21636)🔥 Performance
🩹 Fixes
resolveIdworkaround and update vite-node (#21423)nitro.autoImportoption (#21485)dstnotsrc(#21501)navigateTo(#21500)window.location(#21521)<Title>(#21613):in rendered server components (for win) (#21645)baseUrlintsconfig.json(#21632)BroadcastChannel(#21653)@typescript-eslint/typescript-estree(#21664)res.end()calls with check if event is handled (#21665)redirecttype forNuxtPagetype (#21713)📖 Documentation
renderwhen definingrendering(#21490)addTypeTemplatetypos (#21520)nuxtwith bridge ifnitrois false (#21586)paralleloption on plugins (#21622)examples/from repository (#21538)@latestto install commands (#21702)🏡 Chore
vitestrenovate group (7695aca93)octokit/request-action(dd5955caf)webpack-dev-middlewareupdates on 2.x branch (7f7ae96d1)✅ Tests
🤖 CI
❤️ Contributors
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 becomes conflicted, 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.