chore(deps): update all non-major dependencies#800
Merged
tobiasdiez merged 1 commit intomainfrom Dec 4, 2024
Merged
Conversation
✅ Deploy Preview for nuxt-storybook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
17 times, most recently
from
5e2ee8e to
92b40ee
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
10 times, most recently
from
577fd49 to
cc1f833
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
166e597 to
e99dc13
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
18 times, most recently
from
2db29d6 to
58c6117
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
1ae998a to
75839d0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
75839d0 to
87c2bc2
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
1.2.0->1.2.11.2.5->1.2.142.13.2->2.13.41.5.2->1.6.30.5.7->0.7.20.5.7->0.7.20.9.2->0.10.23.13.2->3.14.15923.13.2->3.14.15923.14.2->3.14.41.4.3->1.5.03.13.2->3.14.15922.1.1->2.2.16.12.1->6.12.20.5.5->0.8.01.47.2->1.49.01.0.36->1.1.022.7.4->22.10.15.1.4->5.2.14.0.1->4.1.12.1.2->2.1.811.11.0->11.20.09.11.1->9.16.02.1.2->2.4.11.7.1->1.7.33.13.2->3.14.15923.0.4->3.1.11.4.0->1.4.19.12.0->9.14.43.3.3->3.4.117.7.0->17.10.05.6.2->5.7.20.8.7->0.10.32.1.2->2.1.83.5.11->3.5.134.4.5->4.5.02.1.6->2.1.10Release Notes
nuxt/content (@nuxt/content)
v2.13.4Compare Source
compare changes
🏡 Chore
@nuxtjs/mdc(0c462d3f)❤️ Contributors
v2.13.3Compare Source
compare changes
🩹 Fixes
@nuxtjs/mdcutils via content module (#2775)charset=utf-8to headers of indexed mode (#2729)ssr: falsewith Content (#2776)defineNitroPluginfrom#imports(34f65172)draftkey as_draft(#2738)📖 Documentation
🏡 Chore
@nuxtjs/mdc(#2781)@nuxtjs/mdc(664ac088)❤️ Contributors
nuxt/devtools (@nuxt/devtools-kit)
v1.6.3Compare Source
Bug Fixes
vite-plugin-inspectversion (a399082)v1.6.2Compare Source
Bug Fixes
Features
vite-plugin-inspectfor both Vite 5 and 6 (#757) (cfcbc24)v1.6.1Compare Source
Bug Fixes
Features
v1.6.0Compare Source
Bug Fixes
1.5.2 (2024-10-02)
Bug Fixes
vite-plugin-vue-inspector(572a0d6)1.5.1 (2024-09-23)
Bug Fixes
nuxt/eslint (@nuxt/eslint)
v0.7.2Compare Source
🚀 Features
View changes on GitHub
v0.7.1Compare Source
No significant changes
View changes on GitHub
v0.7.0Compare Source
🚀 Features
features.formattersto format CSS and HTML - by @antfu in https://github.com/nuxt/eslint/issues/520 (f6d8b)View changes on GitHub
v0.6.2Compare Source
🚀 Features
🐞 Bug Fixes
eslint-config-flat-gitignoreto0.2.0to support ESLint v8, #507 - by @antfu in https://github.com/nuxt/eslint/issues/507 (b781e)View changes on GitHub
v0.6.1Compare Source
🚀 Features
vite-plugin-eslint2v5, close #516 - by @antfu in https://github.com/nuxt/eslint/issues/516 (a6b4e)View changes on GitHub
v0.6.0Compare Source
🚀 Features
nuxt-config-keys-orderrule - by @antfu in https://github.com/nuxt/eslint/issues/491 (b65a8)View changes on GitHub
nuxt/fonts (@nuxt/fonts)
v0.10.2Compare Source
compare changes
🩹 Fixes
✅ Tests
coverage.includepath (36e5e08)❤️ Contributors
v0.10.1Compare Source
compare changes
🩹 Fixes
module.d.mtsas type entrypoint (be6fafc)🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v0.10.0Compare Source
compare changes
🩹 Fixes
font:(#299)💅 Refactors
jiti.importto resolve custom providers (#308)unifontto handle providers (#315)📖 Documentation
🏡 Chore
pnpmto run release (dbbf438)✅ Tests
unifontto handle providers (#315)❤️ Contributors
nuxt/nuxt (@nuxt/kit)
v3.14.1592Compare Source
👉 Changelog
compare changes
🩹 Fixes
webpackbarwith support for rspack (#29823)dstto deduplicate templates when adding them (#29895)dstto invalidate modules (6cd3352de)changeevents (#29954)<NuxtWelcome>when building (#29956)💅 Refactors
📖 Documentation
🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v3.14.159Compare Source
We're leaning into the π theme - future patch releases of this minor version will just continue adding digits. (Sorry for any inconvenience! 😆)
👉 Changelog
compare changes
🩹 Fixes
module.json(#29793)mllyto resolve module paths to avoid cjs fallback (#29799)webpack-dev-middleware(#29806)📖 Documentation
🏡 Chore
❤️ Contributors
v3.14.0Compare Source
👀 Highlights
Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the
unjsside with preparations for Nitro v3!)⚡️ Faster starts powered by
jitiLoading the nuxt config file, as well as modules and other build-time code, is now powered by
jitiv2. You can see more about the release in the jiti v2 release notes, but one of the most important pieces is native node esm import (where possible), which should mean a faster start. ✨📂 Shared folder for code and types shared with client/server
You should never import Vue app code in your nitro code (or the other way around). But this has meant a friction point when it comes to sharing types or utilities that don't rely on the nitro/vue contexts.
For this, we have a new
shared/folder (#28682). You can't import Vue or nitro code into files in this folder, but it produces auto-imports you can consume throughout the rest of your app.If needed you can use the new
#sharedalias which points to this folder.The shared folder is alongside your
server/folder. (If you're usingcompatibilityVersion: 4, this means it's not inside yourapp/folder.)🦀
rspackbuilderWe're excited to announce a new first-class Nuxt builder for
rspack. It's still experimental but we've refactored the internal Nuxt virtual file system to useunpluginto make this possible.Let us know if you like it - and feel free to raise any issues you experience with it.
👉 To try it out, you can use this starter - or just install
@nuxt/rspack-builderand setbuilder: 'rspack'in your nuxt config file.✨ New composables
We have new
useResponseHeaderanduseRuntimeHookcomposables (#27131 and #29741).🔧 New module utilities
We now have a new
addServerTemplateutility (#29320) for adding virtual files for access inside nitro runtime routes.🚧 v4 changes
We've merged some changes which only take effect with
compatibilityVersion: 4, but which you can opt-into earlier.previously, if you had a component like
~/components/App/Header.vuethis would be visible in your devtools as<Header>. From v4 we ensure this is<AppHeader>, but it's opt-in to avoid breaking any manual<KeepAlive>you might have implemented. (#28745).Nuxt scans page metadata from your files, before calling
pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before callingpages:extend. Instead, we have a newpages:resolvedhook, which is called afterpages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by settingexperimental.scanPageMetatoafter-resolve, as it solves a number of bugs.🗺️ Roadmap to v3.15
They didn't quite make it in time for v3.14 but for the next minor release you can expect (among other things):
✅ 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
jiti(#29073)addServerTemplateutility (#29320)useResponseHeadercomposable (#27131)rspackbuilder (#29142)pages:resolvedhook + scan meta post extend (#28861)definePageMeta(#29586)shared/folder and#sharedalias (#28682)useRuntimeHookcomposable (#29741)🔥 Performance
useNuxtApp(#29514)🩹 Fixes
InjectionTypetemplate conditional (#29023)webpackmemfs (#29027)DOMExceptionas fetch abort exception (#29058)devServer.https(#29049)buildDirin dev mode (#29068)node_modules/from parent urls (5bd42c893)crossoriginattribute for stylesheets (#29138)routeRulesto hint pages to prerender (#29172)link:prefetch(#29321)ConfigLayertype fromc12(#29370)typedPages(#29352)configFileas required in layer type (3bbcd7d21)createIsExternal(686be8168)propsvalue indefinePageMeta(#29683)nitropack/typesto ensure api routes are typed (54096875e)💅 Refactors
addBuildPlugininternally ([#29157](https://redConfiguration
📅 Schedule: Branch creation - "* * * * 0,6" (UTC), 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 was generated by Mend Renovate. View the repository job log.