The console displays:

 WARN  nuxt-vite-legacy didn't find legacy-polyfills-legacy chunk. Legacy build will not work. 

But I only use vite-plugin-legacy to generate modern polyfills in my project with renderLegacyChunks: false in config. The plugin should still mutate the reference in the manifest instead of aborting.

Does your module works with static generation websites?

Because we just try it with a demo of ours and the generated html in public folder didn't change at all.

Than you

We need to re-export @vitejs/plugin-legacy options type instead of copy-pasting it, as this is not only sub-optional but simply wrong. Users having @vitejs/[email protected] have false expectation that they can use renderModernChunks.

Unfortunately, this requires implementation at upstream: vitejs/vite#14931

Hi there,

I've been trying to use your plugin for my personal project, as it is necessary for my Nuxt 3 app to work under Chrome 49. I downloaded Chromium version 49 (Version 49.0.2623.23 (64-bit)) for this purpose. I attempted to launch the playground in the repository using this version, but the JavaScript files are not loading. This issue occurs both in dev mode and build mode. Any insights into what might be causing this problem?

Thanks!

Chromium 49:

Current Chrome:

Hi there,

I've been trying to use your plugin for project created by vitesse-nuxt3. I generated the static web site and hosted it with http-server. It doesn't work on chrome 60 while it's ok above chrome66. Any insights into what might be causing this problem? Below is my nuxt.config:

modules: [
    '@vueuse/nuxt',
    '@unocss/nuxt',
    '@pinia/nuxt',
    '@nuxtjs/color-mode',
    'nuxt-module-eslint-config',
    'nuxt-vite-legacy'
  ],
  legacy: {
    targets: ["chrome 49"],
    additionalLegacyPolyfills: [
      "mdn-polyfills/Element.prototype.getAttributeNames",
    ],
    modernPolyfills: [
      'es.global-this',
      'es/object',
      'es/array',
      'es.symbol',
      'es.array.filter',
      'es.promise',
      'es.promise.finally',
      'es/map',
      'es/set',
      'es.array.from',
      'es.array.for-each',
      'es.object.define-properties',
      'es.object.define-property',
      'es.object.get-own-property-descriptor',
      'es.object.get-own-property-descriptors',
      'es.object.keys',
      'es.object.to-string',
      'web.dom-collections.for-each',
      'esnext.global-this',
      'esnext.string.match-all',
      'es.object.define-setter',
      'es.array.iterator',
      'es.object.assign',
      'es.array.includes'
    ],
  },

Thanks!

Following your steps, the entry.legacy.js can be removed successfully, but I don’t know why there is