-
Notifications
You must be signed in to change notification settings - Fork 41
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
chore(deps): update dependencies #68
Merged
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 6, 2024 02:22
e294eb9
to
b0f9213
Compare
renovate
bot
changed the title
chore(deps): update nuxt core to v3.9.0
chore(deps): update nuxt core to v3.9.1
Jan 6, 2024
renovate
bot
changed the title
chore(deps): update nuxt core to v3.9.1
chore(deps): update nuxt core
Jan 9, 2024
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 9, 2024 17:46
b0f9213
to
03a8bb9
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 16, 2024 19:20
03a8bb9
to
1ad5c41
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 17, 2024 17:02
1ad5c41
to
ec91cf9
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 18, 2024 14:50
ec91cf9
to
f859b3c
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 18, 2024 17:25
f859b3c
to
81e4974
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 30, 2024 13:30
81e4974
to
8007dd7
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 30, 2024 19:00
8007dd7
to
c734713
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
January 31, 2024 17:38
c734713
to
76e45eb
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
February 5, 2024 18:02
76e45eb
to
0b0d18b
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
February 14, 2024 15:38
0b0d18b
to
3a4c805
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
February 22, 2024 13:35
3a4c805
to
8ca303e
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
February 22, 2024 16:14
8ca303e
to
f36ec89
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
February 23, 2024 20:01
f36ec89
to
f72f4f7
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
March 5, 2024 13:50
f72f4f7
to
d6a7df2
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
March 12, 2024 17:06
d6a7df2
to
cac6dfc
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
March 17, 2024 10:18
cac6dfc
to
926d17c
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
March 19, 2024 02:20
926d17c
to
ebd2041
Compare
danielroe
changed the title
chore(deps): update nuxt core
chore(deps): update dependencies
Mar 21, 2024
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
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.8.2
->3.11.1
^2.11.1
->^2.14.2
^3.8.2
->^3.11.1
Release Notes
nuxt/nuxt (@nuxt/kit)
v3.11.1
Compare 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
🩹 Fixes
ofetch
intypescript.hoist
defaults (#26316)tsx
parser (#26314)finish
types and add to docs (0d9c63b82)undefined
name when resolving trailing slash (#26358)📖 Documentation
usePreviewMode
(#26303)useId
must be used with single root element (401370b3a)<DevOnly>
component in api section (#26029)@nuxt/schema
should be used by module authors (#26190)routeNameSplitter
example in migration docs (#25838)🏡 Chore
🤖 CI
❤️ Contributors
v3.11.0
Compare Source
v3.10.3
Compare 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 vue and unjs ecosystems.
👉 Changelog
compare changes
🩹 Fixes
dedupe
option inuseFetch
(#25815)css
files with?inline
query (#25822)external
tonavigate
in custom<NuxtLink>
(#25887)@__PURE__
(#25842)setTimeout
before scrolling when navigating (#25817)head
indefineNuxtComponent
(#25410)undefined
paths inresolveTrailingSlashBehavior
(ba6a4132b)to.name
to be undefined rather than deleting entirely (4ca1ab7cf)📖 Documentation
.ts
extension when adding compiled files (#25855)callout
to new components (#25897)🏡 Chore
nuxt.config
to enable pages for docs typecheck (72a2e23cc)🤖 CI
❤️ Contributors
v3.10.2
Compare 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 vue and unjs ecosystems.
👉 Changelog
compare changes
🩹 Fixes
refreshCookie
(#25635).pcss
extension as a CSS extension (#25673)<ClientOnly>
(#25714)baseURL
on serveruseRequestURL
(#25765)rootDir
, notprocess.cwd
, formodulesDir
(#25766)useId
if attrs were not rendered (#25770)📖 Documentation
Fix typo in
useAsyncData
docs (#25644)Add quotes to clarify what site title is in example (#25669)
Enable twoslash for some code snippets (#25679)
Add prepend option docs for
addComponentsDir
(#25683)Extend auto-scanned layer directories (#25720)
Improve wording in seo docs (#25692)
Add how to debug nuxt with node inspector (#25731)
Add missing export defaults for nuxt config (#25774)
Add import statement for mountSuspended (#25783)
Pass
event
touseRuntimeConfig
(#25788)🏡 Chore
❤️ Contributors
v3.10.1
Compare 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 vue and unjs ecosystems.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
refresh
functions (#25568)useId
type signature (#25614)$
from generated id inuseId
(#25615)rel
for same-site external links (#25600)inheritAttrs: false
when usinguseId
(#25616)💅 Refactors
NuxtLink
types (#25599)📖 Documentation
<NuxtLink>
defaults in nuxt config (#25610)🏡 Chore
pathe
in internal tests (e33cec958)nuxt
->nuxtApp
internally for consistency (c5d5932f5)🤖 CI
❤️ Contributors
v3.10.0
Compare Source
👀 Highlights
v3.10 comes quite close on the heels of v3.9, but it's packed with features and fixes. Here are a few highlights.
✨ Experimental shared
asyncData
when prerenderingWhen prerendering routes, we can end up refetching the same data over and over again. In Nuxt 2 it was possible to create a 'payload' which could be fetched once and then accessed in every page (and this is of course possible to do manually in Nuxt 3 - see this article).
With #24894, we are now able to do this automatically for you when prerendering. Your
useAsyncData
anduseFetch
calls will be deduplicated and cached between renders of your site.👉 See full documentation.
🆔 SSR-safe accessible unique ID creation
We now ship a
useId
composable for generating SSR-safe unique IDs (#23368). This allows creating more accessible interfaces in your app. For example:✍️ Extending
app/router.options
It's now possible for module authors to inject their own
router.options
files (#24922). The newpages:routerOptions
hook allows module authors to do things like add customscrollBehavior
or add runtime augmenting of routes.👉 See full documentation.
Client-side Node.js support
We now support (experimentally) polyfilling key Node.js built-ins (#25028), just as we already do via Nitro on the server when deploying to non-Node environments.
That means that, within your client-side code, you can import directly from Node built-ins (
node:
and node imports are supported). However, nothing is globally injected for you, to avoid increasing your bundle size unnecessarily. You can either import them where needed.Or provide your own polyfill, for example, inside a Nuxt plugin.
This should make life easier for users who are working with libraries without proper browser support. However, because of the risk in increasing your bundle unnecessarily, we would strongly urge users to choose other alternatives if at all possible.
🍪 Better cookie reactivity
We now allow you to opt-in to using the CookieStore. If browser support is present, this will then be used instead of a BroadcastChannel to update
useCookie
values reactively when the cookies are updated (#25198).This also comes paired with a new composable,
refreshCookie
which allows manually refreshing cookie values, such as after performing a request. See full documentation.🏥 Detecting anti-patterns
In this release, we've also shipped a range of features to detect potential bugs and performance problems.
setInterval
is used on server (#25259).<NuxtPage />
but have thevue-router
integration enabled (#25490). (<RouterView />
should not be used on its own.)🧂 Granular view transitions support
It's now possible to control view transitions support on a per-page basis, using
definePageMeta
(#25264).You need to have experimental view transitions support enabled first:
And you can opt in/out granularly:
Finally, Nuxt will not apply View Transitions if the user's browser matches
prefers-reduced-motion: reduce
(#22292). You can setviewTransition: 'always'
; it will then be up to you to respect the user's preference.🏗️ Build-time route metadata
It's now possible to access routing metadata defined in
definePageMeta
at build-time, allowing modules and hooks to modify and change these values (#25210).Please, experiment with this and let us know how it works for you. We hope to improve performance and enable this by default in a future release so modules like
@nuxtjs/i18n
and others can provide a deeper integration with routing options set indefinePageMeta
.📦 Bundler module resolution
With #24837, we are now opting in to the TypeScript
bundler
resolution which should more closely resemble the actual way that we resolve subpath imports for modules in Nuxt projects.'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their
package.json
.As part of this, we opened 85 PRs across the ecosystem to test switching the default, and identified and fixed some issues.
If you need to switch off this behaviour, you can do so. However, please consider raising an issue (feel free to tag me in it) in the library or module's repo so it can be resolved at 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
🚀 Enhancements
tryUseNuxtApp
composable (#25031)bundler
module resolution (#24837)pages:routerOptions
hook (#24922)setInterval
is used on server (#25259)refreshCookie
+ experimental CookieStore support (#25198)useId
composable (#23368)🔥 Performance
endsWith
when checking for whitespace (#24746)🩹 Fixes
prefers-reduced-motion
(#22292)fallback
in island response (#25296)defineModel
option as it is now stable (#25306)hidden
sourcemap values to vite (#25329)dedupe
(#25334)instance.attrs
in client-only components (#25381)callOnce
callbacks (#25431)nuxt-client
within template code (#25464)dependsOn
(#25409)NuxtError
(#25398)vue-router
warning with routeRule redirect (#25391)useRequestEvent
(#25480)useRuntimeConfig
signatures (#25440)pages:routerOptions
hook (#25509)💅 Refactors
currentRoute
non-ref warning (#25337)📖 Documentation
@since
annotations to exported composables (#25086)useAsyncData
explanation (#25392)error.vue
(#25320)error.vue
(#25396).cjs
extension forecosystem.config
(#25459)routeRules
example of swr/isr (#25436)sharedPrerenderData
(b0f50bec1)pages:routerOptions
(46b533671)🏡 Chore
NuxtPage
is not used when pages enabled (#25490)✅ Tests
data-island-uid
replacement (#25346)🤖 CI
$fetch
(a1fb399eb)❤️ Contributors
v3.9.3
Compare 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 vue and unjs ecosystems.
👉 Changelog
compare changes
🩹 Fixes
data-island-uid
for island children (#25245)📖 Documentation
✅ Tests
❤️ Contributors
v3.9.2
Compare 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 vue and unjs ecosystems.
👉 Changelog
compare changes
🔥 Performance
Object.fromEntries
(#24953)🩹 Fixes
options
inaddTemplate
(#25109)pages/
files inen-US
locale (#25195)nextTick
(#25197)💅 Refactors
data-island-component
(#25232)📖 Documentation
<NuxtPage>
rather than<RouterView>
(#25106)@nuxt/bridge-edge
(3f09ddc31)--log-level
description (#25211)immediate: false
in the appropriate example (#25224).global.vue
filename for global components (#25144)lagon
from deployment providers (#24955)definePageMeta
(#25073)addDevServerHandler
API (#25233)nuxi
for bridge (637f5622d)🏡 Chore
v3
branch sandbox in issue template (#25174)❤️ Contributors
v3.9.1
Compare 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 vue and unjs ecosystems.
👉 Changelog
compare changes
🔥 Performance
useRequestHeaders
(#24853)startsWith
to array access (#24744)🩹 Fixes
NuxtErrorBoundary
withssr: false
(#24896)any
in inferred injections (#25010)<ClientOnly>
(#25009)currentRoute
inRef
(#25026)💅 Refactors
nuxt-config-schema
(#25067)📖 Documentation
features
/future
docs (f5676fba5)vue-router
docs link (#24948)readValidatedBody
andgetValidatedQuery
(#24990)getValidatedRouterParams
(#25057)🏡 Chore
✅ Tests
❤️ Contributors
v3.9.0
Compare Source
👀 Highlights
A very merry Christmas to you and yours from all Nuxters involved in this release! 🎁🎄
We have lots of features packed into v3.9.0 and can't wait for you to try them out.
⚡️ Vite 5
This release comes with Vite 5 and Rollup 4 support. Module authors may need to check to ensure that any vite plugins you're creating are compatible with these latest releases.
This comes with a whole host of great improvements and bug fixes - check out the Vite changelog for more info.
✨ Vue 3.4 ready
This release is tested with the latest Vue 3.4 release candidate, and has the necessary configuration to take advantage of new features in Vue 3.4, including debugging hydration errors in production (just set
debug: true
) in your Nuxt config.👉 To take advantage, just update your
vue
version once v3.4 is released, or try out the release candidate today:🏝️ Interactive Server Components
This is a highly-experimental update, but it's now possible to play around with interactive components within Nuxt server components. You'll need to enable this new feature additionally to component islands:
Now, within a server component, you can specify components to hydrate by using the
nuxt-client
directive:We're pretty excited about this one - so do let us know how you're using it! 🙏
🔥 Automatic Server Optimisations
We now use Vite's new AST-aware 'define' to perform more accurate replacements on server-side code, meaning code like this will no longer throw an error:
This hasn't been possible until now because we haven't wanted to run the risk of accidentally replacing normal words like
document
within non-JS parts of your apps. But Vite's newdefine
functionality is powered byesbuild
and is syntax-aware, so we feel confident in enabling this functionality. Nevertheless, you can opt out if you need to:🚦 Granular Loading API
We now have a new hook-based system for
<NuxtLoadingIndicator>
, including auseLoadingIndicator
composable that lets you control/stop/start the loading state. You can also hook intopage:loading:start
andpage:loading:end
if you prefer.You can read more in the docs and in the original PR (#24010).
🏁 Run single events in
callOnce
Sometimes you only want to run code once, no matter how many times you load a page - and you don't want to run it again on the client if it ran on the server.
For this, we have a new utility:
callOnce
(#24787).Note that this utility is context-aware so it must be called in component setup function or Nuxt plugin, as with other Nuxt composables.
Read more in the docs.
🚨 Error Types
For a while now, errors returned by
useAsyncData
anduseFetch
have been typed pretty generically asError
. We've significantly improved the type possibilities for them to make them more accurate in terms of what you'll actually receive. (We normalise errors with theh3
createError
utility under the hood, so they can be serialised from server to client, for example.)We've tried to implement the type change in a backwards compatible way, but you might notice that you need to update the generic if you're manually configuring the generics for these composables. See (#24396) for more information, and do let us know if you experience any issues.
🔥 Schema Performance
We've taken some time in this release to make some minor performance improvements, so you should notice some things are a bit faster. This is an ongoing project and we have ideas for improving initial load time of the Nuxt dev server.
✅ 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
<NuxtLayout>
(#24116)addComponentsDir
(#24309)useCookie
(#24503)error.data
when throwing 404 errors (#24674)/module
or/nuxt
module subpath if it exists (#24707)refresh
on islands and server components (#24261)dedupe
option for data fetching composables (#24564)undefined
on server (#24711)addServerScanDir
composable (#24001)setup
withindefineComponent
options (#24515)useRequestHeader
utility (#24781)callOnce
util to allow running code only once (#24787)NuxtIsland
(#22649)bundler
module resolution (#22821)toArray
util (#24857)🔥 Performance
resolve
operation (#24736)join
operation (#24717)get
operations (#24734)useRuntimeConfig
call (#24843)JSON.stringify
operation (#24848)🩹 Fixes
import.d.ts
(#24413)reactivityTransform
(vue 3.4) (#24477)<DevOnly>
(#24511)isBuiltin
polyfill for greater node support (#24512)<NuxtLayout>
usage in islands (#24529)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 is behind base branch, 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.