Legacy build ignores custom filenames

[pedrodim]

Describe the bug

When using custom output's filenames the legacy build ignores the format and keeps its own format.

The formats are hardcoded on legacy plugin: [name]-legacy.[hash].js and [name]-legacy.[hash].js.

Reproduction

import legacy from '@vitejs/plugin-legacy'

export default defineConfig({
  plugins: [legacy()],
  build: {
    rollupOptions: {
      output: {
        entryFileNames: `[name].js`,
        chunkFileNames: `[name].js`,
        assetFileNames: `[name].[ext]`
      }
    }
  }
})

System Info

• vite version: 2.0.4
• Operating System: macOS Big Sur
• Node version: 12.21.0
• Package manager (npm/yarn/pnpm) and version: npm 6.14.11

[wxxcarl]

but when i config output.chunkFileNames width a function, it throw an error:

@vitejs/plugin-legacy rollupOptions.output.entryFileNames and rollupOptions.output.chunkFileNames does not support the function format.

For some reason，i must custom chunkFileNames， how can i do

[github-actions]

This issue has been locked since it has been closed for more than 14 days.

If you have found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Vite version. If you have any other comments you should join the chat at Vite Land or create a new discussion.