Consider setting `target' to es2022 in development to make inspecting private fields easier

[tomtiao]

When targeting es2020 in swc, private fields are transformed to WeakMap, and operations on them are converted to _class_apply_descriptor_get and _class_apply_descriptor_set functions, as can be seen here, making it hard to inspect private fields in the debugger.

Is it possible to default target to es2022 or make target configurable?

[ArnaudBarre]

For now I've set this to something lower to allow people to use new feature while testing on Safari that be could not have implemented all features (less and less true actually)
I would like to avoid an option for this. Ideally we should have an option of "dev target" in Vite. WDYT @patak-dev @bluwy @sapphi-red ?

[bluwy]

Currently in Vite with esbuild, dev always processes jsx/ts files with esnext, unless the user change it via the esbuild.target. If we want to align the plugin with Vite core, we'd have to expose a target option in this plugin.

BUT there are callouts that this is confusing in vitejs/vite#13756, so a dev target could make sense, but I'm not sure how it'll look like holistically if we also consider prebundling target, tsconfig target, etc.

[ArnaudBarre]

An option is available in the latest version!