Describe the bug

Per https://vite.dev/config/build-options#build-rollupoptions :

This option is an alias of build.rolldownOptions option. Use build.rolldownOptions option instead.

I don't use Vite much, but I did know that I was supposed to be using rolldownOptions. So it was rather confusing when I encountered an error referring to an options field that I explicitly had made sure not to use:

Failed to run dependency scan. Skipping dependency pre-bundling. Error: failed to resolve rollupOptions.input value: "./dawn-mazurka/index.html".

(The error itself is confusing, because it has the same symptom as #20377 — failure on first run, then success on subsequent runs — but that's marked as resolved. Not sure if I should file a new issue.)

The source of the error is:

I went to draft a PR to fix this, but the codebase still refers to rollupOptions in a lot of places, even though the documentation and the actual field in the code are marked as deprecated. It feels like a targeted field would cause surprises, so this might best be left to a wider replacement of the deprecated field name throughout the project where possible.

Reproduction

https://github.com/lgarron/choreo-apps

Steps to reproduce

Non-deterministic:

git clone https://github.com/lgarron/choreo-apps && cd ./choreo-apps/
git switch --detach cc0c6a897a548564e3a40d338663946fb18d6879

# Requires `bun`
make setup
make build

System Info

I don't feel comfortable running `npx envinfo`, given I've never heard of it.

None of the packages in the glob `{vite,@vitejs/*,rollup,rolldown}` are installed globally, and the [pinned deps](https://github.com/lgarron/choreo-apps/blob/cc0c6a897a548564e3a40d338663946fb18d6879/bun.lock) are `vite@8.0.10` and (transitively) `rolldown@1.0.0-rc.17`. Not that any of this seems germane to the issue.

I'm on macOS 26.4.1.

Used Package Manager

bun

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.