You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG]: [email protected] no longer supports function-export-based webpack.config.js #1126
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?
changed the title [-][email protected] no longer supports function-export-based webpack.config.js[/-][+][BUG]: [email protected] no longer supports function-export-based webpack.config.js[/+]on Nov 22, 2019
Activity
wood1986 commentedon Nov 21, 2019
Add @TheLarkInn
TheLarkInn commentedon Nov 21, 2019
cc @evenstensberg this is considered a release-blocking bug.
evenstensberg commentedon Nov 22, 2019
Considered!
evenstensberg commentedon Nov 22, 2019
Thx for your bug report @wood1986 , appreciate you putting in the time ❤️
[-][email protected] no longer supports function-export-based webpack.config.js[/-][+][BUG]: [email protected] no longer supports function-export-based webpack.config.js[/+]wood1986 commentedon Nov 23, 2019
I have one more request. webpack-cli 3 has a private function
webpack-cli/bin/cli.js
Line 125 in f9f0860
evenstensberg commentedon Nov 25, 2019
I think that the edit needs to be done here:
https://github.com/webpack/webpack-cli/blob/next/lib/groups/config.js#L86-L88
anikethsaha commentedon Nov 27, 2019
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
ematipico commentedon Feb 29, 2020
Is it fixed with latest beta?
alexander-akait commentedon Aug 1, 2020
/cc @anshumanv fixed by #1721? Can you include it in the PR message?
anshumanv commentedon Aug 1, 2020
Done @evilebottnawi 👍