Compatibility with @vite/plugin-legacy

[vilbergs]

Hello!

I've had fantastic success using this plugin so far, thanks for making our migration to Vite a breeze.

I've been trying to get @vite/plugin-legacy to work alongside this plugin, but the automatic code injection does not seem to take effect, I'm assuming that is for similar reasons that the legacy plugin does not work with the lib entry options in the Vite config (see vitejs/vite#1639).

So far I've gotten Safari 11 to work by manually including the "polyfills" chunk generated by the build, but in order to support Edge 18 I believe I need the runtime check for dynamic import support to run.

Any help towards a solution would be deeply appreciated, if this plugin uses the lib option for entry points I assume we'll just have to hope that vitejs/vite#1639 gets solved, but until then I'll explore workarounds.

[driesvints]

Right now, we don't aim to be compatible with this library, sorry.

[tbruckmaier]

For reference, @kitro suggested a workaround here: laravel/framework#42785 (comment)

[brandonburkett]

Is this still true that the vite-plugin will not be compatible with the legacy plugin? Seems weird to not support older browsers out of the box.

[kyselberg]

hi!
could you tell if there are any updates on plans?