# Important notice for Vite users in newly generated apps

**URL:** <https://discourse.aurelia.io/t/important-notice-for-vite-users-in-newly-generated-apps/6482>\
**Category:** vNext\
**Created:** [July 14, 2025, 9:50am UTC](https://discourse.aurelia.io/t/important-notice-for-vite-users-in-newly-generated-apps/6482 "2025-07-14T09:50:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwaynecharrington](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/dwaynecharrington/32/11_2.png) [@dwaynecharrington](https://discourse.aurelia.io/u/dwaynecharrington)\
**Post date:** [July 14, 2025, 9:50am UTC](https://discourse.aurelia.io/t/important-notice-for-vite-users-in-newly-generated-apps/6482/1 "2025-07-14T09:50:48Z")

</div>

In the latest beta 25 release we upgrade Vite to version 7, however, downstream in Rollup (which Vite uses) a bug was introduced which will break apps when you try running `npm run build` - the bug is detailed here and appears it will be fixed momentarily: [bug from 4.45.0: Cannot add property 0, object is not extensible · Issue #6012 · rollup/rollup · GitHub](https://github.com/rollup/rollup/issues/6012) - but at the time of writing this (and hopefully for not much longer) the issue will appear in new Vite based apps generated using `npx makes aurelia` and if you upgrade any existing Vite apps to the latest beta 25 release.

The fix in the aforementioned link advises pinning the version of Rollup to a version that isn’t broken in your `package.json` file:

```auto
  "resolutions": {
    "rollup": "4.44.0"
  }

```

I have confirmed this fixes the issue.