feat: align with @vitejs/plugin-legacy 5.3.2

[ModyQyW]

closes #7

• chore(deps): update all non-major dependencies
• fix(plugin-legacy): dynamic import browserslist-to-esbuild
• fix(plugin-legacy): replace esbuild-plugin-browserslist with browserslist-to-esbuild
• fix(plugin-legacy): respect modernTargets option if renderLegacyChunks disabled
• feat(plugin-legacy): add modernTargets option

[ModyQyW]

modernTargets defaults to edge>=79, firefox>=67, chrome>=64, safari>=12, chromeAndroid>=64, iOS>=12, which is different with @vitejs/plugin-legacy (edge>=80, firefox>=72, chrome>=80, safari>=13.1, chromeAndroid>=80, iOS>=13.1).

The reason is listed in the code before: However, since esbuild only transform syntax rather than polyfill, the output is not guaranteed to support es2020. So this feature cannot be used as a basis for compatibility.. Should I sync this?

[CyanSalt]

Thx for your contribution! I noticed that vitejs/vite#15789 has been merged. Can you synchronize the changes to this PR? I think it might be important.

[CyanSalt]

Sorry I just noticed it's actually included. LGTM!

[CyanSalt]

modernTargets defaults to edge>=79, firefox>=67, chrome>=64, safari>=12, chromeAndroid>=64, iOS>=12, which is different with @vitejs/plugin-legacy (edge>=80, firefox>=72, chrome>=80, safari>=13.1, chromeAndroid>=80, iOS>=13.1).

The reason is listed in the code before: However, since esbuild only transform syntax rather than polyfill, the output is not guaranteed to support es2020. So this feature cannot be used as a basis for compatibility.. Should I sync this?

I think there should be some inconsistency here. This behavior can ensure that the generated code is always correctly polyfilled, otherwise there may be some methods that are incompatible with browsers in the gap, which had occurred in my project with millions of users. Although I'm not sure if there is any difference in syntax conversion between babel and swc.

[ModyQyW]

modernTargets defaults to edge>=79, firefox>=67, chrome>=64, safari>=12, chromeAndroid>=64, iOS>=12, which is different with @vitejs/plugin-legacy (edge>=80, firefox>=72, chrome>=80, safari>=13.1, chromeAndroid>=80, iOS>=13.1).
The reason is listed in the code before: However, since esbuild only transform syntax rather than polyfill, the output is not guaranteed to support es2020. So this feature cannot be used as a basis for compatibility.. Should I sync this?

I think there should be some inconsistency here. This behavior can ensure that the generated code is always correctly polyfilled, otherwise there may be some methods that are incompatible with browsers in the gap, which had occurred in my project with millions of users. Although I'm not sure if there is any difference in syntax conversion between babel and swc.

I think we can just keep it.

[ModyQyW]

vitejs/vite@4af9f97

For new comers, now the modernTargets default value is the same as @vitejs/plugin-legacy.