-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Supporting custom webpack.config.js #16
Comments
Sure. Let's do it. Do you want to make PR? Also, why custom config should not include compression and minification plugins? What if users will want to customize them too? |
Totally possible. I was assuming that the |
|
Got it. What I'm trying to figure out is the best way to (or if it's feasible) to implement the following:
In other words: what's an efficient way to check if |
I think we could ignore this problem. If you pass custom config, it is your responsibility now. If we will have a lot of issues, we can add check later. |
That's reasonable. Will take a stab at this in the next couple of weeks. |
@indexzero @ai I have submitted #29, and #31 to enable a |
Released in 0.12 |
@SivanMehta I'm wondering, how are you using this --config option? How do you handle the Lines 32 to 49 in 2286080
|
This PR should have supported the usage as described in the initial issue descriptions
|
Interested in using your project, but the projects in which we would be using it do not build using the webpack config included in
index.js
.Would you be interested in a PR that allows for a custom webpack config file path to be provided?
e.g.
The
webpack.config.js
file would be expected to:webpack
config object... thoughts?
The text was updated successfully, but these errors were encountered: