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

ref(react): Stop using parseSemvar #4270

Merged
merged 3 commits into from
Dec 13, 2021
Merged

Conversation

AbhiPrasad
Copy link
Member

@AbhiPrasad AbhiPrasad commented Dec 11, 2021

We don't need the bloated method from utils, just make our own. This helps save on bundle size when user's use the ErrorBoundary (which is very common).

We should maybe lint so that parseSemvar is only used in node environments, as including the entire regex is pretty expensive for ungzipped bundle size.

We don't need the bloated method from utils, just make our own
@AbhiPrasad AbhiPrasad added this to the Treeshaking / Bundle Size milestone Dec 11, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Dec 11, 2021

size-limit report

Path Base Size (582d678) Current Size Change
@sentry/browser - CDN Bundle (gzipped) 22.45 KB 22.45 KB 0%
@sentry/browser - Webpack 23.29 KB 23.29 KB 0%
@sentry/browser - Webpack - gzip = false 82.73 KB 82.73 KB 0%
@sentry/react - Webpack 23.32 KB 23.32 KB 0%
@sentry/nextjs Client - Webpack 48.07 KB 48.07 KB 0%
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 29.98 KB 29.98 KB -0.01% 🔽

@AbhiPrasad AbhiPrasad marked this pull request as ready for review December 13, 2021 15:04
@AbhiPrasad AbhiPrasad requested review from a team, sl0thentr0py and iker-barriocanal and removed request for a team December 13, 2021 15:04
@AbhiPrasad AbhiPrasad enabled auto-merge (squash) December 13, 2021 17:56
@AbhiPrasad AbhiPrasad merged commit 626102f into master Dec 13, 2021
@AbhiPrasad AbhiPrasad deleted the abhi-react-parseSemvar branch December 13, 2021 18:08
onurtemizkan pushed a commit that referenced this pull request Dec 19, 2021
We don't need the bloated method from utils, just make our own. This helps save on bundle size when user's use the `ErrorBoundary` component (which is very common).
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.

2 participants