Fix size-limit config

[aryaemami59]

This PR:

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

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[netlify]

✅ Deploy Preview for redux-starter-kit-docs ready!

Name	Link
🔨 Latest commit	7bac2a4
🔍 Latest deploy log	https://app.netlify.com/sites/redux-starter-kit-docs/deploys/672b8b7dd3b52200082fae76
😎 Deploy Preview	https://deploy-preview-4415--redux-starter-kit-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codesandbox-ci]

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.

Latest deployment of this branch, based on commit 7bac2a4:

Sandbox	Source
@examples-query-react/basic	Configuration
@examples-query-react/advanced	Configuration
@examples-action-listener/counter	Configuration
rtk-esm-cra	Configuration

[EskiMojo14]

For what it's worth, I don't think we actually want size info for every single entry point and export possible. We intentionally only measure entry points and exports we're actually concerned about the size for.

It's less of an issue since we filter out unchanged entries, but it still feels a little spammy.

[markerikson]

Yeah, this is definitely a lot more info than we need or care about. (Also, it made the size job take 14 minutes to run.)

Is there actually a problem with the current config?

[aryaemami59]

I cut down on the size-limit config, let me know if this is still not ideal and I will try to look for another solution.