fix(ssr): dont replace rollup input

[manucorporat]

Description

Setting custom input in rollupConfig always replaces, even the ssr entry points.

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[ydcjeff]

Can you describe more about why this change is required?

[manucorporat]

Basically, the --ssr my.ssr.entry.tsx is not used at all if a rollupConfig input is specified.

export default defineConfig(({ mode }) => {
  return {
    build: {
      rollupOptions: {
        input: ['src/main.tsx', 'index.html'],

Notice that we already generate the final input, using rollupConfig when necessarily...
https://github.com/vitejs/vite/pull/7275/files#diff-aa53520bfd53e6c24220c44494457cc66370fd2bee513c15f9be7eb537a363e7R381-R385

But this value is override and never used because this line:
https://github.com/vitejs/vite/pull/7275/files#diff-aa53520bfd53e6c24220c44494457cc66370fd2bee513c15f9be7eb537a363e7R432

replaces it.

[ydcjeff]

I see. For your example, which input do you expect to pass to the rollup since it now has ssr entry and rollupOptions.input?

[manucorporat]

I would expect to use the one I passed in --ssr

[manucorporat]

Any updates?

[patak-dev]

Sorry @manucorporat, I missed this one til now

[SteveDesmond-ca]

Per #9086, it seems this may have gone a little too broad. Any thoughts on how to rein it back in a bit? Or is my use case now officially unsupported?