Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
This was a regression in v3.3.1. Use v3.3.2 that has a fix.
Something seems wrong with the last release (3.3.1) :
The text was updated successfully, but these errors were encountered:
Have you checked that it was working with v3.3.0?
Sorry, something went wrong.
Yes it works
Ok @th0r it's likely that #262 might have caused an issue. There's a strange \u003c line in the code that should be valid JS
I'm able to reproduce this on our own repository when building a static report.
Server build has no issues
same here, firefox and chrome... thx
Yup we're looking into this. This is a known regression
Fixed in v3.3.2
Bump webpack-bundle-analyzer to 3.3.2
* Fix VULN webpack-contrib/webpack-bundle-analyzer#263
chore: bump lodash and WBA
- Fixes WS-2019-0058: webpack-contrib/webpack-bundle-analyzer#263
- Fixes CVE-2019-10744: lodash/lodash#4336
updated webpack-bundle-analyzer because of WS-2019-0058 - webpack-con…
Successfully merging a pull request may close this issue.