Sourced from @​nuxt/vite-builder's releases.

v3.15.4

3.15.4 is the next patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest upgrade --force

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

• nuxt: Improve error logging when parsing with acorn (#30754)
• nuxt: Clear island uid before saving into the payload (#30767)
• kit: Load @nuxt/schema from nuxt package dir (#30774)
• nuxt: Allow restarting nuxt on paths outside srcDir (#30771)
• nuxt: Don't warn about calling useRoute in SFC setup (#30788)
• webpack: Disallow cross-site requests in no-cors mode (#30757)
• vite: Restore externality for dev server externals (#30802)

💅 Refactors

• vite: Use new rollup chunk.names for asset names (#30780)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Peter Radko (@​Gwynerva)
• Lansi (@​lansi951)
• Julien Huang (@​huang-julien)
• Norbiros (@​Norbiros)

v3.15.3

3.15.3 is the next regularly scheduled patch release.

👀 Highlights

CORS configuration for dev server

Alongside a range of improvements, we've also shipped a significant fix to impose CORS origin restrictions on the dev server. This applies to your Vite or Webpack/Rspack dev middleware only.

This is a significant/breaking change we would not normally ship in a patch but it is a security fix (see GHSA-4gf7-ff8x-hq99 and GHSA-2452-6xj8-jh47) and we urge you to update ASAP.

You can configure the allowed origins and other CORS options via the devServer.cors options in your nuxt.config, which may be relevant if you are developing with a custom hostname:

export default defineNuxtConfig({
</tr></table> 

... (truncated)

• 244da17 v3.15.4
• 56d889e fix(vite): restore externality for dev server externals (#30802)
• 325ed41 refactor(vite): use new rollup chunk.names for asset names (#30780)
• 940bcb8 chore(deps): update all non-major dependencies (3.x) (#30747)
• 048f974 v3.15.3
• c6056bd chore(deps): update all non-major dependencies (3.x) (#30733)
• 406db5b fix(vite,webpack): restrict access via cors to local origins + allow configur...
• 09d8db5 chore(deps): update vitest to v3.0.4 (3.x) (#30724)
• 10a5495 fix(vite): inline shared folder in dev mode (#30690)
• f1c2948 chore(deps): update all non-major dependencies (3.x) (#30694)
• Additional commits viewable in compare view

Sourced from nuxt's releases.

v3.15.4

3.15.4 is the next patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest upgrade --force

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

• nuxt: Improve error logging when parsing with acorn (#30754)
• nuxt: Clear island uid before saving into the payload (#30767)
• kit: Load @nuxt/schema from nuxt package dir (#30774)
• nuxt: Allow restarting nuxt on paths outside srcDir (#30771)
• nuxt: Don't warn about calling useRoute in SFC setup (#30788)
• webpack: Disallow cross-site requests in no-cors mode (#30757)
• vite: Restore externality for dev server externals (#30802)

💅 Refactors

• vite: Use new rollup chunk.names for asset names (#30780)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Peter Radko (@​Gwynerva)
• Lansi (@​lansi951)
• Julien Huang (@​huang-julien)
• Norbiros (@​Norbiros)

v3.15.3

3.15.3 is the next regularly scheduled patch release.

👀 Highlights

CORS configuration for dev server

Alongside a range of improvements, we've also shipped a significant fix to impose CORS origin restrictions on the dev server. This applies to your Vite or Webpack/Rspack dev middleware only.

This is a significant/breaking change we would not normally ship in a patch but it is a security fix (see GHSA-4gf7-ff8x-hq99 and GHSA-2452-6xj8-jh47) and we urge you to update ASAP.

You can configure the allowed origins and other CORS options via the devServer.cors options in your nuxt.config, which may be relevant if you are developing with a custom hostname:

export default defineNuxtConfig({
</tr></table> 

... (truncated)

• 244da17 v3.15.4
• ceaf0f5 chore(deps): update all non-major dependencies (3.x) (#30804)
• 626eba0 fix(nuxt): don't warn about calling useRoute in SFC setup (#30788)
• 7a1e5c8 fix(nuxt): allow restarting nuxt on paths outside srcDir (#30771)
• ca2d91f fix(kit): load @nuxt/schema from nuxt package dir (#30774)
• b78da56 fix(nuxt): clear island uid before saving into the payload (#30767)
• e0c47f9 fix(nuxt): improve error logging when parsing with acorn (#30754)
• 940bcb8 chore(deps): update all non-major dependencies (3.x) (#30747)
• 048f974 v3.15.3
• e96a96d perf(nuxt): enable Transition component only on client side (#30720)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.