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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
.webpack
webpack config file where module.exports is a function doesn't work depending on the file path.
module.exports
If the config file path contains .webpack, the result of calling the config function is ignored.
Steps to reproduce the behavior:
// project/config.webpack.js -- note that filename contains ".webpack" module.exports = (env) => ({ entry: 'some-file.js' output: { path: './dist', file: 'some-bundle.js' } });
$/project> webpack --config config.webpack.js
This produces an error saying "./src cannot be resolved" because the actual config is ignored, and webpack falls back to default configuration.
./src
** Cause **
lib/groups/ConfigGroup.js in the finalize function:
lib/groups/ConfigGroup.js
finalize
if (configOptions && configPath.includes('.webpack')) { // overrides the resolved options }
this condition is not specific enough.
The text was updated successfully, but these errors were encountered:
Please do not ignore the issue template, in future it will be closed without reply
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
webpack config file where
module.exports
is a function doesn't work depending on the file path.If the config file path contains
.webpack
, the result of calling the config function is ignored.Steps to reproduce the behavior:
This produces an error saying "
./src
cannot be resolved" because the actual config is ignored, and webpack falls back to default configuration.** Cause **
lib/groups/ConfigGroup.js
in thefinalize
function:this condition is not specific enough.
The text was updated successfully, but these errors were encountered: