Closed notiv-nt closed 7 years ago
I'm also getting this with:
Node v5.3.0 NPM 3.10.6 and webpack
I'm running into the same issue with webpack running tests. anyone figure this out? @notiv-nt, @alassiter did you ever get this fixed?
I tried using
node: {
fs: "empty"
}
but no luck
@cfinke Can a new release be pushed to npm with this commit included? npm still reflects the prior package.json.
Sorry about that, I've published version 1.0.2 on npm now.
Node v5.12.0 NPM 3.8.6 Win10
Using Webpack