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

Replace bundlesize with bundlewatch #362

Merged
merged 2 commits into from
Feb 10, 2020

Conversation

ctavan
Copy link
Member

@ctavan ctavan commented Feb 7, 2020

Unfortunately bundlewatch also doesn't seem to be super actively maintained however at least the server-side service seems to be working at the moment so we git diffs w.r.t. master directly in the Github check.

Since I can't find any drawbacks w.r.t. bundlesize I'd give it a try.

@ctavan ctavan force-pushed the replace-bundlesize-with-bundlewatch branch 2 times, most recently from a92ccff to 75c6f71 Compare February 10, 2020 08:27
@ctavan ctavan requested a review from broofa February 10, 2020 08:29
Copy link
Member

@broofa broofa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bundlewatch has smaller dependency graph, which is never a bad thing. http://npm.broofa.com/?q=bundlesize vs http://npm.broofa.com/?q=bundlewatch

@ctavan
Copy link
Member Author

ctavan commented Feb 10, 2020

I'm watching http://npm.broofa.com/?q=@ampproject/filesize as well which has an even smaller dependency graph, however it doesn't support reporting differences w.r.t. master out of the box yet.

This should be done by every developer in the global gitignore file
depending on whether they are on MacOS or use IntelliJ or whatever, it
should not be part of this project-specific .gitignore file.
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 ctavan force-pushed the replace-bundlesize-with-bundlewatch branch from 75c6f71 to 043a761 Compare February 10, 2020 14:41
@ctavan
Copy link
Member Author

ctavan commented Feb 10, 2020

BTW apparently during the last few hours there was a problem on GitHubs side with verifying signed commits which has now been resolved, however commits need to be rewritten in order for GitHub to pick up the changes. This is why I had to rebase once more…

@ctavan ctavan merged commit 0bbbdd0 into master Feb 10, 2020
@ctavan ctavan deleted the replace-bundlesize-with-bundlewatch branch February 10, 2020 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants