Closed kedarv closed 3 years ago
/cc @valscion Can we add tests late? I can send tests late, right now I am busy with webpack-dev-server
Yeah we can add tests later to get this bug fix out.
I'll copy over what I wrote in https://github.com/webpack-contrib/webpack-bundle-analyzer/pull/384#issuecomment-842324202 to here:
as long as there are no tests, it's possible that we'll break the fix even in a patch release as there is no way we can make sure that this fix doesn't suddenly stop working unless we have test coverage for that.
@valscion It looks like I'll have to waste time on a pretty obvious bug :confused: :disappointed:
I'll get this bug fix out, no worries about that. I'm merely noting the effect a missing test coverage has for this kind of bug fix.
It's not possible for us to keep this bug fix working for sure if we do changes to the code later. Reproducing the bug takes effort we're not willing to do every time we change the code.
I do appreciate @alexander-akait you reproducing the original issue in #384! It was very helpful βΊοΈ it makes it possible for us to ship this fix even without test coverage, and I do appreciate that π
Can you try using this https://github.com/webpack-contrib/webpack-bundle-analyzer/pull/384#issuecomment-838569309? Do you see the error? Just want check it out too
Yes I see the error with the reproduction
This fix has been released in v4.4.2 π
via https://github.com/webpack-contrib/webpack-bundle-analyzer/pull/384#issuecomment-838827301
In some cases,
this.compiler.outputFileSystem.constructor
can be undefined, causing access to properties on this to fail. This PR adds a check to prevent this.