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.5.0
->^0.5.1
^18.18.5
->^18.18.6
^6.7.5
->^6.8.0
^6.7.5
->^6.8.0
^8.51.0
->^8.52.0
^15.0.1
->^15.0.2
^3.7.4
->^3.8.0
^4.4.11
->^4.5.0
^3.3.4
->^3.3.6
^1.8.19
->^1.8.20
Release Notes
vuejs/pinia (@pinia/nuxt)
v0.5.1
Compare Source
Please refer to CHANGELOG.md for details.
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.8.0
Compare Source
Bug Fixes
Features
prefer-destructuring
(#7117) (3c6379b)You can read about our versioning strategy and releases on our website.
6.7.5 (2023-10-09)
Bug Fixes
You can read about our versioning strategy and releases on our website.
6.7.4 (2023-10-02)
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
6.7.3 (2023-09-25)
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
6.7.2 (2023-09-18)
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
6.7.1 (2023-09-18)
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.8.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.7.5 (2023-10-09)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.7.4 (2023-10-02)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.7.3 (2023-09-25)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.7.2 (2023-09-18)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.7.1 (2023-09-18)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
eslint/eslint (eslint)
v8.52.0
Compare Source
Features
70648ee
feat: report-unused-disable-directive to report unused eslint-enable (#17611) (Yosuke Ota)Bug Fixes
5de9637
fix: Ensure shared references in rule configs are separated (#17666) (Nicholas C. Zakas)dcfe573
fix: add preceding semicolon in suggestions ofno-object-constructor
(#17649) (Francesco Trotta)Documentation
476d58a
docs: Add note about invalid CLI flags when using flat config. (#17664) (Nicholas C. Zakas)660ed3a
docs: Plugin flat config migration guide (#17640) (Nicholas C. Zakas)a58aa20
docs: fix examples for several rules (#17645) (Milos Djermanovic)179929b
docs: Remove trailing newline from the code of Playground links (#17641) (Francesco Trotta)f8e5c30
docs: Update README (GitHub Actions Bot)b7ef2f3
docs: Enable pretty code formatter output (#17635) (Nicholas C. Zakas)0bcb9a8
docs: Fix syntax errors in rule examples (#17633) (Francesco Trotta)61b9083
docs: Make no-continue example code work (#17643) (Zhongyuan Zhou)9fafe45
docs: upgrade to 11ty 2.0 (#17632) (Percy Ma)ff8e4bf
docs: Update README (GitHub Actions Bot)fab249a
docs: Update README (GitHub Actions Bot)392305b
docs: Updateno-irregular-whitespace
and fix examples (#17626) (Francesco Trotta)6b8acfb
docs: Add real whitespace tono-trailing-spaces
examples (#17630) (Francesco Trotta)1000187
docs: Fix examples inunicode-bom
(#17631) (Francesco Trotta)000290c
docs: Update README (GitHub Actions Bot)Chores
6d1f0c2
chore: upgrade @eslint/js@8.52.0 (#17671) (Milos Djermanovic)d63d4fe
chore: package.json update for @eslint/js release (ESLint Jenkins)f30cefe
test: fix FlatESLint tests for caching (#17658) (Milos Djermanovic)ef650cb
test: update tests for no-promise-executor-return (#17661) (Milos Djermanovic)okonet/lint-staged (lint-staged)
v15.0.2
Compare Source
Patch Changes
8e82364
Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.nuxt/nuxt (nuxt)
v3.8.0
Compare Source
👀 Highlights
We have a lot of exciting features in v3.8, and can't wait for you to try it out.
💻 Nuxi improvements
Just to remind you, we're now using the new Nuxt CLI which is now versioned separately. There are some exciting improvements there to follow, so do check out the latest releases. (For example, we now share the same port with the Vite websocket, meaning better support for docker containers in development.)
🚨 Built-in Nuxt DevTools
Nuxt DevTools v1.0.0 is out and we now think it's ready to be shipped as a direct dependency of Nuxt.
👉 You can check out the release notes for more information - and stay tuned for an article detailing our roadmap for the future.
📸 Nuxt Image auto-install
We've now made
<NuxtImg>
and<NuxtPicture>
first-class built-in components, documenting them and auto-installing@nuxt/image
the first time that they are used (#23717).autoinstall2.mp4
We would definitely advise using
@nuxt/image
if you're using images in your site; it can apply optimisations to make your site more performant.📂 Deeper layout scanning
🚨 This is a behaviour change so do take care with this one: 🚨
We now support scanning layouts within subfolders in
~/layouts
in the same way as we do with~/components
.File | Layout name
-- | --
~/layouts/desktop/default.vue | 'desktop-default'
~/layouts/desktop-base/base.vue | 'desktop-base'
~/layouts/desktop/index.vue | 'desktop'
See #20190 for more information
📊 App Manifest
We now support a built-in app manifest (see #21641), which generates a manifest at
/_nuxt/builds/meta/<buildId>.json
.Initially this enables loading payloads only for prerendered routes, if a site is static (preventing 404s). It also enables client-side route rules. To begin with, only
redirect
route rules will have an effect; they will now redirect when performing client-side navigation. (More coming soon...!)The app manifest also enables future enhancements including detection of outdated deployments by checking
/_nuxt/builds/latest.json
.You can switch off this behaviour if you need to (but do let us know if you have any issues):
🤝 Scope and context improvements
We now define a 'scope' for Nuxt composables executed in plugins (#23667), which allows running synchronous cleanup before navigating away from your site, using the Vue
onScopeDispose
lifecycle method. This should fix an edge case with cookies (#23697) and also improves memory management, for example in Pinia stores (#23650). You can read more about Vue effect scopes.We also now support native async context for the Vue composition API (#23526). In case you're unaware, we support native async context on Node and Bun, enabled with
experimental.asyncContext
. This can help address issues with missing a Nuxt instance. But it didn't previously affect missing Vue instances.If you experience issues with 'Nuxt instance unavailable', enabling this option may solve your issues, and once we have cross-runtime support we are likely to enable it by default.
🔗 NuxtLink defaults
We've supported defining your own
NuxtLink
components with thedefineNuxtLink
utility. We now support customising the options for the built-in<NuxtLink>
, directly in yournuxt.config
file (#23724). This can enable you to enforce trailing slash behaviour across your entire site, for example.⚡️ Data fetching improvements: deep and caching
We have two very significant new features for
useAsyncData
anduseFetch
:deep: false
to prevent deep reactivity on thedata
object returned from these composables (#23600). It should be a performance improvement if you are returning large arrays or objects. The object will still update when refetched; it just won't trigger reactive effects if you change a property deep within thedata
.getCachedData
option to handle custom caching for these composables (#20747)We also support configuring some default values for these composables in an app-wide way (#23725):
🔢 Layer improvements
We now more carefully load layer plugins (#22889 and #23148) and middleware (#22925 and #23552) in the order of the layers, always loading your own plugins and middleware last. This should mean you can rely on utilities that layers may inject.
We've also added a test suite to cover these layer resolution changes.
And probably one of the most significant changes - if you are using remote layers we now clone these within your
node_modules/
folder (#109) so layers can use dependencies with your project. Seec12
release notes for full details.😴 Nightly release channel
Every commit to the
main
branch of Nuxt is automatically deployed to a new release, for easier testing before releases. We've renamed this from the 'edge release channel' to the 'nightly release channel' to avoid confusion with edge deployments. And probably also with Microsoft Edge (though I haven't heard that anyone was confused with that one!)➡️
nuxt3
is nownuxt-nightly
➡️
nuxi-edge
is nownuxi-nightly
➡️
@nuxt/kit-edge
is now@nuxt/kit-nightly
... and so on.
You can read more about how it works.
⚗️ Nitro v2.7
Nitro v2.7 has been released with lots of improvements and bug fixes - do check out the full changelog.
🔥 One of the most significant is that we now save ~40% of bundle size in production by using native
fetch
(which is supported in Node 18+) (#1724). So if possible, we'd recommend you update your Node version to at least 18.💪 Type import changes
🚨 This is likely to need code changes in your project 🚨
Vue requires that type imports be explicit (so that the Vue compiler can correctly optimise and resolve type imports for props and so on). See core Vue
tsconfig.json
.We've therefore taken the decision to turn on
verbatimModuleSyntax
by default in Nuxt projects, which will throw a type error if types are imported without an explicittype
import. To resolve it you will need to update your imports:You may also encounter modules in the Nuxt ecosystem that need to be updated; please open an issue for those modules. I'm also very happy to help if you're encountering any problems with this, if you're a module author. Just tag me and I'll take a look.
If for whatever reason you need to undo this change in your project you can set the following configuration:
However, we'd recommend only doing that temporarily, as Vue does need this option to be set for best results.
✅ Upgrading
As usual, our recommendation for upgrading is to run:
👉 Changelog
compare changes
🚀 Enhancements
addServerImports
andaddServerImportsDir
(#23288)prerenderRoutes
ssr composable (#22863)appManifest
by default (#23448)withAsyncContext
(#23526)-nightly
extension (#23508)@nuxt/devtools
as dependency and enable (#23576)deep: false
for data composables (#23600)@nuxt/image
when it is used (#23717)<NuxtLink>
options (#23724)🔥 Performance
🩹 Fixes
asyncData
errors withnull
(#23428)vue-router
(#23440)config.autoImport
inaddServerImports
(#23472)clearNuxtState
called w/o keys (#23483)addPrerenderRoutes
name (#23509)test
/dev
as manifest buildId when appropriate (#23512)<DevOnly>
(#23466)useFetch
(#23693)lodash-es
+ simplify postcss resolution (#23692)useAsyncData
(#23351)prerenderedAt
to override app manifest (#23781)prerenderedAt
behaviour pending next patch (108b1bdf7)📖 Documentation
listhen
options on nuxi dev page (#23415)handler
foruseAsyncData
(#23389)nitro
to useruntimeConfig
(#23454)bridge.typescript
option must be set. (#23503)nuxt kit
section (#22375)/edge-channel
page to/nightly-release-channel
(#23648)routeRules
example (818dc626c)<NuxtImg>
and<NuxtPicture>
(#23741)🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
vitejs/vite (vite)
v4.5.0
Compare Source
Please refer to CHANGELOG.md for details.
vuejs/core (vue)
v3.3.6
Compare Source
Bug Fixes
Performance Improvements
v3.3.5
Compare Source
Bug Fixes
inert
attribute and missinghidden
values (#8090) (ceb0732)Performance Improvements
MutationObserver
listener when disconnected (#8666) (24d98f0)defineComponent
as side-effects-free (#8512) (438027c)vuejs/language-tools (vue-tsc)
v1.8.20
Compare Source
v-bind
argument to be an object (#3666) - thanks @so1ve$event
(#3668) - thanks @so1vevolar
tovue
in diagnostics (#3667) - thanks @so1veFull-time Support by
WebContainer API is here.
Our Platinum Sponsors
Our Silver Sponsors
Add you via GitHub Sponsors or Open Collective
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/Rome, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.