-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix size-limit
config
#4415
base: master
Are you sure you want to change the base?
Fix size-limit
config
#4415
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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 68b3a4a:
|
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. |
43b6a99
to
723c544
Compare
Yeah, this is definitely a lot more info than we need or care about. (Also, it made the Is there actually a problem with the current config? |
764eb4e
to
32e222d
Compare
I cut down on the |
bcb769b
to
b3fbc67
Compare
9d20e8b
to
e1ecb4c
Compare
8d2f628
to
297a8ea
Compare
f12ca17
to
bc1e685
Compare
f7a6ba8
to
8906ae4
Compare
8906ae4
to
7bac2a4
Compare
41862a0
to
0fff6a5
Compare
0fff6a5
to
68b3a4a
Compare
This PR:
size-limit
config to monitor bundle size changes in preparation for any potential changes we'll have to make to migrate to React 19.