Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expanding input's array- and object-form beyond experimentalCodeSplitting? #2227

Closed
maranomynet opened this issue May 28, 2018 · 4 comments
Closed

Comments

@maranomynet
Copy link
Contributor

maranomynet commented May 28, 2018

experimentalCodeSplitting introduces a relatively coherent mechanism for specifying multiple entry points and output bundle mapping, via input in array-form and object-form.

It seems like expanding those mechanisms to work beyond experimentalCodeSplitting would be the logical next step.

...or what?

@lukastaegert
Copy link
Member

Non-experimentalising this is currently a top-priority. At the moment, especially @guybedford is working on updating the plugin hooks and some internal code paths. It should be finished soon, ideally with a 1.0.0 release :)

#2208 is the most important task here at the moment.

@guybedford
Copy link
Contributor

The current 0.60 release is moving towards enabling --experimentalCodeSplitting by default by enabling the flag for single-file builds as well. Further feedback very welcome before this gets unflagged.

@diegohaz
Copy link

diegohaz commented Aug 2, 2018

via input in array-form and object-form

Is it possible to pass an object to input?

@lukastaegert
Copy link
Member

Yes it is. Information can be found here: #2068
The docs still need updating, though. Any help is appreciated here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants