plugin-legacy: polyfills chunk should respect output.entryFileNames option

[portfolioris]

Clear and concise description of the problem

As a developer I want to disable hashing of filenames, so I can always reference the same polyfill file.

Suggested solution

I would be nice if the plugin-legacy would follow the build.rollupOptions.output.entryFileNames option. In my case, I would like to add <script nomodule src="dist/assets/polyfills-legacy.js"></script> to my HTML.

I guess it would involve adding entryFileNames: buildOptions.rollupOptions.output.entryFileNames, to the output config of buildPolyfillChunk().

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[hsuna]

Waiting for repair!

[keith0305]

Hey, I have the same issue. I managed to remove all hashes in the output, except for polyfills-legacy js.

[vamsidotdev]

Same issue for me. Has anyone found a workaround for this?

[freesou2]

same issue for me

[jheng-jie]

temporary plan

• node_modules/@vitejs/plugin-legacy/index.js

• find async function buildPolyfillChunk

const res = await build({
  build: {
    rollupOptions: {
      output: {
        entryFileNames: "[name].js",
      }
    }
  }
})

waiting for repair!