Aiming to help teams analyze and optimize their webpack bundle. Bringing a delivery performance concern into their day to day process by tracking the overall asset profile for every commit, and reporting this information back to GitHub. Allowing you to see the impact your pull request will have on the overall asset profile of your app.

Hi everyone! 👋 Now that JavaScript is TAKING OVER ALL THE THINGS, we've got some really great tools like webpack and the npm registry to help package, bundle, and reuse JavaScript. The combination of these tools is a force to be reckoned with. After working on a few projects that utilized these tools, I recognized a gap in the way we were measuring success. Long ago in a land far far away (circa early 2000s web development) we would obsess over the size of the code we were forcing our users to download. Public CDNs and dependency free libraries seem to be becoming the exception as we continue to lean into the lie that bandwidth is cheap and compression is good enough. Many times we can't even answer how any given package is going to effect our delivery size before getting it in front of our users. We've traded in our size conscious, delivery performance obsession in for the admittedly high upside of module systems and bundlers. Cleanly separating and re-using our own code, and making it easier than ever to distribute and utilize code as a community. This is a huge win, but ignoring the delivery profile of our code can cost our users time (especially on that vital first-run experience!). The goal of packtracker.io is to bring a delivery performance benchmark back into your process and consciousness. To make front and center how your use of webpack and npm affect your delivery profile, and to make those optimizations gratifyingly visible. 📉 🎉 I'm currently doing a closed beta with a few people that want to get involved, so feel free to request early access if that sounds interesting. Hope you'll want to help me kick the tires and see if this thing is useful to you!

It's amazing. We started to use packtracker in our application and we got a visual representation with packages being in packs we absolutely didn't expect. This then allowed us to go down certain routes and eventually we were able to reduce our packsize by 80% and leveraged a better build approach. I think this will become essential for many webpack users!

🚀 We did it y'all, now open for signup. 🚀 📊 Webpack bundle analysis on every commit ✅ Report build changes on every pull request 🔴 Fail your pull requests by setting size budgets 🆓 Always free for Open Source 🔒 Free trial for private projects https://packtracker.io/?utm_sour...

packtracker.io

Webpack bundle analysis, for every commit 📉

Webpack bundle analysis, for every commit 📉

packtracker.io

Webpack bundle analysis, for every commit 📉

Webpack bundle analysis, for every commit 📉

Do you use packtracker.io?

Do you use packtracker.io?