Figure out why NPM 6.11+ breaks our build

[IanMatthewHuff]

This is the build issue that hit us previously. Right now we are pinned at 6.10.3. But in 6.11+ we get an issue with -n command that we pass to webpack. NPM in this release had a number of issues with windows command lines and this issue on only showing on windows, so I would assume this is related (see notes in 6.11.1 6.11.2).

https://github.com/npm/cli/releases

[IanMatthewHuff]

reported.

[IanMatthewHuff]

npm/npx#5 - Open issue causing the problem
npm/npx#30 - Possible maintenance issues? This is npm version of npx. Previous version of this died here: zkat/npx#223

[IanMatthewHuff]

Set max heap globally (which is why we were using npx I believe):
npm/npm#12238

Something like this works as a script:
cross-env NODE_OPTIONS=--max_old_space_size=9096 webpack --config webpack.config.js --mode production

[IanMatthewHuff]

Seems like nyc needs an update as well:
istanbuljs/nyc#1205
istanbuljs/nyc#1104

I think 15 that just came out should fix windows nyc.

[rchiodo]

Validated