chore(deps): update all non-major dependencies #76
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}
Codecov Report
@@ Coverage Diff @@
## main #76 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 68 68
Branches 7 7
=========================================
Hits 68 68 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
54dd3b0
to
c5599a7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
c5599a7
to
8ae46af
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8ae46af
to
ba827b6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ba827b6
to
6b27362
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
f9d466f
to
5d6c6e4
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
5d6c6e4
to
ac933eb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ac933eb
to
2bb3605
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.2.3->^3.3.17.29.1->7.29.3Release Notes
nuxt/nuxt
v3.3.1Compare Source
👀 Highlights
✨ Local module development DX
We've landed a raft of changes to enable local modules and improve DX. We now auto-scan your
~/modulesfolder and register top level files there as modules in your project (https://github.com/nuxt/nuxt/pull/19394). When these files are changed, we'll automatically restart the nuxt server.export default defineNuxtConfig({ modules: [ '@​nuxtjs/tailwindcss', - '~/modules/purge-comments' ] })We also now expose
nuxt/kitfor easy access to kit composables in your local project without having to install@nuxt/kit(https://github.com/nuxt/nuxt/pull/19422).♻️ Restarting Nuxt
You can add files to the
watcharray to automatically restart the server (https://github.com/nuxt/nuxt/pull/19530). This is likely to be particularly useful for module authors. You can also trigger a restart of the Nuxt server with the newrestarthook (https://github.com/nuxt/nuxt/pull/19084). We also landed a couple of fixes on restarting the Nuxt server which should improve your experience when developing.🔥 Performance improvements
We've increased static asset maxAge to 1yr as a matter of best practice (https://github.com/nuxt/nuxt/pull/19335), and support tree-shaking more of your build (https://github.com/nuxt/nuxt/pull/19508). We also now support preloading
<NuxtLink>s with a route in object-syntax (https://github.com/nuxt/nuxt/pull/19120).We also track how long it takes each module you use to perform its setup, and warn if it takes too long. You can see all these values by running your dev server with
DEBUG=1You can also opt-in to some of Nuxt's internal optimisations by configuring composables to be treeshaken in a particular environment (https://github.com/nuxt/nuxt/pull/19383), or to have magic keys automatically injected (https://github.com/nuxt/nuxt/pull/19490) - primarily useful for module authors.
🐛 Error handling
We now handle chunk errors by default (https://github.com/nuxt/nuxt/pull/19086), meaning if your site updates with a redeploy, we automatically handle reloading it on navigation. You can disable this and handle it yourself with the new
reloadNuxtAppcomposable. You can also setexperimental.restoreStateto preserve some of your app state across reloads.We also have a new experimental error handling component:
<NuxtClientFallback>(https://github.com/nuxt/framework/pull/8216) which can capture errors rendering on server, replace them with fallback content, and granularly trigger rerendering the part with an error on the client. This can be enabled withexperimental.clientFallback- feedback very welcome!⚡️ Head improvements
We've migrated to use
unheaddirectly (https://github.com/nuxt/nuxt/pull/19519) - and automatically tree-shake server-only head composables likeuseServerHeadfrom your client build (https://github.com/nuxt/nuxt/pull/19576), meaning you can have great SEO without needing to include meta tag logic that's relevant only for crawlers in your client build.There's also a new
useHeadSafecomposable that handles santising untrusted user input (https://github.com/nuxt/nuxt/pull/19548).🪵 Better logging in browser DevTools
Working with the Chrome DevTools team, we've landed a couple of features across the unjs + Nuxt ecosystem meaning we now have first-class support for hiding Nuxt internal stack traces from logs in your (Chromium-based, for now) browser (https://github.com/nuxt/nuxt/pull/19243). We also landed a couple of improvements with stacktraces involving Nuxt hooks (https://github.com/unjs/hookable/pull/69 and https://github.com/unjs/hookable/pull/68) implementing
console.createTask.💪 Type improvements
Types for server API routes are now more correct - with non-serialisable types stripped out of the return type (https://github.com/unjs/nitro/pull/1002).
We also now type more of
NuxtAppand correctly type unknown injections for greater type-safety (https://github.com/nuxt/nuxt/pull/19643).And if you were struggling with correct types when using
transform+defaultwith Nuxt data fetching composables, fear no more - we now infer the types correctly (https://github.com/nuxt/nuxt/pull/19487).⚗️ Nitro enhancements
This release comes with Nitro v2.3, which brings lots of improvements of its own. Check out the release for more info.
We now support
useAppConfigin nitro server routes (https://github.com/nuxt/nuxt/pull/19489) - a long-awaited change. NowuseAppConfigis consistently available throughout your app for non-runtime configuration from layers, modules, etc.We've also added a
nitro:build:public-assetshook to allow modifying assets output from nitro's prerender/build phase (https://github.com/nuxt/nuxt/pull/19638).🛠️ Build changes
As part of moving towards first-class support for PNP and pnpm support without
--shamefully-hoist, we've dropped support for some internal (deprecated) utilities using CJS resolve patterns (https://github.com/nuxt/nuxt/pull/19537, https://github.com/nuxt/nuxt/pull/19608). We also now resolve dependencies likenuxt,@nuxt/kitand more using ESM search-paths. We'll be keeping a close eye on this.We're also preparing the groundwork for support of new TypeScript Node16 module resolution (https://github.com/nuxt/nuxt/issues/19606), and as part of this have changed the format of our runtime output (using
.jsinstead of.mjsextensions, providingtypesfields for subpath exports, and more).🗺️ Custom config schema (advanced)
We've been testing out an experimental feature to allow modules and users to extend the Nuxt config schema (https://github.com/nuxt/nuxt/issues/15592), and we've now enabled this by default (https://github.com/nuxt/nuxt/pull/19172). We expect this will be particularly useful for module and layer/theme authors, and should result in some nicer DX for their users.
Changelog
compare changes
🚀 Enhancements
restarthook is called (#19084)versionsto runtime nuxtApp (#19064)node_modulesand buildDir tox_google_ignoreList(#19243)nuxt/kitsubpath for local use (#19422)~/modules(#19394)priorityto allow overriding (#19252)trailingSlashBehaviorindefineNuxtLink(#19458)logLevel(#19369)<NuxtClientFallback>component (#8216)watchoption and refactor dev server restarting (#19530)useHeadSafeand remove layer around head imports (#19548)nitro:build:public-assetshook (#19638)🔥 Performance
@vueuse/headdependency (#19519)🩹 Fixes
NuxtLink(#19379)import.metatypes (#19338)/fromsourcemapIgnoreListfor windows support (73ade185b)kit.*files to published package (#19430)transform(#19487)booleanfrom inline module definitions (#19621)payloadExtractionwarning only when unset (#18516)💅 Refactors
📖 Documentation
versionsand modules (#19448)routeRules(#19455)devServer.httpsexample (#19486)~/server/utilsdirectory in~/utilspage (#19500)addComponentjsdoc comment (#19503)--log-level(06b9233b1)🏡 Chore
@nuxt/test-utilspackage as external group (#19419)hasProtocoloptions format (#19555)✅ Tests
🤖 CI
❤️ Contributors
v3.3.0Compare Source
pnpm/pnpm
v7.29.3Compare Source
Patch Changes
node_modules/.pnpm/node_modulesdirectory through theNODE_PATHenv variable, then the command's ownnode_modulesdirectory #5176.extend-node-pathis set back totrueby default. It was set tofalsein v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extendingNODE_PATH. We have fixed the Jest issue with a different solution #6213.Our Gold Sponsors
Our Silver Sponsors
v7.29.2Compare Source
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.