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

Add size-limit config #2173

Draft
wants to merge 18 commits into
base: master
Choose a base branch
from
Draft

Conversation

aryaemami59
Copy link
Contributor

This PR:

  • Adds size-limit config to monitor bundle size changes in preparation for any potential changes we'll have to make to migrate to React 19.

Copy link

codesandbox-ci bot commented May 15, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@timdorr
Copy link
Member

timdorr commented May 16, 2024

Honestly, I'm not a huge fan of these sorts of tools. They tend to be more annoying than helpful. Maybe we can limit it to just a react19 branch, so we don't have to tend to it after we complete that work?

Edit: Wait, don't we already have this? https://github.com/reduxjs/react-redux/blob/master/.github/workflows/size.yaml

@aryaemami59
Copy link
Contributor Author

@timdorr

Honestly, I'm not a huge fan of these sorts of tools. They tend to be more annoying than helpful.

That's fair, but size-limit does give us an idea of how the changes that we make impact our bundle sizes. And with the way I setup the config, it can keep track of every single named export, in every single package entry point, in both development and production builds. And the config is simple enough that I hope we'd be able to insert into any one of the redux packages and it should just work.

Edit: Wait, don't we already have this? https://github.com/reduxjs/react-redux/blob/master/.github/workflows/size.yaml

While preactjs/compressed-size-action does give us some info about bundle size changes, it looks like it's only looking at dist/cjs/index.js and dist/react-redux.legacy-esm.js. It also doesn't look at named exports, or different environments.

The idea is to have this here so that if we were ever to make a set of changes, we could use it to keep an eye on bundle sizes, it doesn't necessarily have to put a "limit" on anything.

@EskiMojo14
Copy link
Collaborator

yeah, while I don't think the concept of a size "limit" is very useful, I do find it useful to have visibility on how a given set of changes affects final bundle size.

@timdorr
Copy link
Member

timdorr commented May 17, 2024

Could this supplant our usage of compressed-size-action? That one hasn't been updated in a long time and causes some warnings in CI that will eventually turn into errors, so it's been on my radar to replace it.

@aryaemami59
Copy link
Contributor Author

I guess we could use https://github.com/EskiMojo14/size-limit-action, same thing we're doing with RTK.

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.

None yet

3 participants