-
Couldn't load subscription status.
- Fork 183
chore(deps): update all non-major dependencies #385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
04371cd to
782c111
Compare
782c111 to
82a7412
Compare
82a7412 to
66e1aac
Compare
66e1aac to
72de552
Compare
72de552 to
a448315
Compare
a448315 to
226e56a
Compare
226e56a to
9043490
Compare
9043490 to
e2f3465
Compare
e2f3465 to
fe8a192
Compare
35984d2 to
c2bfaae
Compare
c2bfaae to
00d5953
Compare
00d5953 to
32bdbb6
Compare
32bdbb6 to
aac12d5
Compare
aac12d5 to
d4ffd63
Compare
d4ffd63 to
adaab1f
Compare
adaab1f to
80ccc58
Compare
80ccc58 to
2ba9a8b
Compare
2ba9a8b to
6e9907f
Compare
6e9907f to
7dbf232
Compare
7dbf232 to
8c05337
Compare
8c05337 to
d7e5b0b
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:
^0.10.15->^0.10.16^3.6.5->^3.7.3Release Notes
cloydlau/json-editor-vue (json-editor-vue)
v0.10.16Compare Source
🐞 Bug Fixes
View changes on GitHub
nuxt/nuxt (nuxt)
v3.7.3Compare Source
👉 Changelog
compare changes
🩹 Fixes
#components(#23188)💅 Refactors
📖 Documentation
❤️ Contributors
v3.7.2Compare Source
✅ Upgrading
As usual, our recommendation for upgrading is to run:
👉 Changelog
compare changes
🩹 Fixes
joinURLwith remote sources on NuxtIsland (#23093)data-vattrs from server component props (#23095)useFetchauto key (#23086)cssCodeSplit(#23049)spaLoadingTemplateif file exists (#23048)tsconfig.jsondefaults (#23121)0(#23127)📖 Documentation
nameparam toPageMetainterface description (#23107)experimental.componentIslands(#23138)nuxi initcommand (#23155)🏡 Chore
🤖 CI
❤️ Contributors
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
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.
👻 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.