-
-
Notifications
You must be signed in to change notification settings - Fork 601
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
[BUG]: [email protected] no longer supports function-export-based webpack.config.js #1126
Comments
Add @TheLarkInn |
cc @evenstensberg this is considered a release-blocking bug. |
Considered! |
Thx for your bug report @wood1986 , appreciate you putting in the time ❤️ |
I have one more request. webpack-cli 3 has a private function Line 125 in f9f0860
|
I think that the edit needs to be done here: https://github.com/webpack/webpack-cli/blob/next/lib/groups/config.js#L86-L88 |
Not sure why this bug is happening but the tests seems fine and passing for config type function https://github.com/webpack/webpack-cli/tree/next/test/config/type/function |
Is it fixed with latest beta? |
/cc @anshumanv fixed by #1721? Can you include it in the PR message? |
Done @evilebottnawi 👍 |
Describe the bug
When my webpack.config.js is exporting a function instead of a simple object. Webpack won't recognize my config anymore. I have checked your test case on your next branch and I do not see any webpack.config.js which is exporting a function. When I export an object, it works Are you work in progress? Or Will you deprecate that kind of export?
What is the current behavior?
See the previous
To Reproduce
use this webpack.config.js
and then run
Expected behavior
/
Screenshots
/
Please paste the results of
webpack-cli info
here, and mention other relevant informationwebpack: next
webpack-cli: 4.0.0-beta.1
node: 13.1.0
OS: macOS 10.15.1
Additional context
/
The text was updated successfully, but these errors were encountered: