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
How do we deal with ES6+ only distributions effectively?
From a problem statement, it is essentially an end user should be able to build an optimized build that targets a "modern browser" and effectively elides unnecessary code while still maintain the same API so the user does not have to rewrite their code. We should also provide them with the appropriate tooling to be able to also provide code that can be elided when targeting a "modern browser". We may also want to include a pre-built "modern" version in our distributions to make it easy for someone to grab-and-go.
There are at least three keys to this puzzle:
We need a better understanding of how we are going to elide code with the has API.
We are delivering build optimization in dojo/cli-build-webpack#172, there isn't much more that is actionable from this at the moment. It gives effective eliding of built in functionality at build time.
Broken off from #18.
How do we deal with ES6+ only distributions effectively?
From a problem statement, it is essentially an end user should be able to build an optimized build that targets a "modern browser" and effectively elides unnecessary code while still maintain the same API so the user does not have to rewrite their code. We should also provide them with the appropriate tooling to be able to also provide code that can be elided when targeting a "modern browser". We may also want to include a pre-built "modern" version in our distributions to make it easy for someone to grab-and-go.
There are at least three keys to this puzzle:
has
API.Are there any other thoughts/considerations/etc?
The text was updated successfully, but these errors were encountered: