You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v2.6.1 default build.minify to esbuild(e4892be),
all configurations that do not set build.minify BUT use plugin-legacy will receive an Can't use esbuild as the minifier when targeting legacy browsers because esbuild minification is not legacy safe error.
The solution is simple. Just set build.minify to terser.
But is this a best practice? How about the default is esbuild and the legacy part uses terser?
I don't know the result because the current plugin-legacy doesn't support configuring the minifier separately.
I think the relevant documents and options can be better done, to guide users to use the best configuration with plugin-legacy
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Since
v2.6.1
defaultbuild.minify
to esbuild(e4892be),all configurations that do not set
build.minify
BUT useplugin-legacy
will receive anCan't use esbuild as the minifier when targeting legacy browsers because esbuild minification is not legacy safe
error.The solution is simple. Just set
build.minify
to terser.But is this a best practice? How about the default is esbuild and the legacy part uses terser?
I don't know the result because the current
plugin-legacy
doesn't support configuring the minifier separately.I think the relevant documents and options can be better done, to guide users to use the best configuration with
plugin-legacy
Beta Was this translation helpful? Give feedback.
All reactions