plugin-legacy misunderstand

[rodriciru]

Hi.
As far as I know, plugin-legacy is to add compatibility with older browsers that don't understand import.meta, dynamic import, async generators.

OK. Now I want to add support for ||= which is included in Firefox >=69.
So, I want the main build to have ||= and the legacy build to have the pollyfied version of that.
Now I open Firefox 68 and because it passes all test for modern build, it will load the main build and fail because it don't understand ||=
Can this be accomplished?

[sapphi-red]

||= is supported by Firefox 79+, not 69+.

So, I want the main build to have ||= and the legacy build to have the pollyfied version of that.

This is impossible currently. #6922 needs to be implemented to control the threshold.

Now I open Firefox 68 and because it passes all test for modern build, it will load the main build and fail because it don't understand ||=

I guess you set modernTargets. That should output a warning that some browsers wouldn't work (plugin-legacy 'modernTargets' option overrode the builtin targets of modern chunks. Some versions of browsers between legacy and modern may not be supported.).

[rodriciru]

Firefox 69 was a typo, sorry.

OK. Will wait to it. Thanks!