Could not resolve entry module "index.html".

[artuska]

Describe the bug

Vite kepp trying to resolve an index.html as build entry point though i have set another entry point in Rollup input config:

build: {
  outDir: "./.next/static",
  emptyOutDir: false,
  copyPublicDir: false,
  assetsDir: "microfrontends",
  assetsInlineLimit: 0,
  minify: true,
  modulePreload: false,
  target: "esnext",
  rollupOptions: {
    external: [
      "/apps/iplatform-client-header/remoteEntry.js",
      "/apps/iplatform-client-footer/remoteEntry.js",
    ],
    input: {
      microfrontends: fileURLToPath(
        new URL("./src/microfrontends.html", import.meta.url),
      ),
    },
    output: {
      entryFileNames: "[name].js",
    },
  },
},

Reproduction

https://oh-cmon-of-course-i-dont-have-time-to-make-a-reproduction-just-use-your-own-test-environment-and-look-at-your-code.com

Steps to reproduce

No response

System Info

System:
  OS: Linux 5.15.131-1.el7.3.x86_64
Binaries:
  Node: 20.18.1
  npm: 10.8.2
Browsers:
  Edge: Chromium (127.0.2651.74)
  Internet Explorer: 11.0.19041.4355
npmPackages:
  @vitejs/plugin-react: 4.3.4 => 4.3.4
  vite: 5.4.14 => 5.4.14, also tried with 5.4.11

Used Package Manager

npm

Logs

Click to expand!

#16 55.34 vite v5.4.14 building for production...
#16 55.39 ✓ 0 modules transformed.
#16 55.39 x Build failed in 12ms
#16 55.39 error during build:
#16 55.39 Could not resolve entry module "index.html".
#16 55.39     at getRollupError (file:///opt/node_modules/rollup/dist/es/shared/parseAst.js:397:41)
#16 55.39     at error (file:///opt/node_modules/rollup/dist/es/shared/parseAst.js:393:42)
#16 55.39     at ModuleLoader.loadEntryModule (file:///opt/node_modules/rollup/dist/es/shared/node-entry.js:21141:20)
#16 55.39     at async Promise.all (index 0)

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.