-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
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? Sign in to your account
deps: bundlesize to 0.18.0 #10272
deps: bundlesize to 0.18.0 #10272
Conversation
didn't fix anything. fwiw i also tried refreshing the env variable on travis but no luck either. |
The upstream bug: siddharthkp/bundlesize#308 |
Brendan points me to #9089 where he called out out bundlewatch (which looks nice) and speaking of other options.. there's also |
I'm also looking for alternative solutions. The aforementioned issue is present for so many months. Also, bundlesize itself is quite a big devDependency and requires native bindings due to brotli. One could just target Node.js > 10.16 or so that has brotli built in. I'll keep an eye on bundlewatch. I've also found https://github.com/ampproject/filesize but it doesn't seem to integrate with pull requests. |
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
hopefully fixing the spam in our CI output.