chore(deps): update dependency nuxt to v3.14.1592 #824
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}
✅ Deploy Preview for tresjs-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
from
cde2113 to
9a1cdb7
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
3 times, most recently
from
ddd4cf7 to
73dc5f4
Compare
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
9 times, most recently
from
1b16354 to
0633478
Compare
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
9 times, most recently
from
30ea0fb to
979aac4
Compare
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
from
979aac4 to
882086f
Compare
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
3 times, most recently
from
0fc2f3e to
fec4f3e
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
from
fec4f3e to
46038ca
Compare
renovate
bot
force-pushed
the
renovate/nuxtjs-monorepo
branch
from
46038ca to
14a7971
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:
3.13.0->3.14.1592Release Notes
nuxt/nuxt (nuxt)
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)📖 Documentation
defineNuxtComponentinstead ofdefineComponent(#29011)useRequestFetchandevent.$fetch(#29099)useFetcherrors (#29253)ofetchheaders for interceptors (#29118).env.test(#29398)mockImplementation()call (#29669)$fetch(#29755)--envNameflag (#28909)📦 Build
beasties(1b5391182)🏡 Chore
unbuildupdate (71e0fb06f)jiti.import(7ece49f9b)✅ Tests
unctxtransform (d81196122)🤖 CI
❤️ Contributors
v3.13.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
propsDestructureby default (#28830)routehas enumerable keys (#28841)asyncData(#28842)ssr: false(#28834)injectAtEndto reduce circular auto-imports (#28822)buildDirfor unimport (#28899)<NuxtErrorBoundary>(#28901)modulesarray (#28922)filePath(#28925)runWithContextgeneric (#28926)inheritAttrs: falsefor fragment components (#28939)<script>blocks (4fd24381c)isNuxtMajorVersionexport (#29016)useError(#28996)💅 Refactors
vite:preloadErrorevent (#28862)📖 Documentation
useFetchparameter signature (#28993)🏡 Chore
noUncheckedSideEffectImports(#28903)pending triageto blank issues (#28923)htmlnano+ pin workflow deps (#28946)✅ Tests
routein template (#28967)🤖 CI
❤️ Contributors
v3.13.1Compare Source
👀 Highlights
Although this is a patch release, there are two features I'd love to draw your attention to.
useIdnow uses a built-in Vue composable for stable ids between server + client! https://github.com/nuxt/nuxt/pull/28285experimental.buildCachefeature now allows for quicker app rebuilds https://github.com/nuxt/nuxt/pull/28726As always, feedback is appreciated 🙏 ❤️
✅ 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
ServerPlaceholderfor ssr client components (#28563)🩹 Fixes
serverDirrelative to root (#28700)MiddlewareKey(#28676)NuxtLink(#28738)NuxtOptionsas well as config (#28747)CookieStoreevents (#28760)appConfigwith non-iterable objects (#28773)isNuxtErrortype inference (#28814)💅 Refactors
useId(#28285)📖 Documentation
queryreturned value fromuseRoute()(#28743)--frozen-lockfilewhen installing dependencies (#28794)🏡 Chore
tinyexecinternally (#28684)tinyglobbyinternally (#28686)✅ Tests
❤️ Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.