Andy Wermke
Andy Wermke
Good idea! I am just not sure whether to provide the `test: context.match.test` stuff or the actual output for some example input.
@trajedy Thanks for the feedback! Yes, documentation is still an issue... If you have a suggestion how to improve the docs, feel free to open a PR. Help is always...
Thanks for sharing, @zcei! I created a new issue (#171) for that. Your feedback is very valuable and shall be addressed. It would be really cool if you could suggest...
Thanks for reporting, Adam. Can you please share the stack trace with us?
Hi @niieani! No, I was not aware of `easy-webpack`, but thanks for the link. I guess the most difficult thing to achieve when building such a specific utility like `easy-webpack`,...
Thanks for starting work on this, @zcei! Will have a deeper look into it :)
We need to discuss terminology here, since most terms haven't ever been clearly defined. Current state of affairs is: > Initially I was thinking that a `block` is a self-contained,...
Another term that might be discussable is `WebpackBlockUpdater`. Maybe it's rather a `WebpackConfigUpdater`: It's actually so generic that it's not webpack-blocks-specific. And this name might transport more information. Objections?
Update: Let's better discuss this in the issue (#246) than in the PR.
@stevenjlho Not sure what you mean. Writing presets is already possible, just did not write any yet. @sapegin True! Edited it :)