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 dependency nuxt to ^3.11.2 #2588
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
Deploying nuxt-content with Cloudflare Pages
|
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
March 17, 2024 09:47
292e221
to
bb8df8a
Compare
renovate
bot
changed the title
chore(deps): update devdependency @nuxt/test-utils to v3.12.0
chore(deps): update nuxt framework
Mar 17, 2024
renovate
bot
force-pushed
the
renovate/nuxt
branch
3 times, most recently
from
March 21, 2024 10:34
0d7adcc
to
8927d54
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
April 4, 2024 17:21
8927d54
to
47a62b2
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
2 times, most recently
from
April 18, 2024 14:39
5baab0b
to
07d163c
Compare
renovate
bot
changed the title
chore(deps): update nuxt framework
chore(deps): update dependency nuxt to ^3.11.2
Apr 18, 2024
renovate
bot
force-pushed
the
renovate/nuxt
branch
2 times, most recently
from
April 18, 2024 14:55
ac8481f
to
4f912c7
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
April 18, 2024 14:57
4f912c7
to
f483f79
Compare
renovate
bot
force-pushed
the
renovate/nuxt
branch
from
April 23, 2024 15:19
3651bb5
to
96c6c64
Compare
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. |
farnabaz
approved these changes
Apr 23, 2024
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.10.3
->^3.11.2
Release Notes
nuxt/nuxt (nuxt)
v3.11.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 unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
useServerHead
in dev (#26421)🩹 Fixes
navigateTo
open
option on server side (#26392)definePageMeta
in server pages (#26422)joinRelativeURL
+ share paths on server (#26407)<srcDir>/index.html
from import protection (#26430)refreshCookie
on server (22ada37b4)v-if
to wrapper in islands transform (#26386)getLatestManifest
(#26486)GlobalComponents
in multiple vue modules (#26541)transformAssetUrls
+ passhoistStatic
to vite plugin (#26563)typescript.shim
(#26607)useRoute
(#26633)💅 Refactors
navigateTo
for server (#26546)runtimeConfig
initialization of client side (#26558)📖 Documentation
prerenderRoutes
in dynamic routes (#26547)process.*
withimport.meta.*
(#26611)typescript.shim
JSDoc (#26626)🏡 Chore
❤️ Contributors
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
👀 Highlights
This is possibly the last minor release before Nuxt v4, and so we've packed it full of features and improvements we hope will delight you! ✨
🪵 Better logging
When developing a Nuxt application and using
console.log
in your application, you may have noticed that these logs are not displayed in your browser console when refreshing the page (during server-side rendering). This can be frustrating, as it makes it difficult to debug your application. This is now a thing of the past!Now, when you have server logs associated with a request, they will be bundled up and passed to the client and displayed in your browser console. Asynchronous context is used to track and associate these logs with the request that triggered them. (#25936).
For example, this code:
will now log to your browser console when you refresh the page:
👉 We also plan to support streaming of subsequent logs to the Nuxt DevTools in future.
We've also added a
dev:ssr-logs
hook (both in Nuxt and Nitro) which is called on server and client, allowing you to handle them yourself if you want to.If you encounter any issues with this, it is possible to disable them - or prevent them from logging to your browser console.
🎨 Preview mode
A new
usePreviewMode
composable aims to make it simple to use preview mode in your Nuxt app.When preview mode is enabled, all your data fetching composables, like
useAsyncData
anduseFetch
will rerun, meaning any cached data in the payload will be bypassed.Read more in the docs.
💰 Cache-busting payloads
We now automatically cache-bust your payloads if you haven't disabled Nuxt's app manifest, meaning you shouldn't be stuck with outdated data after a deployment.
👮♂️ Middleware
routeRules
It's now possible to define middleware for page paths within the Vue app part of your application (that is, not your Nitro routes) (#25841).
⌫ New
clear
data fetching utilityNow,
useAsyncData
anduseFetch
expose aclear
utility. This is a function that can be used to setdata
to undefined, seterror
tonull
, setpending
tofalse
, setstatus
toidle
, and mark any currently pending requests as cancelled. (#26259)🕳️ New
#teleports
targetNuxt now includes a new
<div id="teleports"></div>
element in your app within your<body>
tag. It supports server-side teleports, meaning you can do this safely on the server:🚦 Loading indicator and transition controls
It's now possible to set custom timings for hiding the loading indicator, and forcing the
finish()
method if needed (#25932).There's also a new
page:view-transition:start
hook for hooking into the View Transitions API (#26045) if you have that feature enabled.🛍️ Server- and client-only pages
This release sees server- and client-only pages land in Nuxt! You can now add a
.server.vue
or.client.vue
suffix to a page to get automatic handling of it.Client-only pages will render entirely on the client-side, and skip server-rendering entirely, just as if the entire page was wrapped in
<ClientOnly>
. Use this responsibly. The flash of load on the client-side can be a bad user experience so make sure you really need to avoid server-side loading. Also consider using<ClientOnly>
with afallback
slot to render a skeleton loader (#25037).⚗️ Server-only pages are even more useful because they enable you to integrate fully-server rendered HTML within client-side navigation. They will even be prefetched when links to them are in the viewport - so you will get instantaneous loading (#24954).
🤠 Server component bonanza
When you are using server components, you can now use the
nuxt-client
attribute anywhere within your tree (#25479).You can listen to an
@error
event from server components that will be triggered if there is any issue loading the component (#25798).Finally, server-only components are now smartly enabled when you have a server-only component or a server-only page within your project or any of its layers (#26223).
🔥 Performance improvements
We've shipped a number of performance improvements, including only updating changed virtual templates (#26250), using a 'layered' prerender cache (#26104) that falls back to filesystem instead of keeping everything in memory when prerendering - and lots of other examples.
📂 Public assets handling
We have shipped a reimplementation of Vite's public asset handling, meaning that public assets in your
public/
directory or your layer directories are now resolved entirely by Nuxt (#26163), so if you have addednitro.publicAssets
directories with a custom prefix, these will now work.📦 Chunk naming
We have changed the default
_nuxt/[name].[hash].js
file name pattern for your JS chunks. Now, we default to_nuxt/[hash].js
. This is to avoid false positives by ad blockers triggering off your component or chunk names, which can be a very difficult issue to debug. (#26203)You can easily configure this to revert to previous behaviour if you wish:
💪 Type fixes
Previously users with
shamefully-hoist=false
may have encountered issues with types not being resolved or working correctly. You may also have encountered problems with excessive type instantiation.We now try to tell TypeScript about certain key types so they can be resolved even if deeply nested (#26158).
There are a whole raft of other type fixes, including some regarding import types (#26218 and #25965) and module typings (#25548).
✅ 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
nuxt-client
in all components (#25479)page:view-transition:start
hook (#26045)finish()
(#25932)<NuxtIsland>
can't fetch island (#25798)usePreviewMode
composable (#21705)#teleports
element for ssr teleports (#25043)typescript.hoist
(85166cced)getCachedData
(#26287)nuxtMiddleware
route rule (#25841)clear
utility touseAsyncData
/useFetch
(#26259)🔥 Performance
isPrerendered
in dev for server page (#26061)🩹 Fixes
.config/nuxt.config
(5440ecece).config/nuxt.*
(7815aa534)error
inshowError
/createError
with h3 (#25945)useId
(#25969)vueCompilerOptions
property totsConfig
(#25924)useRuntimeConfig
in Nuxt renderer (#26058)typescript.shim
in favour of volar (#26052)defu
/h3
paths in type templates (#26085)toExports
fromunimport
(#26086)AsyncDataRequestStatus
type (#26023)<html>
and<body>
attrs (#26027)node_modules
formodulesDir
(#25548)routeRules
(#26120)cookieRef
values deeply (#26151)ssrRender
(#26162)ssr: false
(f080c426a)baseUrl
within server components (#25727)useNuxtData
(#22277)publicAssetsURL
(9d08cdfd1)buildAssetsDir
(81933dfc3)joinRelativeURL
for build assets (#26282)deep
toselectiveClient
(357f8db41)consola
for now (adbd53a25)window
access more carefully (977377777)💅 Refactors
request
computation (#26191)nuxtMiddleware
toappMiddleware
(cac745470)📖 Documentation
useId
composable was introduced (#25953)domEnvironment
option to testing example (#25972)fallback
prop for<NuxtLayout>
(#26091)vue-tsc
(#26083)macros.pageMeta
andtypescript.esbuild
option (#26136)definePageMeta
page (#26139)app:manifest:update
hook (#26192)zhead
(e889a7df5)clear
(24217a992)appMiddleware
docs (da8e8eba8)🏡 Chore
✅ Tests
scrollY
(#26298)networkidle
(9b5bffbbb)🤖 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.