-
Notifications
You must be signed in to change notification settings - Fork 4
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 v3 - autoclosed #283
Closed
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
force-pushed
the
renovate/nuxt-3.x
branch
from
November 23, 2022 09:16
6dec175
to
7b47e5c
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
3 times, most recently
from
December 7, 2022 20:57
c790dde
to
b9500af
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
5 times, most recently
from
December 14, 2022 02:27
7645647
to
6c8904c
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
December 17, 2022 01:28
6c8904c
to
f4f12a7
Compare
renovate
bot
changed the title
chore(deps): update dependency nuxt to v3
Update dependency nuxt to v3
Dec 17, 2022
renovate
bot
changed the title
Update dependency nuxt to v3
chore(deps): update dependency nuxt to v3
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
December 18, 2022 02:20
f4f12a7
to
66af0cf
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
December 26, 2022 22:28
66af0cf
to
5d9ba8d
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
January 14, 2023 08:00
c2898ba
to
58ceb95
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
3 times, most recently
from
January 31, 2023 02:59
6bf31a6
to
27d8a4f
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
5 times, most recently
from
February 9, 2023 16:53
75db765
to
1717ae8
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
February 17, 2023 22:17
1717ae8
to
4856f54
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
February 28, 2023 13:36
4856f54
to
ce421a0
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
4 times, most recently
from
March 17, 2023 19:46
b0082f8
to
128fdbc
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
April 13, 2023 16:05
079570d
to
759b0b1
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
April 23, 2023 15:17
4a3cb74
to
131c6f7
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
May 3, 2023 13:08
5c19afb
to
d2e7f92
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
May 21, 2023 18:42
fe7d2da
to
ea89156
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
May 29, 2023 13:56
ea89156
to
410d91e
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
June 10, 2023 01:11
c15d32a
to
69474fc
Compare
renovate
bot
changed the title
chore(deps): update dependency nuxt to v3
chore(deps): update dependency nuxt to v3 - autoclosed
Jun 21, 2023
renovate
bot
changed the title
chore(deps): update dependency nuxt to v3 - autoclosed
chore(deps): update dependency nuxt to v3
Jun 22, 2023
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
4 times, most recently
from
June 29, 2023 13:00
b5f37a2
to
681af1d
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
3 times, most recently
from
July 6, 2023 03:05
15ab767
to
e74d995
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
2 times, most recently
from
July 19, 2023 17:28
871fbf6
to
0e23a73
Compare
renovate
bot
force-pushed
the
renovate/nuxt-3.x
branch
from
July 19, 2023 18:02
0e23a73
to
9744d4e
Compare
renovate
bot
changed the title
chore(deps): update dependency nuxt to v3
chore(deps): update dependency nuxt to v3 - autoclosed
Jul 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
2.15.8
->3.6.5
Release Notes
nuxt/nuxt (nuxt)
v3.6.5
Compare Source
v3.6.4 release notes
✅ 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
dist
from the default ignore list (#22227)❤️ Contributors
v3.6.4
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
buildDir
andnode_modules
(#22214)🩹 Fixes
toLowerCase
for possiblemoduleResolution
(#22160)baseURL
to island fetch requests (#22009)--inspect
in dev mode (#22205)📖 Documentation
❤️ Contributors
v3.6.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 unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
unctx
options (4e32e70bb)isExternal
(#21966)experimental
option (0643d4315)💅 Refactors
bundler
module resolution flag (#22142)📖 Documentation
/
(#22118)🏡 Chore
❤️ Contributors
v3.6.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
🩹 Fixes
@nuxt/ui-templates
frommodulesDir
(#21836)nuxi generate
(#21860)tsconfig.json
scope (#21917)typedPages
(#21659)node_modules
to tsconfig include (#21929)$fetch.raw
in dev client mode for islands (#21904)vite.publicDir
(#21847)📖 Documentation
spaLoadingTemplate
link (#21845)<NuxtLoadingIndicator>
(#21952)🏡 Chore
✅ Tests
nuxt-vitest
and composable unit tests (#21884)❤️ Contributors
v3.6.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
typescript
dep (#21729)false
to disable spa loading template (#21739)path
from SPA payload (#21732)ssr: false
route rule (#21763)#imports
(#21796)📖 Documentation
defineNuxtRouteMiddleware
migration (#21718)✅ Tests
❤️ Contributors
v3.6.0
Compare Source
📣 Upcoming news
In the coming week you can expect two announcements:
nuxt/cli
by @pi0 - a new, drop-in replacement fornuxi
featuring more extensibility and better DX. We are aiming to release this alongside Nuxt 3.7, but you would be very welcome to test and contribute tonuxi-ng
before then!👀 Highlights
This minor release contains quite a lot, and we have big plans
SPA loading indicator
If your site is served with
ssr: false
or you have disabled server-rendering on some of your pages, you might be particularly interested in the new built-in SPA loading indicator.You can now place an HTML file in
~/app/spa-loading-template.html
with some HTML you would like to use to render a loading screen that will be rendered until your app is hydrated on these pages.👉 By default an animated Nuxt icon is rendered. You can completely disable this indicator by setting
spaLoadingTemplate: false
in your nuxt configuration file.⚡️ Performance improvements
The first thing that happens when your app is hydrated is that your plugins run, and so we now perform build-time optimisations on your plugins, meaning they do not need to be normalised or reordered at runtime.
We also include your error component JS in your main entrypoint, meaning that if an error occurs when a user has no connectivity, you can still handle it with your
~/error.vue
. (This also should decrease your total bundle size.)👉 Compared to Nuxt 3.5.3, the minimal client bundle has decreased by ~0.7kB. Let's keep this up!
🔥 Fully static server components
It has been possible to use server components on static pages, but until now they would increase the payload size of your application. That is no longer true. We now store rendered server components as separate files, which are preloaded before navigation.
👉 This does rely on the new, richer JSON payload format, so make sure you have not disabled this by setting
experimental.renderJsonPayloads
to false.🎨 Better style inlining
If you're monitoring your metrics closely and have not turned off
experimental.inlineSSRStyles
, you should see more CSS inlined in your page, and a significantly external CSS file. We're now better at deduplicating global CSS, particularly added by libraries like tailwind or unocss.🎬 Animation controls
To give you more fine-grained control over your page/layout components, for example to create custom transitions with GSAP or other libraries, we now allow you to set
pageRef
on<NuxtPage>
andlayoutRef
on<NuxtLayout
. These will get passed through to the underlying DOM elements.✨ Automatic 'static' preset detection
Up to now, running
nuxt generate
produced the same output on every deployment provider, but with Nuxt 3.6 we now enable static provider presets automatically. That means if you are deploying a static build (produced withnuxt generate
) to a supported provider (currently vercel and netlify with cloudflare and github pages coming soon) we'll prerender your pages with special support for that provider.This means we can configure any route rules (redirects/headers/etc) that do not require a server function. So you should get the best of both worlds when deploying a site that doesn't require runtime SSR. It also unblocks use of Nuxt Image on Vercel (with more potential for automatic provider integration coming soon).
💪 Increased type safety
We now have better support for server-specific
#imports
and augmentations if you are using the new~/server/tsconfig.json
we shipped in Nuxt 3.5. So when importing from#imports
in your server directory, you'll get IDE auto-completion for the right import locations in Nitro, and won't see Vue auto-imports likeuseFetch
that are unavailable within your server routes.You should now also have type support for runtime Nitro hooks.
Finally, we have removed more locations where objects had a default
any
type. This should improve type safety within Nuxt in a number of locations where unspecified types fell back to any:RuntimeConfig
PageMeta
NuxtApp['payload']
(accessible now fromNuxtPayload
interface)ModuleMeta
You can find out more about how to update your code if this affects you in the original PR.
⚗️ Nitro 2.5 built-in
This release ships with new Nitro 2.5, which has a whole list of exciting improvements that are worth checking out.
Of particular note is experimental support for streaming, which is also enabled by a couple of changes in Nuxt itself.
🛠️ New tools for module authors
This release brings a number of utilities for modules authors to easily add type templates and assert compatibility with a given version of another module.
In addition, this release will finally unlock a new
nuxt/module-builder
mode that should improve type support for module authors. If you're a module author, you might consider following these migration steps to try it out in the coming days.✅ 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
useCookie
state between tabs (#20970)renderResult
toapp:rendered
(#18610)esbuild-loader
options (#21436)open
option innavigateTo
helper (#21333)clearNuxtState
composable (#21409)addTypeTemplate
helper with auto-registration (#21331)status
fromuseAsyncData
(#21045)NuxtPage
ref viapageRef
(#19403)NuxtLayout
ref vialayoutRef
(#19465)ssr-error
event (#21547)defineNuxtModule
(#20763)useNuxtApp
to window for convenience (#21636)🔥 Performance
🩹 Fixes
resolveId
workaround and update vite-node (#21423)nitro.autoImport
option (#21485)dst
notsrc
(#21501)navigateTo
(#21500)window.location
(#21521)<Title>
(#21613):
in rendered server components (for win) (#21645)baseUrl
intsconfig.json
(#21632)BroadcastChannel
(#21653)@typescript-eslint/typescript-estree
(#21664)res.end()
calls with check if event is handled (#21665)redirect
type forNuxtPage
type (#21713)📖 Documentation
render
when definingrendering
(#21490)addTypeTemplate
typos (#21520)nuxt
with bridge ifnitro
is false (#21586)parallel
option on plugins (#21622)examples/
from repository (#21538)@latest
to install commands (#21702)🏡 Chore
vitest
renovate group (7695aca93)octokit/request-action
(dd5955caf)webpack-dev-middleware
updates on 2.x branch (7f7ae96d1)✅ Tests
🤖 CI
❤️ Contributors
v3.5.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 unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
--no-clear
config through to vite (#21262)vue-loader
options type (#21363)typeCheck
(#21064)std-env
in runtime code (#21372)lodash.template
fromlodash-es
(#20892)📖 Documentation
index.vue
to page routing example (#21240)$fetch
and fetch composables (#21228)env
property to matchruntimeConfig
(#21265)🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v3.5.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
.test
and hoist regexps where possible (#21011)🩹 Fixes
@default
jsdoc tag (#21010)pages/
integration (397c54c9d)<DevOnly>
with webpack (#21013)refreshNuxtData
(#21008)abortNavigation
(#21047)Set-Cookie
header if value is null (#21072)📖 Documentation
render:island
hook (#21065)🏡 Chore
✅ Tests
❤️ Contributors
v3.5.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
🔥 Performance
🩹 Fixes
/
route (#20894)useFetch
method when generic is passed (#20797)refresh
when hydrating when data is present (#20916)default
type for initial value for composables (#20968)resolvePath
to handle edge cases for modules (#20975)📖 Documentation
pnpm test
command to run whole test suite (4907660ff)experimental.renderJsonPayloads
(891ba880e)useAsyncData
anduseFetch
types (#20935)useState
(#20249)pages/
docs (#20976)🏡 Chore
🤖 CI
❤️ Contributors
v3.5.0
Compare Source
👀 Highlights
⚡️ Vue 3.3 released!
Vue 3.3 has been released, with lots of exciting features, particularly around type support. This also brings a significant improvement to data fetching when navigating between nested pages (https://github.com/nuxt/nuxt/pull/20777), thanks to @antfu and @baiwusanyu-c.
defineOptions
macroRead the full release announcement for more details.
🙌 Nitropack v2.4
We've been working on lots of improvements to Nitro and these have landed already in Nitro v2.4 - you may already have this upgrade, which contains a lot of bug fixes, updates to the module worker format for Cloudflare, Vercel KV support and more.
One note: if you're deploying to Vercel or Netlify and want to benefit from incremental static regeneration, you should now update your route rules:
Read the full release notes.
💖 New defaults
Rich JSON payload serialisation is now enabled by default (https://github.com/nuxt/nuxt/pull/19205, https://github.com/nuxt/nuxt/pull/20770). This is both faster and allows serialising complex objects in the payload passed from the Nuxt server to client (and also when extracting payload data for prerendered sites).
This now means that various rich JS types are supported out-of-the-box: regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like
ref
,reactive
,shallowRef
andshallowReactive
.You can find an example in our test suite.
This is all possible due to Rich-Harris/devalue#58. For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original.
You can even register your own custom types with a new object-syntax Nuxt plugin:
You can read more about how this works here.
🛝 Interactive server components
This feature should be considered highly experimental, but thanks to some great work from @huang-julien we now support interactive content within server components via slots (https://github.com/nuxt/nuxt/pull/20284).
You can follow the server component roadmap at https://github.com/nuxt/nuxt/issues/19772.
⏰ Environment config
You can now configure fully typed, per-environment overrides in your
nuxt.config
:If you're authoring layers, you can also use the
$meta
key to provide metadata that you or the consumers of your layer might use.Read more: https://github.com/nuxt/nuxt/pull/20329.
💪 Fully typed pages
You can benefit from fully typed routing within your Nuxt app via this experimental integration with https://github.com/posva/unplugin-vue-router - thanks to some great work from @posva! Out of the box, this will enable typed usage of
navigateTo
,<NuxtLink>
,router.push()
and more. You can even get typed params within a page by usingconst route = useRoute('route-name')
.🔎 'Bundler' module resolution
We now have full support within Nuxt for the
bundler
strategy of module resolution. We would recommend adopting this if possible. It has type support for subpath exports, for example, but more exactly matches the behaviour of build tools like Vite and Nuxt thanNode16
resolution.This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like
mylib/path
that is mapped tomylib/dist/path.mjs
then the types for this can be pulled in frommylib/dist/path.d.ts
rather than requiring the library author to createmylib/path.d.ts
.⚗️ Separate server types
We plan to improve clarity within your IDE between the 'nitro' and 'vue' part of your app, and we've shipped the first part of this via a separate generated
tsconfig.json
for your~/server
directory (https://github.com/nuxt/nuxt/pull/20559). You can use by adding an additional~/server/tsconfig.json
with the following content:Although right now these values won't be respected when type checking, you should get better type hints in your IDE.
💀 Deprecations
Although we have not typed or documented the
build.extend
hook from Nuxt 2, we have been calling it within the webpack builder. We are now explicitly deprecating this and will remove it in a future minor version.✅ 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
prepend
option toaddImportsDir
(#20307)vite:configResolved
hook (#20411)webpack:configResolved
hook (#20412)addVitePlugin
andaddWebpackPlugin
(#20525)nuxi analyze
from cli (#20387)nuxtApp.runWithContext
(#20608)typedPages
option (#20367)runWithContext
withincallWithNuxt
(#20775)useRequestURL
helper (#20765)<DevOnly>
([#20817](https://togithub.com/nuxt/nuxt/pulConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.