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

document array export from config file #69

Closed
Rich-Harris opened this issue Jun 3, 2017 · 4 comments
Closed

document array export from config file #69

Rich-Harris opened this issue Jun 3, 2017 · 4 comments

Comments

@Rich-Harris
Copy link
Contributor

As of 0.42, config files can export an array, and all the builds will happen in parallel. This also works with watch mode

@nathancahill
Copy link

Important to note in the docs that each config object in the array must have its own instance of any plugins used. Sharing plugin instances across configs will cause unexpected behavior.

@ghost
Copy link

ghost commented Jun 4, 2017

Sharing plugin instances across configs will cause unexpected behavior.

Could this be expanded upon just a little? I haven't seen any unexpected behavior with minify or license under basic use, though I'm only using them with a single import from within just one config file (pre- and post-0.42 release) to roll 6 bundles.

@nathancahill
Copy link

Some plugins might work, others might not. I think rollup-plugin-uglify with it's custom output options was where I noticed the issue. When a plugin reads from the Rollup config object, it will overwrite that value until the last config in the array.

@ghost
Copy link

ghost commented Jun 5, 2017

Thanks for expanding. I'm using the new array syntax to output bundles and using uglifiy with harmony. Looks good to me. Not sure if our set-ups differ, but I'm using the technique left in your PR to create the minis. Was very pleased by being able to remove a dev dependency with that pull. 💯

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

2 participants