chore(deps): update devdependency nuxt to v3 - autoclosed #90
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}
|
Deployment failed with the following error: |
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
8f8a049
to
c8a6289
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
c8a6289
to
1c4d66a
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
1c4d66a
to
effe862
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
effe862
to
ad3193b
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
28cdaa5
to
f871dc5
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
f871dc5
to
1e5998a
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
23fb43a
to
a079cdd
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
a079cdd
to
51b0aac
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
12af4bf
to
2eb9e87
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
2eb9e87
to
947005a
Compare
renovate
bot
changed the title
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:
^2.14.3->^3.6.5Release Notes
nuxt/nuxt (nuxt)
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 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
v3.5.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
--no-clearconfig through to vite (#21262)vue-loaderoptions type (#21363)typeCheck(#21064)std-envin runtime code (#21372)lodash.templatefromlodash-es(#20892)📖 Documentation
index.vueto page routing example (#21240)$fetchand fetch composables (#21228)envproperty to matchruntimeConfig(#21265)🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v3.5.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
.testand hoist regexps where possible (#21011)🩹 Fixes
@defaultjsdoc tag (#21010)pages/integration (397c54c9d)<DevOnly>with webpack (#21013)refreshNuxtData(#21008)abortNavigation(#21047)Set-Cookieheader if value is null (#21072)📖 Documentation
render:islandhook (#21065)🏡 Chore
✅ Tests
❤️ Contributors
v3.5.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
/route (#20894)useFetchmethod when generic is passed (#20797)refreshwhen hydrating when data is present (#20916)defaulttype for initial value for composables (#20968)resolvePathto handle edge cases for modules (#20975)📖 Documentation
pnpm testcommand to run whole test suite (4907660ff)experimental.renderJsonPayloads(891ba880e)useAsyncDataanduseFetchtypes (#20935)useState(#20249)pages/docs (#20976)🏡 Chore
🤖 CI
❤️ Contributors
v3.5.0Compare Source
👀 Highlights
⚡️ Vue 3.3 released!
Vue 3.3 has been released, with lots of exciting features, particularly around type support. This also brings a significant improvement to data fetching when navigating between nested pages (https://github.com/nuxt/nuxt/pull/20777), thanks to @antfu and @baiwusanyu-c.
defineOptionsmacroRead the full release announcement for more details.
🙌 Nitropack v2.4
We've been working on lots of improvements to Nitro and these have landed already in Nitro v2.4 - you may already have this upgrade, which contains a lot of bug fixes, updates to the module worker format for Cloudflare, Vercel KV support and more.
One note: if you're deploying to Vercel or Netlify and want to benefit from incremental static regeneration, you should now update your route rules:
routeRules: { -- '/blog/**': { swr: 3000 }, ++ '/blog/**': { isr: 3000 }, }Read the full release notes.
💖 New defaults
Rich JSON payload serialisation is now enabled by default (https://github.com/nuxt/nuxt/pull/19205, https://github.com/nuxt/nuxt/pull/20770). This is both faster and allows serialising complex objects in the payload passed from the Nuxt server to client (and also when extracting payload data for prerendered sites).
This now means that various rich JS types are supported out-of-the-box: regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like
ref,reactive,shallowRefandshallowReactive.You can find an example in our test suite.
This is all possible due to Rich-Harris/devalue#58. For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original.
You can even register your own custom types with a new object-syntax Nuxt plugin:
You can read more about how this works here.
🛝 Interactive server components
This feature should be considered highly experimental, but thanks to some great work from @huang-julien we now support interactive content within server components via slots (https://github.com/nuxt/nuxt/pull/20284).
You can follow the server component roadmap at https://github.com/nuxt/nuxt/issues/19772.
⏰ Environment config
You can now configure fully typed, per-environment overrides in your
nuxt.config:If you're authoring layers, you can also use the
$metakey to provide metadata that you or the consumers of your layer might use.Read more: https://github.com/nuxt/nuxt/pull/20329.
💪 Fully typed pages
You can benefit from fully typed routing within your Nuxt app via this experimental integration with https://github.com/posva/unplugin-vue-router - thanks to some great work from @posva! Out of the box, this will enable typed usage of
navigateTo,<NuxtLink>,router.push()and more. You can even get typed params within a page by usingconst route = useRoute('route-name').🔎 'Bundler' module resolution
We now have full support within Nuxt for the
bundlerstrategy of module resolution. We would recommend adopting this if possible. It has type support for subpath exports, for example, but more exactly matches the behaviour of build tools like Vite and Nuxt thanNode16resolution.This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like
mylib/paththat is mapped tomylib/dist/path.mjsthen the types for this can be pulled in frommylib/dist/path.d.tsrather than requiring the library author to createmylib/path.d.ts.⚗️ Separate server types
We plan to improve clarity within your IDE between the 'nitro' and 'vue' part of your app, and we've shipped the first part of this via a separate generated
tsconfig.jsonfor your~/serverdirectory (https://github.com/nuxt/nuxt/pull/20559). You can use by adding an additional~/server/tsconfig.jsonwith the following content:{ "extends": "../.nuxt/tsconfig.server.json" }Although right now these values won't be respected when type checking, you should get better type hints in your IDE.
💀 Deprecations
Although we have not typed or documented the
build.extendhook from Nuxt 2, we have been calling it within the webpack builder. We are now explicitly deprecating this and will remove it in a future minor version.✅ 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
prependoption toaddImportsDir(#20307)vite:configResolvedhook (#20411)webpack:configResolvedhook (#20412)addVitePluginandaddWebpackPlugin(#20525)nuxi analyzefrom cli (#20387)nuxtApp.runWithContext(#20608)typedPagesoption (#20367)runWithContextwithincallWithNuxt(#20775)useRequestURLhelper (#20765)<DevOnly>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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.