Skip to content
This repository has been archived by the owner on Feb 7, 2022. It is now read-only.

[Webpack 2] Using --optimize-minimize argument with parallel-webpack #40

Closed
softvar opened this issue May 30, 2017 · 3 comments
Closed

Comments

@softvar
Copy link

softvar commented May 30, 2017

I tried but failed to minimize my files

parallel-webpack -p=1 --optimize-minimize --progress --colors --watch -- --env.mode=build

&

parallel-webpack -p=1 --progress --colors --watch -- --optimize-minimize --env.mode=build

Any solution?

@softvar softvar changed the title Using --optimize-minimize argument with parallel-webpack [Webpack 2] Using --optimize-minimize argument with parallel-webpack May 30, 2017
@pago
Copy link
Contributor

pago commented Jun 9, 2017

We don't support most of the webpack related CLI arguments. You need to configure optimization as part of your webpack.config.js.

If we add support for some, we'd need to support all of them and would also have to ensure compatibility. For now we don't intend to support this option.

P.S.: Sorry for the delay, I was on vacation.

@pago pago closed this as completed Jun 9, 2017
@carlescs
Copy link

carlescs commented Jul 6, 2017

As a crazy idea, would it be possible to add a generic parameter that added its values as parameters to webpack? Like this:

parallel-webpack -w "--optimize-minimize --progress --colors --watch -- --env.mode=build"

@pago
Copy link
Contributor

pago commented Jul 6, 2017

We're not actually calling the CLI interface but rather just use the programmatic API instead so we'd still need to parse and transform those options.

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

No branches or pull requests

3 participants