💡 RFC: Pass target option tgo esbuild transform call

[melink14]

Motivation

Simplification of the build pipeline by not requiring esbuild optimization after esbuild transformation in order to target something other than esnext

Proposed solution

Possible solutions

esbuild transform already takes target so passing it is easy enough. It's currently only surfaced in optimize section of config but it seems like it would fit well into buildOptions as well.

Risks, downsides, and/or tradeoffs

Having target in two places might be confusing since it doens't make too much sense to have them differ.

Detailed design

No response

Open questions

No response

Help make it happen!

• I am willing to submit a PR to implement this change.
• I am willing to submit a PR to implement this change, but would need some guidance.
• I am not willing to submit a PR to implement this change.

[drwpow]

We are already considering this! This will be a part of our planned Snowpack v4 work, hinted at by the “multi-platform targeting.” This is a major (breaking) change, so we can’t ship something easily in 3.x with one PR.

I’m going to close this issue as it’s already planned/captured elsewhere, but TL;DR we agree 🙂