chore(deps): bump the all-updates group across 1 directory with 15 updates

[dependabot]

Bumps the all-updates group with 15 updates in the / directory:

Package	From	To
@nuxt/hints	1.0.0-alpha.6	1.0.0
nuxt	4.3.0	4.4.2
vue	3.5.27	3.5.30
@iconify-json/tabler	1.2.26	1.2.31
@nuxt/fonts	0.13.0	0.14.0
@vueuse/core	14.2.0	14.2.1
drizzle-kit	1.0.0-beta.12-a5629fb	1.0.0-beta.18-905b79a
drizzle-orm	1.0.0-beta.12-a5629fb	1.0.0-beta.18-905b79a
drizzle-seed	1.0.0-beta.12-a5629fb	1.0.0-beta.18-905b79a
sass	1.97.3	1.98.0
taze	19.9.2	19.10.0
valibot	1.2.0	1.3.0
vite	8.0.0-beta.11	8.0.0
vue-tsc	3.2.4	3.2.6
wrangler	4.61.1	4.75.0

Updates @nuxt/hints from 1.0.0-alpha.6 to 1.0.0

Release notes

Sourced from @​nuxt/hints's releases.

v1.0.0

Nuxt Hints v1.0.0

We are very excited to move Nuxt hints from alpha stage to 1.0.0 !

Developer experience in Nuxt is truly something we treasure and we hope this module will help you out on finding different ways to make your Nuxt application more performant. We also want to thank every contributors and users of the modules. It is thanks to them that @​nuxt/hints is reaching 1.0.0

Vision

Our vision at Nuxt has always been that better DX will have an impact on end-user's UX. By releasing this module, the goal is to help Nuxt developers to improve their Nuxt applications.

Roadmap

• Production build integration
  • Having runtime warning in production could help users to actually get what happens in production
• Font and scripts performance hints
• Your ideas !
  • Nuxt is what it is thanks to it's incredible community. Your ideas and feedbacks are always welcomed and have an impact on the future of Nuxt.

Features

v1.0.0 comes with several improvement:

🚀 Enhancements

• Html-validate integration (#253)
• hydration: Improve hydration log (#258)
• client: Allow to open potential lazy load components in editor (#270)
• Add feature related configuration (#261)

🩹 Fixes

• lazy-load: Avoid wrapping glob imports (#264)
• TDZ violation in lazy-hydration plugin with .client components (#265)
• web-vitals: Report all changes for CLS (#266)
• client: Remove shiki fit content style (#272)
• web-vitals: Correct next-gen image format detection logic (#273)
• Set correct tsconfig.json (#274)

❤️ Thank you to all contributors

• Julien Huang (@​huang-julien)
• @​dargmuesli
• @​Baroshem
• @​danielroe
• @​Mini-ghost
• @​atinux
• @​TheAlexLichter
• @​gmercey

... (truncated)

Commits

• d468c8b chore: 1.0.0 (#275)
• a071165 chore(deps): bump tar from 7.5.9 to 7.5.11 (#276)
• 469ace2 chore(deps): update all non-major dependencies (#271)
• 51b0da2 feat: add feature related configuration (#261)
• 63e5127 fix: set correct tsconfig.json (#274)
• a08b9b9 fix(web-vitals): correct next-gen image format detection logic (#273)
• 42bc3c0 fix(client): remove shiki fit content style (#272)
• 21d6c7f feat(client): allow to open potential lazy load components in editor (#270)
• 05c0148 feat(hydration): improve hydration log (#258)
• 0763406 chore(deps): update all non-major dependencies (#268)
• Additional commits viewable in compare view

Updates nuxt from 4.3.0 to 4.4.2

Release notes

Sourced from nuxt's releases.

v4.3.1

4.3.1 is a regularly scheduled patch release.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Correct reference format of server builder (#34177)
• nuxt: Add status/statusText getters to NuxtError (#34188)
• nuxt: Don't inject shared types for differing auto-imports (#34191)
• schema: Add direnv and vendor to default ignore (#34190)
• nuxt: Focus hash links after navigation (#34193)
• nuxt: Exclude head runtime from unhead imports transform (#34195)
• kit: Include prereleases in semver satisfy check (#34210)
• nitro: Encode unicode paths in x-nitro-prerender header (#34202)
• nuxt: Watch server/ for builder:watch hook (#34208)
• nitro: Preserve error.message for fatal errors (#34226)
• Only enable dynamic imports when ts plugin (#34205)
• webpack: Use H3Error for 403 in dev server (#34233)
• nuxt: Ensure NuxtError extends Error type (#34242)
• vite: Use H3Error for 404 in dev server (#34225)
• nuxt: Add backwards compat for #app barrel export in keyed functions (#34199)
• nuxt: Track + re-add custom routes on hmr (#32044)
• nuxt: Keep vnode when leaving deeper nested route (#33778)
• vite: Prevent CSS flickering in dev mode after config changes (#33856)
• nuxt: Do not start view transition if there is no route (#33723)
• nuxt: Call deferHydration done on NuxtPage unmount (#34152)
• nuxt: Handle invalid datetime in ` (#33992)
• nuxt: Preserve middleware error status in 404 fallback (#34148)
• nitro: Do not augment nuxt/schema (#34255)
• nuxt: Cache manifest files to preserve buildId (#34002)
• nuxt: Don't decode query string in SSR context URL (#34252)
• nuxt: Allow specifying moduleDependencies by meta.name (#34263)
• nuxt: Resolve #components import mapping conflict for packages outside rootDir (#34139)
• vite,webpack: Use node.res to send 403/404 (#34266)
• nitro,nuxt: Align path encoding with vue-router (#34265)
• nitro: Augment nuxt/schema once more (552bbd8d1)

💅 Refactors

• nuxt: Prefer genObjectKey to omit unnecessary quotes (#34245)
• nuxt: Use ComponentProps helper to extract layout props (#34248)

📖 Documentation

• Update roadmap dates (#34166)
• Correct default value of nitroAutoImports (#34182)
• Clarify shared type context limitations for custom imports (#34194)
• Fix broken links (#34223)
• Document payload extraction for ISR/SWR routes (#34222)
• Update default aliases in configuration reference (#34237)

... (truncated)

Commits

• d042505 v4.4.2
• 7781701 v4.4.1
• 5c3ca59 v4.4.0
• 31028d2 chore: lint
• df7ef5d feat(nuxt,kit,schema): add a factory function for useFetch and `useAsyncDat...
• 2dc5255 fix(nuxt): handle rejected promise in view transition abort (#34515)
• cf3e2ad fix(nuxt): fix cookie expiration timeout for long-lived cookies (#34513)
• 3b9d0bc fix(nuxt): pass deleteCount to splice in preloadRouteComponents (#34514)
• 414a283 fix(nuxt): never preload manifest (#34511)
• d586631 fix(nuxt): check file freshness before truncating in cache restore (#34509)
• Additional commits viewable in compare view

Updates vue from 3.5.27 to 3.5.30

Release notes

Sourced from vue's releases.

v3.5.30

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

v3.5.29

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

v3.5.28

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

Changelog

Sourced from vue's changelog.

3.5.30 (2026-03-09)

Bug Fixes

• compat: add entities to @​vue/compat deps to fix CJS edge cases (#12514) (e725a67), closes #10609
• custom-element: ensure child component styles are injected in correct order before parent styles (#13374) (1398bf8), closes #13029
• custom-element: properly locate parent when slotted in shadow dom (#12480) (f06c81a), closes #12479
• custom-element: should properly patch as props for vue custom elements (#12409) (740983e), closes #12408
• reactivity: avoid duplicate raw/proxy entries in Set.add (#14545) (d943612)
• reactivity: fix reduce on reactive arrays to preserve reactivity (#12737) (16ef165), closes #12735
• reactivity: handle Set with initial reactive values edge case (#12393) (5dc27ca), closes #8647
• runtime-core: warn about negative number in v-for (#12308) (9438cc5)
• ssr: prevent watch from firing after async setup await (#14547) (6cda71d), closes #14546
• types: make generics with runtime props in defineComponent work (fix #11374) (#13119) (cea3cf7), closes #13763
• types: narrow useAttrs class/style typing for TSX (#14492) (bbb8977), closes #14489

3.5.29 (2026-02-24)

Bug Fixes

• runtime-core: prevent instance leak in withAsyncContext (#14445) (702284f), closes nuxt/nuxt#33644
• server-renderer: render className as escaped string (#14469) (da6690c)
• transition: prevent enter if leave is in progress (#14443) (df059f8), closes #12091 #12133

3.5.28 (2026-02-09)

Bug Fixes

• transition: avoid unexpected cancelled parameter in transition done callback (#14391) (6798853)
• compiler-sfc: add resolution trying for .mts/.cts files (#14402) (c09d41f), closes vuejs/router#2611
• compiler-sfc: no params were generated when using withDefaults (#12823) (b0a1f05), closes #12822
• reactivity: add __v_skip flag to EffectScope to prevent reactive conversion (#14359) (48b7552), closes #14357
• runtime-core: avoid retaining el on cached text vnodes during static traversal (#14419) (4ace79a), closes #14134
• runtime-core: prevent child component updates when style remains unchanged (#12825) (57866b5), closes #12826
• runtime-core: properly handle async component update before resolve (#11619) (e71c26c), closes #11617
• runtime-dom: handle null/undefined handler in withModifiers (#14362) (261de54), closes #14361
• teleport: properly handling disabled teleport target anchor (#14417) (d7bcd85), closes #14412
• transition-group: correct move translation under scale via element rect (#14360) (0243a79), closes #14356
• useTemplateRef: don't update setup ref for useTemplateRef key (#12756) (fc40ca0), closes #12749

Commits

• fdd863f release: v3.5.30
• 6cda71d fix(ssr): prevent watch from firing after async setup await (#14547)
• 9438cc5 fix(runtime-core): warn about negative number in v-for (#12308)
• 1398bf8 fix(custom-element): ensure child component styles are injected in correct or...
• 0d63202 chore(deps): update dependency puppeteer to ~24.38.0 (#14544)
• 5098986 chore(deps): update all non-major dependencies (#14498)
• 5d98213 chore(deps): update dependency minimatch to v10.2.3 [security] (#14495)
• 6a06ee5 chore(deps): update actions/upload-artifact action to v7 (#14500)
• 34a5d84 fix(deps): update dependency postcss to ^8.5.8 (#14543)
• d4ea55b chore(deps): update build (#14497)
• Additional commits viewable in compare view

Updates @iconify-json/tabler from 1.2.26 to 1.2.31

Commits

• See full diff in compare view

Updates @nuxt/fonts from 0.13.0 to 0.14.0

Release notes

Sourced from @​nuxt/fonts's releases.

v0.14.0

0.14.0 is the next minor release.

🚨 Breaking changes

Default font format is now woff2 only

Font providers previously returned multiple formats (woff2, woff, truetype, etc.). The default behavior now only resolves woff2 fonts, which is supported by all modern browsers.

Your @font-face declarations will typically have fewer src entries, reducing CSS size. In most cases this is a transparent improvement.

To restore the previous behavior or add additional formats:

export default defineNuxtConfig({
  fonts: {
    defaults: {
      formats: ['woff2', 'woff', 'ttf'],
    },
  },
})

Available values: 'woff2', 'woff', 'ttf', 'otf', 'eot'.

Cache invalidation

Font metadata caches are now isolated per provider and per provider options. After upgrading, your font metadata cache (node_modules/.cache/nuxt/fonts/) will be invalidated and fonts will be re-fetched on the next build. This is a one-time occurrence.

✨ Features

Resolve fonts from node_modules

A new built-in npm provider can resolve fonts installed as npm packages. If no other provider matches a font family, @nuxt/fonts will now attempt to find it in your node_modules via CDN metadata.

export default defineNuxtConfig({
  fonts: {
    npm: {
      // options for the npm provider (optional)
    },
  },
})

Font format resolution

You can control which font formats are resolved via the new defaults.formats option:

</tr></table> 

... (truncated)

Commits

• 95b332b v0.14.0
• fce0318 feat: add support for resolving fonts from local node_modules (#781)
• 035091a test: update snapshots for adobe preloads
• 9d7715d fix(deps): bump unifont + reenable adobe tests
• aedb0e1 chore(deps): update devdependency eslint to v10 (#778)
• de70796 chore(deps): update all non-major dependencies (#762)
• 25c87c4 chore: remove changelog (in favour of github releases)
• 171c9a4 feat: support lightningcss transforms
• 6e8e343 fix: include more css-ish files when injecting font-families
• 0ec437e fix: prevent font flashes in development
• Additional commits viewable in compare view

Updates @vueuse/core from 14.2.0 to 14.2.1

Release notes

Sourced from @​vueuse/core's releases.

v14.2.1

   🚀 Features

• Add skills at the root directory for skills cli  -  by @​antfu (c005d)
• skills: Transfer @vueuse/skills  -  by @​serkodev in vueuse/vueuse#5286 (532ac)

   🐞 Bug Fixes

• useRafFn: Resolve reactive null fpsLimit not being handled  -  by @​nemanjamalesija in vueuse/vueuse#5284 (8ce0d)

    View changes on GitHub

Commits

• c76c4ee chore: release v14.2.1
• 8ce0dae fix(useRafFn): resolve reactive null fpsLimit not being handled (#5284)
• 39afd85 refactor: explicitly define return type (#5275)
• fa483b4 refactor: unify Supportable across composables (#5274)
• See full diff in compare view

Updates drizzle-kit from 1.0.0-beta.12-a5629fb to 1.0.0-beta.18-905b79a

Commits

• See full diff in compare view

Updates drizzle-orm from 1.0.0-beta.12-a5629fb to 1.0.0-beta.18-905b79a

Release notes

Sourced from drizzle-orm's releases.

v1.0.0-beta.17

New SQLite driver node-sqlite

Usage example:

import { drizzle } from 'drizzle-orm/node-sqlite';
const db = drizzle("sqlite.db");
const result = db.select().from(...);

If you need to provide your existing driver:

import { drizzle } from 'drizzle-orm/node-sqlite';
import { DatabaseSync } from 'node:sqlite';
const sqlite = new DatabaseSync('sqlite.db');
const db = drizzle({ client: sqlite });
const result = db.select().from(...);

Fixes

We added a few checks to the migration upgrade logic introduced in beta.16. Now, when your migrations table is upgraded, we double-check that all entities in the table have been updated. If any are missing, we prompt you to pull all migrations into your environment so that we can properly update the drizzle_migrations table

v1.0.0-beta.16

Drizzle ORM beta.16 updates

We've fixed a regression in migrations introduced in beta.13 that persisted through beta.15, and used the opportunity to significantly improve the entire migration infrastructure going forward.

After receiving github issue, we focused on not just fixing the symptoms but rethinking how migrations are tracked, validated, and applied. As we always do with Drizzle we went deeper and redesigned the underlying architecture so it can be stable for all future changes, additions, and edge cases

We went through how we check migrations, how we store them, and how we help developers keep their migration flow reliable. After several iterations of rewriting the migrate function in both ORM and Kit, adding migration table versioning, and building a new commutativity check system: here's what changed and why.

What happened in beta.12–beta.15 and what caused the issue

On latest (pre-beta) versions, the migrations folder used a journal-based structure. A meta/_journal.json file stored a timestamp for each migration in milliseconds. That same millis value was stored in the database's created_at column and used to determine which migrations had been applied. Because the journal enforced ordering, we could simply fetch the last applied migration from the database and apply everything after it.

With the new v3 folder structure (introduced in beta), each migration lives in its own folder named <YYYYMMDDHHmmss>_<name>. This format only has second precision. The new structure also intentionally allows out-of-order migrations (as it should for team workflows), so we switched to reading all migrations from the database and comparing against all local migrations.

The problem appeared after drizzle-kit up converted the old journal structure to v3 folders. It mapped millis timestamps to the YYYYMMDDHHmmss_name format, stripping away the millisecond precision. So when the new migration checker compared what was in the database (millis) to what was on disk (seconds), nothing matched causing migrations to be re-applied on every run.

This only affected beta users who upgraded from the journal-based format. Users on latest were not impacted.

How we fixed it

... (truncated)

Commits

• See full diff in compare view

Updates drizzle-seed from 1.0.0-beta.12-a5629fb to 1.0.0-beta.18-905b79a

Release notes

Sourced from drizzle-seed's releases.

v1.0.0-beta.17

New SQLite driver node-sqlite

Usage example:

import { drizzle } from 'drizzle-orm/node-sqlite';
const db = drizzle("sqlite.db");
const result = db.select().from(...);

If you need to provide your existing driver:

import { drizzle } from 'drizzle-orm/node-sqlite';
import { DatabaseSync } from 'node:sqlite';
const sqlite = new DatabaseSync('sqlite.db');
const db = drizzle({ client: sqlite });
const result = db.select().from(...);

Fixes

We added a few checks to the migration upgrade logic introduced in beta.16. Now, when your migrations table is upgraded, we double-check that all entities in the table have been updated. If any are missing, we prompt you to pull all migrations into your environment so that we can properly update the drizzle_migrations table

v1.0.0-beta.16

Drizzle ORM beta.16 updates

We've fixed a regression in migrations introduced in beta.13 that persisted through beta.15, and used the opportunity to significantly improve the entire migration infrastructure going forward.

After receiving github issue, we focused on not just fixing the symptoms but rethinking how migrations are tracked, validated, and applied. As we always do with Drizzle we went deeper and redesigned the underlying architecture so it can be stable for all future changes, additions, and edge cases

We went through how we check migrations, how we store them, and how we help developers keep their migration flow reliable. After several iterations of rewriting the migrate function in both ORM and Kit, adding migration table versioning, and building a new commutativity check system: here's what changed and why.

What happened in beta.12–beta.15 and what caused the issue

On latest (pre-beta) versions, the migrations folder used a journal-based structure. A meta/_journal.json file stored a timestamp for each migration in milliseconds. That same millis value was stored in the database's created_at column and used to determine which migrations had been applied. Because the journal enforced ordering, we could simply fetch the last applied migration from the database and apply everything after it.

With the new v3 folder structure (introduced in beta), each migration lives in its own folder named <YYYYMMDDHHmmss>_<name>. This format only has second precision. The new structure also intentionally allows out-of-order migrations (as it should for team workflows), so we switched to reading all migrations from the database and comparing against all local migrations.

The problem appeared after drizzle-kit up converted the old journal structure to v3 folders. It mapped millis timestamps to the YYYYMMDDHHmmss_name format, stripping away the millisecond precision. So when the new migration checker compared what was in the database (millis) to what was on disk (seconds), nothing matched causing migrations to be re-applied on every run.

This only affected beta users who upgraded from the journal-based format. Users on latest were not impacted.

How we fixed it

... (truncated)

Commits

• See full diff in compare view

Updates sass from 1.97.3 to 1.98.0

Release notes

Sourced from sass's releases.

Dart Sass 1.98.0

To install Sass 1.98.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

Command-Line Interface

• Gracefully handle dependency loops in --watch mode.

Dart API

• Add a const Logger.defaultLogger field. This provides a logger that emits to standard error or the browser console, but automatically chooses whether to use terminal colors.

JavaScript API

• Fix a crash when manually constructing a SassCalculation for 'calc' with an argument that can't be simplified.

• Properly emit deprecation warnings as text rather than StringBuffer objects when running in a browser.

• Emit colored warnings and other messages on the console when running in a browser.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.98.0

Command-Line Interface

• Gracefully handle dependency loops in --watch mode.

Dart API

• Add a const Logger.defaultLogger field. This provides a logger that emits to standard error or the browser console, but automatically chooses whether to use terminal colors.

JavaScript API

• Fix a crash when manually constructing a SassCalculation for 'calc' with an argument that can't be simplified.

• Properly emit deprecation warnings as text rather than StringBuffer objects when running in a browser.

• Emit colored warnings and other messages on the console when running in a browser.

Commits

• 5a81ae3 Bump version to 1.98.0 (#2754)
• e25e71d Update immutable to v5.1.5 (#2753)
• 43fac1a Bump actions/upload-artifact from 6 to 7 (#2747)
• 8b85c9a Bump actions/download-artifact from 7 to 8 (#2749)
• 00f83f0 Bump postcss from 8.5.6 to 8.5.8 in /pkg/sass-parser (#2752)
• 0a325a4 Bump actions/attest-build-provenance from 3 to 4 (#2748)
• 7fb3c0f Gracefully handle dependency loops in watch mode (#2746)
• e86d044 Bump eslint from 9.39.3 to 10.0.1 in /pkg/sass-parser (#2743)
• 4bcd256 Add Logger.defaultLogger to automatically choose whether to use colors (#2742)
• c3f8ff0 Always convert printed objects to strings in JS (#2741)
• Additional commits viewable in compare view

Updates taze from 19.9.2 to 19.10.0

Release notes

Sourced from taze's releases.

v19.10.0

   🚀 Features

• Support packageManager with hex hash  -  by @​hyoban and @​antfu in antfu-collective/taze#234 (ea5ac)

   🐞 Bug Fixes

• Version resolution  -  by @​antfu (5a1d3)
• Prevent bun catalog write clobber on taze -w  -  by @​vcode-sh in antfu-collective/taze#238 (6bf61)

   🏎 Performance

• Optimize rendering time to resolve flickering issues during interaction with large data  -  by @​Emiyaaaaa and @​antfu in antfu-collective/taze#243 (0a8af)

    View changes on GitHub

Commits

• 75bdd8c chore: release v19.10.0
• 0a8afb9 perf: optimize rendering time to resolve flickering issues during interaction...
• 3f6cba2 chore: pnpm configurations moved together (#242)
• bc9f377 chore: update test
• 02ad8ce chore: update deps and lint
• ea5ac41 feat: support packageManager with hex hash (#234)
• 39a5d30 docs: add maturity-period to readme (#237)
• 80479b7 refactor: make recursive (monorepo) check in full parallel (#240)
• a53696d test: stable tests cross os (#241)
• 6bf613d fix: prevent bun catalog write clobber on taze -w (#238)
• Additional commits viewable in compare view

Updates valibot from 1.2.0 to 1.3.0

Release notes

Sourced from valibot's releases.

v1.3.0

Many thanks to @​EskiMojo14, @​yslpn, @​alexilyaev, @​idleberg, @​BerkliumBirb and @​frenzzy for contributing to this release.

Read the release notes on our website for a quick overview of the most exciting new features in this release.

• Add guard transformation action to narrow types using type predicates (pull request #1204)
• Add parseBoolean transformation action to parse boolean values from strings and other types (pull request #1251)
• Add isrc validation action to validate ISRC codes (pull request #1373)
• Add cache method for caching schema output by input (pull request #1170)
• Add domain validation action to validate domain names (pull request #1284)
• Add jwsCompact validation action to validate JWS compact strings (pull request #1348)
• Fix creditCard validation action to allow 13-digit Visa card numbers (pull request #1347)
• Fix isoTimestamp validation action to allow optional space before UTC offset for PostgreSQL timestamptz compatibility (pull request #1195)
• Fix types for deeply readonly default and fallback values

v1.3.0 (to-json-schema)

Many thanks to @​Xiot for contributing to this release.

• Add ignoreActions configuration to be able to ignore specific actions during conversion
• Add typeMode configuration to be able to control whether to convert input or output type of schema
• Add ConversionContext, OverrideSchemaContext, OverrideActionContext and OverrideRefContext to exports
• Change JSDoc comments to improve documentation
• Change build step to tsdown and Rolldown

Commits

• 3215908 Change npm publishing to new Trusted Publisher auth
• 80d5a18 Merge pull request #1424 from open-circle/valibot-v1.3
• 711f676 Bump version to 1.3.0 and update changelog for release
• d794895 Merge pull request #1306 from yslpn/fix-i18n-ko-migration-deprecate-kr
• e7d2260 Merge pull request #1348 from yslpn/feat-jwt-action
• d18bee8 Update changelog of i18n to our compact format
• dd39fc1 Update Korean translations to use .mjs and .mts extensions
• 660ca1c Merge branch 'main' into feat-jwt-action
• d541786 Streamline website docs for new jwtCompact action
• 66be243 Enhance docs for new jwtCompact action
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for valibot since your current version.

Updates vite from 8.0.0-beta.11 to 8.0.0

Release notes

Sourced from vite's releases.

create-vite@8.0.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.0.0

Please refer to CHANGELOG.md for details.

v8.0.0

Please refer to CHANGELOG.md for details.

v8.0.0-beta.18

Please refer to CHANGELOG.md for details.

v8.0.0-beta.17

Please refer to CHANGELOG.md for details.

v8.0.0-beta.16

Please refer to CHANGELOG.md for details.

v8.0.0-beta.15

Please refer to CHANGELOG.md for details.

v8.0.0-beta.14

Please refer to CHANGELOG.md for details.

v8.0.0-beta.13

Please refer to CHANGELOG.md for details.

v8.0.0-beta.12

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

8.0.0 (2026-03-12)

Today, we're thrilled to announce the release of the next Vite major:

• Vite 8.0 announcement blog post
• Docs (translations: 简体中文, 日本語, Español, Português, 한국어, Deutsch, فارسی)
• Migration Guide

⚠ BREAKING CHANGES

• remove import.meta.hot.accept resolution fallback (#21382)
• update default browser target (#21193)
• the epic rolldown-vite merge (#21189)

Features

• update rolldown to 1.0.0-rc.9 (#21813) (f05be0e)
• warn when vite-tsconfig-paths plugin is detected (#21781) (ada493e)
• css: support es2025 build target for lightningcss (#21769) (08906e7)
• forward browser console logs and errors to dev server terminal (#20916) (2540ed0)
• update rolldown to 1.0.0-rc.8 (#21790) (a0c950e)
• export Visitor and ESTree from rolldown/utils (#21664) (45de31e)
• update rolldown to 1.0.0-rc.6 (#21714) (37a65f8)
• use util.inspect for CLI error display (#21668) (5f425a9)
• update rolldown to 1.0.0-rc.5 (#21660) (b3ddbc5)
• update rolldown to 1.0.0-rc.4 (#21617) (1ee5c7f)
• wasm: add SSR support for .wasm?init (#21102) (216a3b5)
• integrate devtools (

[github-actions]

🎉 Deployed to Cloudflare!

• Commit: 59ff18d35b8c7e3b9e80104f30cedde92decb934
• Preview URL: https://08ea2d0e-perd-staging.perd.workers.dev

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.