Skip to content
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

Merged
merged 1 commit into from
Jan 28, 2020
Merged

deps: bundlesize to 0.18.0 #10272

merged 1 commit into from
Jan 28, 2020

Conversation

paulirish
Copy link
Member

hopefully fixing the spam in our CI output.

@patrickhulce patrickhulce merged commit e7abad4 into master Jan 28, 2020
@patrickhulce patrickhulce deleted the bundlesize branch January 28, 2020 03:18
@paulirish
Copy link
Member Author

didn't fix anything.

fwiw i also tried refreshing the env variable on travis but no luck either.

@paulirish
Copy link
Member Author

The upstream bug: siddharthkp/bundlesize#308

@paulirish
Copy link
Member Author

Brendan points me to #9089 where he called out out bundlewatch (which looks nice)

and speaking of other options.. there's also

https://github.com/GoogleChromeLabs/travis-size-report

and https://buildtracker.dev/

@XhmikosR
Copy link
Contributor

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.

ctavan added a commit to uuidjs/uuid that referenced this pull request Feb 7, 2020
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)
ctavan added a commit to uuidjs/uuid that referenced this pull request Feb 10, 2020
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)
ctavan added a commit to uuidjs/uuid that referenced this pull request Feb 10, 2020
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)
ctavan added a commit to uuidjs/uuid that referenced this pull request Feb 10, 2020
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants