fix(deps): update nuxtjs monorepo #16
Open
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.1.1->3.7.13.1.1->3.7.12.15.8->2.17.13.1.1->3.7.1Release Notes
nuxt/nuxt (@nuxt/kit)
v3.7.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
🔥 Performance
🩹 Fixes
ssr: false(#22869)prioritywhen registering components dirs (#22882)addLayout(#22902)true(#22905)write: falsefor type templates (#22972)shouldExternalize(#22991)destrin more places overJSON.parse(#22997)📖 Documentation
<NuxtPage>(#22912)pageKey(#22920)envobject for nuxt plugins (#22963)NuxtLayout(#22989)🏡 Chore
nuxi-edgerather thannuxi-ng(9610cf03d)🤖 CI
GITHUB_REF_NAMEto get branch for release (d49ea58de)❤️ Contributors
v3.7.0Compare Source
👀 Highlights
🐣 A New CLI
We've refactored
nuxiusing unjs/citty and this marks the first Nuxt release that depends on the new version, safely in its own repository. We have grand plans for this - check out some of the features + roadmap discussions in nuxt/cli and please feel free to contribute!Nuxi is now decoupled from the main
nuxtversion - we plan to iterate and release nuxi more quickly in future so you can expect new things coming soon!🕸️ Native Web Streams and
ResponseWith improvements in unjs/h3 and unjs/nitro, it's now possible to directly return a
Responseobject from server routes, meaning it's also possible to return and handle streams natively in Nuxt.👉 Check out the full detail in the unjs/h3 and unjs/nitro release notes.
🔥 HTML Rendering Optimisations
This release comes with a couple of improvements in rendering HTML responses from the server. We now determine whether to preload/prefetch resources at build time (so you can customise this in the
build:manifesthook). We also now manage rendering the HTML for them directly inunhead(#22179), which means you can configure the order for<link>,<meta>,<script>,<style>, and more. And - in our preliminary testing - it's even faster!It's possible to opt-in to upcoming head improvements with the
experimental.headNextflag. This currently includes a new ordering algorithm based on capo.js (#22431) and allows enabling future optimisations as they are released inunhead:We'd love your thoughts - you can respond with any issues/feedback in this discussion.
🛠️ Build Environment Shortcuts
In your Nuxt config you can now use
$clientand$servershortcuts to easily define configuration that is specific to just the Vite client/server (#22302) or webpack client/server (#22304) builds. This previously was only possible with thevite:extendConfigandwebpack:confighooks.For example:
⚡️ Vite 4.4
We've chosen to unpin Vite from minor versions, meaning whenever Vite releases a new feature version you can opt-in straight away. Vite 4.4 brings a lot of exciting things, including experimental Lightning CSS support - and much more!
👉 Check out the Vite release notes for more.
💪 TypeScript Updates
We now use purely relative paths in the generated
tsconfig.jsoninstead of setting abaseUrl. This means better support for dev environments like docker images where the absolute path may not match your IDE (#22410).We also set a couple of additional compiler flag defaults to match Vite/TS recommendations (#22468).
Plus, you should now get type hinted access to layouts in
setPageLayoutand also in<NuxtLayout name>(#22363).🦄 Async Context support
If you've ever got an issue with 'Nuxt context unavailable' this might be one for you. We now support native async context for Bun and Node under an experimental flag, in both Nuxt and Nitro (#20918).
This enables using Nuxt composables on the server without needing to ensure they are being called directly in a setup function. It also allows the same in Nitro, with a new
useEvent()utility that is usable in server routes.To try it out, you can enable
experimental.asyncContext:👓 Watcher Updates
We've fixed a couple of issues with watchers, meaning that you should need to restart your server less often - and you should see a significant performance increase if you are using layers.
⚗️ Nitro 2.6
There lots more exciting features coming directly from Nitro 2.6, including smaller, lighter servers and new persistent data storage in a
.datadirectory.👉 Read more in the full release article.
✅ 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
$clientand$servervite env overrides (#22302)$clientand$serveroverrides (#22304)scrollToToppage meta (#21741)app:templatesGeneratedhook (#21935)unhead(#22179)@nuxt/webpack-builderwhen needed (#21747)writeTypesutility (#22385)setPageLayout/<NuxtLayout>(#22362)import.meta.*build flags (#22428)node_modules(#22478)webpack/nitro/postcssconfig (#22521)global: 'sync'components (#22558)app.rootIdoptional (#22528)experimental.headNextunhead integration (#22620)bunpackage manager (#22673)routeRulesdefined within pages (#20391)hiddensourcemaps (#22787)nuxt/cli(#22799)./schema/config.schema.jsonsubpath (#22813)🔥 Performance
nuxt/config(#22391)capo.jshead tag order (#22431).toLowerCase()(#22743)🩹 Fixes
prerender:routeshook (#22247)scrollBehaviorType(#22264)asyncDatageneric + default (#22258)createClientOnlyrender function to ctx (#22289)build.extend(#22305)validatereturn typing to be either error or boolean (#22323)hasNuxtModule(#22316)builder:watch(#22333)useFetchhash (#22378)watchpaths against all layersrcDirs (#22307)nameis an optional prop for<NuxtLayout>(0d9a0b753)useFetch(#22418)baseUrland use relative paths in tsconfig (#22410)injectHeadusage (#22447)useCookie(#22474)internal:nuxtnamespace (9b0d371b0)normalizecall (14bf2b02f)webpackoptions should be optional (#22524)app.config.tsfiles (#22494)hookableto externals list (4552d39c4)app.{rootId ([rootTag}(#22543)](nuxt/nuxt@rootTag}\` (#22543)))import.metabuild vars indefineas well (#22576)page:finish(#22566)distDirafter first build (#22614)''key for root scope in variable collector (#22679)excludepaths to nitrotsconfig.server.json(#22768)asyncDatawhenimmediateis disabled (#20980)spaLoadingTemplatetofalse(#22798)unctxwhere possible (#22811)💅 Refactors
nuxi-ngfor edge releases (#22413)useNitroAppfrom subpath (#22785)📖 Documentation
#componentsimport for dynamic component (#22231).envsection (#22369)NuxtIsland(#22434)]in code-block filenames (#22389)scrollToTop(#22503)statustype foruseAsyncData(#22511)useSeoMetaparameters (#22513)pick(#22531)ReadMorecomponents (#22541)addServerHandlerexample to modules author guide (#22603)server: falsedoesn't await on initial load (#22619)import.meta.*update until v3.7 release (98c17e5d4)NuxtIslandin server only components docs (#22685)useFetchdocs (#22755)useAsyncData(#22760)📦 Build
nuxi(df2bc8a72)🏡 Chore
.eslintignorefile with 'ignorePatterns' (#22547)h3-nightlyon edge releases (#22593)✅ Tests
networkidledependency (#22596)🤖 CI
❤️ Contributors
v3.6.5Compare Source
v3.6.4 release notes
✅ 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
distfrom the default ignore list (#22227)❤️ Contributors
v3.6.4Compare 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
🔥 Performance
buildDirandnode_modules(#22214)🩹 Fixes
toLowerCasefor possiblemoduleResolution(#22160)baseURLto island fetch requests (#22009)--inspectin dev mode (#22205)📖 Documentation
❤️ Contributors
v3.6.3Compare 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
🔥 Performance
🩹 Fixes
unctxoptions (4e32e70bb)isExternal(#21966)experimentaloption (0643d4315)💅 Refactors
bundlermodule resolution flag (#22142)📖 Documentation
/(#22118)🏡 Chore
❤️ Contributors
v3.6.2Compare 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
🔥 Performance
🩹 Fixes
@nuxt/ui-templatesfrommodulesDir(#21836)nuxi generate(#21860)tsconfig.jsonscope (#21917)typedPages(#21659)node_modulesto tsconfig include (#21929)$fetch.rawin dev client mode for islands (#21904)vite.publicDir(#21847)📖 Documentation
spaLoadingTemplatelink (#21845)<NuxtLoadingIndicator>(#21952)🏡 Chore
✅ Tests
nuxt-vitestand composable unit tests (#21884)❤️ Contributors
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 bConfiguration
📅 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.
👻 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.