Issue 1:
Bug report

What is the current behavior?

"build": "NODE_ENV=production webpack -p --config webpack.config.prod.js"

vendors~app.1119d1fb9353e3bd9353.js:77 Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at xu (vendors~app.1119d1fb9353e3bd9353.js:77)
at d (vendors~app.1119d1fb9353e3bd9353.js:77)
at v (vendors~app.1119d1fb9353e3bd9353.js:77)
at vendors~app.1119d1fb9353e3bd9353.js:77
at ji (vendors~app.1119d1fb9353e3bd9353.js:77)
at mc (vendors~app.1119d1fb9353e3bd9353.js:77)
at lu (vendors~app.1119d1fb9353e3bd9353.js:77)
at cu (vendors~app.1119d1fb9353e3bd9353.js:77)
at Zc (vendors~app.1119d1fb9353e3bd9353.js:77)
at vendors~app.1119d1fb9353e3bd9353.js:77

Trying with -d option its working fine.

"build": "NODE_ENV=development webpack -d --config webpack.config.prod.js"

If the current behavior is a bug, please provide the steps to reproduce.

Create a react project with antd v4.0.0 and use the form components with the syntax getFieldDecorator().

<FormItem label="Type" labelCol={{ span: 7 }} wrapperCol={{ span: 17 }}>
{getFieldDecorator('type', {
initialValue: 'DYNAMIC',
rules: [
{
required: true,
message: 'Please select type!',
},
],ﬁ
})(
<RadioGroup>
<RadioButton value="DYNAMIC">Dynamic</RadioButton>
<RadioButton value="STATIC">Static</RadioButton>
</RadioGroup>,
)}
</FormItem>

Adding -p option to build the react project.

reproduce test repo - https://github.com/liho98/webpack-4.44.0-bug

What is the expected behavior?

It should be working fine as webpack version v4.43.0.

Other relevant information:

webpack version: v4.44.0

Node.js version: v12.16.1

Operating System: macOS Catalina 10.15.4

Additional tools: Antd v4.0.0

Issue 2:
We are running a fairly large project with 922 JavaScript and .less files being watched by Webpack's watch function on OS X (10.10.2) running on Node.js 5.2.0. During the initial build, or right when it's done with that, the following happens:

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamScheduleWithRunLoop: failed to create the cffd
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamCreate: _FSEventStreamCreate: ERROR: could not open kqueue
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamScheduleWithRunLoop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamStart(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamStop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamUnscheduleFromRunLoop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamInvalidate(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamRelease(): failed assertion 'streamRef != NULL'

I've made an issue about this at libuv/libuv#645, but I was wondering if this is something other Webpack users have also suffered from and if a workaround is known. Thanks.