v1.0.0 Roadmap

[siddharthkp]

Hi 👋

I built bundlesize in June 2017 to solve a problem I had at the time.

Since then, it has become pretty popular. Here's are some crazy numbers:

• Bundlesize does about 50k builds every week
• 1.5M builds in it's lifetime (2 years)
• There are 10.8K public repositories (and unknown number of private repos 🤷‍♀) that have bundlesize as a dependency
• Used by popular open source libraries like Bootstrap, lighthouse, styled-components, emotion, redux-saga, react-apollo, popper and a bunch more!

But I haven't been doing a good job at maintaining as after I moved projects. I'm really thankful to the ~50 contributors that have been generous with their time in improving bundlesize.

Maintaining an open source project requires consistent effort, not just with adding code, but also code reviews and support. I haven't been able to keep up with the changes in my career.

The Chrome Performance Fund might be able to help with that by paying contributors for their time 👏

---

There are a few themes that come up in the issues on the regular. Please give a 👍 to the problems you have faced and would like to see solved.

Feel free to create an issue to suggest additions to this roadmap as well

[siddharthkp]

Deeper GitHub integration

Right now, bundlesize requires a manual configuration with copy-pasting access tokens, which

1. Prevents some folks from using it (Don't know how to, Don't have access, admins don't allow, etc.)
2. Is very difficult to debug when it doesn't work.

Using GitHub Apps + Checks will solve both of these problems and allow us to use improved UX

Related issues: #223 #203 #148 #29

[siddharthkp]

Better configuration

bundlesize started with an array in package.json, this did not scale well 😅

We now have inconsistent support in package.json and the CLI (used with npx). One of the most popular request is to add a config file.

1. We can tackle all these problems with a common format over all 3 mediums (most probably using cosmiconfig)

2. On the same theme, better support toolkits where you don't have direct access to the files. Example: create-react-app, nextjs

Related issues: #304 #256 #225 #206 #173 #162

[siddharthkp]

Better error handling

Because bundlesize uses access token from environment variables, it can fail given any of these scenarios:

1. Token was not set correctly
2. Token does't have the correct permissions attached to it
3. Token expired
4. Incorrect parameters sent to GitHub for status

All of these scenarios result in a 404: Not Found error or the build hanging in CI which is not helpful. (GitHub returns 404 instead of 401)

We can take care of most of these in the tool itself and give more helpful error messages that can help folks fix their issue.

Related issues: #93 #245 #280 #284 #308

[siddharthkp]

Remove false negatives

Like any software, bundlesize has bugs. The scariest of them is when bundlesize should have failed but does not fail the build.

This stems from returning the wrong flag for a CI environment OR reading the file size incorrectly.

A few tests will take us a long way!

Related issues: #188 #229 #159 #281 #267

[siddharthkp]

Support bundlesize in forks

In every CI system, forks don't get environment variables which makes a lot of sense. This also means bundlesize can't report on pull requests submitted to the source repository. (Basically, every external contribution to an open source project)

I don't have a solution yet, but we might have to think of alternate ways of reporting like comments

Related issues: #219

I know @mxstbr and @developit have run into this amongst others

[siddharthkp]

Better reporting

bundlesize does an okay job at reporting when there are multiple files involved.

1. The messages in GitHub status should be better
2. Fix the details link when there are too many files

Related issues: #182 #208 #164 #285

[siddharthkp]

Make it easier to support more CI environments

Codefresh: #236
Teamcity #257
Sephamore #176
AppVeyor #234
GitLab #19

[siddharthkp]

Plugin system to extend/tweak core functionality via plugins

Every once in a while there's a feature request (or even a pull request) that makes a lot of sense for the contributor and their team but doesn't sit well in bundlesize core.

Example: Add check for minSize; Warn instead of failing build

It would make a lot of sense if you can intercept bundlesize and use it's output to set the message that fits your need

Related issues: #207 #271 #254

[siddharthkp]

Hi collaborators with push access (30!) 👋

Please, add a 👍 to the GitHub issue (first thing on top) if you are cool with bundlesize being part of the Chrome Performance Fund

cc train: @SaraVieira @styfle @jagzviruz @destromas1 @montmanu @rahulgandhi @karanjthakkar @ateev @cg-cnu @narendrashetty @reznord @sunilkumarc @yatharthk @vs1682 @chakrihacker @hackerrdave @ankibalyan @samparsky @tohjustin @ForsakenHarmony @hawkins @kuldeepkeshwar @kakadiadarpan @Pancrisp @g3offrey @sreetamdas @kamleshchandnani @palashmon @nitin42 @jkdamilola @Haroenv

[karanjthakkar]

👏

[Haroenv]

One thing which would make it a lot nicer too is if the comparison would be to the base branch on GitHub (instead of always master), since that way you get a pure diff

[Haroenv]

Sometimes you want to compare why something changed, it would be nice to visually diff the two bundles somehow. This could be done by tracking the bundled files in git, but it’s not a nice solution

[kuldeepkeshwar]

Support for Github Enterprise with a pluggable way to store stats. The storage solution can be Remote Server or FileSystem