chore(deps): update all non-major dependencies #1356
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
force-pushed
the
renovate/all-minor-patch
branch
from
14a457c
to
9781579
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #1356 +/- ##
=======================================
Coverage 99.67% 99.67%
=======================================
Files 88 88
Lines 5882 5882
Branches 515 515
=======================================
Hits 5863 5863
Misses 17 17
Partials 2 2 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
9781579
to
026d773
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
26 times, most recently
from
349369e
to
8ca7329
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
24 times, most recently
from
d0fd8db
to
0b47310
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
4f8e63e
to
0d94bae
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
0d94bae
to
300cf50
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.2->^3.7.0^12.0.0->^12.1.0^0.1.2->^0.1.3^8.2.4->^8.2.6^18.16.16->^18.17.12^2.7.2->^2.7.3^9.0.1->^9.0.3^0.31.2->^0.34.3^1.7.1->^1.7.2^2.3.2->^2.4.1^8.0.0->^8.0.1^3.30.2->^3.32.1^8.41.0->^8.48.0^10.0.3->^10.11.2^1.2.0->^1.3.018.16.0->18.17.1^2.1.3->^2.1.6^2.1.3->^2.1.6^3.0.0->^3.0.3^8.2.4->^8.2.6^3.3.3->^3.4.3^7.0.0->^7.2.0^4.3.9->^4.4.9^0.14.5->^0.14.6Release Notes
nuxt/nuxt (@nuxt/schema)
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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.