compressed-size-action replacement tracker

[msutkowski]

Original context here: #632

To evaluate:

• Supposedly https://github.com/kuldeepkeshwar/size-plugin-bot works better because it's a bot and not an action, or so the author told me.
  • tl:dr; I don't trust this lib to have the permissions it requests and documentation is lacking. You need a PHD to figure out how to configure this, and I'm short on that, unfortunately. In general, I would not recommend this as it asks for overzealous GitHub permissions and looks like it can possibly rewrite branches and be destructive. I wouldn't have a problem with that, but the code base is a little bit of a 🔥 and references a lot of the authors WIP libs that specifically say to not use for anything other than hobby projects? As a comparison, all of these type of libs basically just use github status checks - this one tries to do much more.
• https://github.com/bundlewatch/bundlewatch#i-use-bundlesize-why-should-i-switch-to-bundlewatch ?
  • I spent about 2 hours trying to get this to pass in a PR here, as well as on one of my own repos and kept running into walls. It seems like their service is down and not storing anything even though it's generating the output and a permalink. I could fork their service layer and spin up a quick instance and point to that, but that defeats the point of a managed service IMO. I will evaluate the other options before going that route.
• https://github.com/ai/size-limit
  • I got this working, but it has the same issue as compressed-size-action regarding forked PRs. It'd need to have a service/github app layer added.
• https://github.com/siddharthkp/bundlesize2
  • I got this working, but the GitHub App never posted back the status check results even though it console.log'd that it was 'working'. I realize this is still a WIP, but could possibly be picked up and moved along with a few contributions.
• https://github.com/siddharthkp/bundlesize
  • I'm going to spin up a test repo with travis and see if I can get this to work as desired. This seems to be the most promising route at this point.

[msutkowski]

Updated notes. I'm going to ping the bundlewatch folks and see if they can let me know what the deal is on service failures. As of right now, that'd be my preferred choice. After that, I'll try the travis/bundlesize combo. After that, I'll just fork bundlewatch and bend it to my will 💪

[msutkowski]

Will be closed by #638 🎉

[phryneas]

Repopening this as #638 does not seem to be a viable solution

[msutkowski]

Tacking on a note: current thought process is to stand up a microservice + GitHub bot (based on Probot). I should be able to have something up by the EOW for sure. The ideal solution would borrow some of the infra from bundlesize2 and bundlewatch.

[markerikson]

We seem to have settled on https://github.com/ai/size-limit now.