We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Improve the experience of using webpack-blocks as shared by @zcei: see comment
core
createConfig()
dev-server
HotModuleReplacementPlugin
--hot
extract-text
The text was updated successfully, but these errors were encountered:
Hej, I thought it might be cool to provide the actual configuration output of each block in its README, like this for babel:
babel
{ module: { rules: [{ test: context.match.test, // /\.(js|jsx)$/ exclude: context.match.exclude, // /node_modules/ use: [{ loader: 'babel-loader', options: { cacheDirectory: options.cacheDirectory // true } }] }] } }
I think this would make it easier to grasp when coming from a "pure" webpack background. What do you think?
(I would volunteer running each block once and adjusting the output to the style above & filing a PR)
Sorry, something went wrong.
Good idea! I am just not sure whether to provide the test: context.match.test stuff or the actual output for some example input.
test: context.match.test
No branches or pull requests
Improve the experience of using webpack-blocks as shared by @zcei: see comment
core
: More useful output forcreateConfig()
block assertiondev-server
: Document that it adds theHotModuleReplacementPlugin
; maybe don't add it at all if--hot
is found in the arguments (see Error with hot reloading and "-d": "SyntaxError: missing ) after argument list" webpack-contrib/style-loader#18)extract-text
: Investigate if re-using a plugin instance for multiple matches with the same file type test makes senseThe text was updated successfully, but these errors were encountered: