feat(core): split exports by browser/server for bundle size by isaacs · Pull Request #20435 · getsentry/sentry-javascript

isaacs · 2026-04-21T23:37:00Z

Split the exports from @sentry/core into three options:

@sentry/core, the default (unchanged)
@sentry/core/browser, containing only shared and browser-specific
functionality, nothing server-specific.
@sentry/core/server, containing only shared and server-specific
functionality, nothing browser-specific.

This allows us to make the bundle sizes quite a bit smaller in our
browser SDKs where this is important, while adding more functionality to
our server-specific SDKs, in @sentry/core where they can be easily
shared across runtimes.

fix: #20434
fix: JS-2243

linear-code · 2026-04-21T23:37:04Z

JS-2243 Split @sentry/core exports up, adding ./server and ./browser exports

github-actions · 2026-04-22T03:15:03Z

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	26.3 kB	-	-
@sentry/browser - with treeshaking flags	24.78 kB	-	-
@sentry/browser (incl. Tracing)	44.17 kB	-	-
@sentry/browser (incl. Tracing + Span Streaming)	46.39 kB	-	-
@sentry/browser (incl. Tracing, Profiling)	49.14 kB	-	-
@sentry/browser (incl. Tracing, Replay)	83.82 kB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	73.28 kB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	88.51 kB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	101.12 kB	-	-
@sentry/browser (incl. Feedback)	43.44 kB	-	-
@sentry/browser (incl. sendFeedback)	31.11 kB	-	-
@sentry/browser (incl. FeedbackAsync)	36.19 kB	-	-
@sentry/browser (incl. Metrics)	27.6 kB	-	-
@sentry/browser (incl. Logs)	27.73 kB	-	-
@sentry/browser (incl. Metrics & Logs)	28.43 kB	-	-
@sentry/react	28.04 kB	-	-
@sentry/react (incl. Tracing)	46.4 kB	-	-
@sentry/vue	31.18 kB	-	-
@sentry/vue (incl. Tracing)	46.02 kB	-	-
@sentry/svelte	26.32 kB	-	-
CDN Bundle	28.9 kB	-0.01%	-2 B 🔽
CDN Bundle (incl. Tracing)	46.94 kB	-	-
CDN Bundle (incl. Logs, Metrics)	30.33 kB	-0.01%	-3 B 🔽
CDN Bundle (incl. Tracing, Logs, Metrics)	48.03 kB	-0.01%	-4 B 🔽
CDN Bundle (incl. Replay, Logs, Metrics)	69.64 kB	-0.01%	-4 B 🔽
CDN Bundle (incl. Tracing, Replay)	84.32 kB	+0.01%	+3 B 🔺
CDN Bundle (incl. Tracing, Replay, Logs, Metrics)	85.4 kB	+0.01%	+1 B 🔺
CDN Bundle (incl. Tracing, Replay, Feedback)	90.12 kB	-0.01%	-6 B 🔽
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics)	91.22 kB	+0.03%	+27 B 🔺
CDN Bundle - uncompressed	84.88 kB	-	-
CDN Bundle (incl. Tracing) - uncompressed	140.44 kB	-	-
CDN Bundle (incl. Logs, Metrics) - uncompressed	89.08 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed	143.9 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed	213.9 kB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	259.14 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed	262.59 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	272.84 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed	276.28 kB	-	-
@sentry/nextjs (client)	48.9 kB	-	-
@sentry/sveltekit (client)	44.64 kB	-	-
@sentry/node-core	60.48 kB	+0.02%	+7 B 🔺
@sentry/node	165.51 kB	+0.01%	+9 B 🔺
@sentry/node - without tracing	73.49 kB	+0.01%	+6 B 🔺
@sentry/aws-serverless	107.64 kB	+0.01%	+5 B 🔺
@sentry/cloudflare (withSentry) - minified	169.37 kB	-	-
@sentry/cloudflare (withSentry)	427.59 kB	-	-

View base workflow run

Split the exports from `@sentry/core` into three options: - `@sentry/core`, the default (unchanged) - `@sentry/core/browser`, containing _only_ shared and browser-specific functionality, nothing server-specific. - `@sentry/core/server`, containing _only_ shared and server-specific functionality, nothing browser-specific. This should allow us to make the bundle sizes quite a bit smaller in our browser SDKs where this is important, while adding more functionality to our server-specific SDKs, in `@sentry/core` where they can be easily shared across runtimes. Integration may require updating our `tsconfig` settings so that tsc knows it is allowed to look on `package.json` exports. fix: #20434 fix: JS-2243

Split the exports from `@sentry/core` into three options: - `@sentry/core`, the default (unchanged) - `@sentry/core/browser`, containing _only_ shared and browser-specific functionality, nothing server-specific. - `@sentry/core/server`, containing _only_ shared and server-specific functionality, nothing browser-specific. This should allow us to make the bundle sizes quite a bit smaller in our browser SDKs where this is important, while adding more functionality to our server-specific SDKs in `@sentry/core`, where they can more easily be shared across runtimes. Some integration requires updating `tsconfig` settings so that tsc knows it is allowed to look up `package.json` exports. In particular, we cannot use the `module: "node"` option, or `moduleResolution: "node"`. In many cases, this means either using `module: "esnext"` and `moduleResolution: "bundler"`, so that tsc lets the bundler handle the assembly, or `nodenext` or `node16` for both `module` and `moduleResolution`. fix: #20434 fix: JS-2243

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 24304fe. Configure here.}

Split the exports from `@sentry/core` into three options: - `@sentry/core`, the default (unchanged) - `@sentry/core/browser`, containing _only_ shared and browser-specific functionality, nothing server-specific. - `@sentry/core/server`, containing _only_ shared and server-specific functionality, nothing browser-specific. This should allow us to make the bundle sizes quite a bit smaller in our browser SDKs where this is important, while adding more functionality to our server-specific SDKs in `@sentry/core`, where they can more easily be shared across runtimes. Some integration requires updating `tsconfig` settings so that tsc knows it is allowed to look up `package.json` exports. In particular, we cannot use the `module: "node"` option, or `moduleResolution: "node"`. In many cases, this means either using `module: "esnext"` and `moduleResolution: "bundler"`, so that tsc lets the bundler handle the assembly, or `nodenext` or `node16` for both `module` and `moduleResolution`. fix: #20434 fix: JS-2243

JPeer264

Do you think it would make sense to add size limit / bundle checks for these exports?

Split the exports from `@sentry/core` into three options: - `@sentry/core`, the default (unchanged) - `@sentry/core/browser`, containing _only_ shared and browser-specific functionality, nothing server-specific. - `@sentry/core/server`, containing _only_ shared and server-specific functionality, nothing browser-specific. This should allow us to make the bundle sizes quite a bit smaller in our browser SDKs where this is important, while adding more functionality to our server-specific SDKs in `@sentry/core`, where they can more easily be shared across runtimes. Some integration requires updating `tsconfig` settings so that tsc knows it is allowed to look up `package.json` exports. In particular, we cannot use the `module: "node"` option, or `moduleResolution: "node"`. In many cases, this means either using `module: "esnext"` and `moduleResolution: "bundler"`, so that tsc lets the bundler handle the assembly, or `nodenext` or `node16` for both `module` and `moduleResolution`. fix: #20434 fix: JS-2243

JPeer264

Changes LGTM, also it is backwards compatible so we can ship it 🚢

The question is still valid: #20435 (review)

Split the exports from `@sentry/core` into three options: - `@sentry/core`, the default (unchanged) - `@sentry/core/browser`, containing _only_ shared and browser-specific functionality, nothing server-specific. - `@sentry/core/server`, containing _only_ shared and server-specific functionality, nothing browser-specific. This should allow us to make the bundle sizes quite a bit smaller in our browser SDKs where this is important, while adding more functionality to our server-specific SDKs in `@sentry/core`, where they can more easily be shared across runtimes. Some integration requires updating `tsconfig` settings so that tsc knows it is allowed to look up `package.json` exports. In particular, we cannot use the `module: "node"` option, or `moduleResolution: "node"`. In many cases, this means either using `module: "esnext"` and `moduleResolution: "bundler"`, so that tsc lets the bundler handle the assembly, or `nodenext` or `node16` for both `module` and `moduleResolution`. fix: #20434 fix: JS-2243

isaacs · 2026-05-09T23:15:48Z

@JPeer264

Sorry, thought I replied to this, but I guess gh mobile ate it:

Do you think it would make sense to add size limit / bundle checks for these exports?

Yes, 100%. I intend to do this on a subsequent PR.

## Summary - Adds `browser.d.ts` and `server.d.ts` to the `files` list in `@sentry/core` `package.json` so they are included in the published npm tarball - Adds `typesVersions` entries for `browser` and `server` subpaths to support TypeScript < 5.0 ## Context PR [#20435](#20435) introduced `@sentry/core/browser` and `@sentry/core/server` subpath exports and added root-level `.d.ts` shim files for compatibility with TypeScript compilers that don't support the `exports` field (e.g. `moduleResolution: "node"`). However, the `.d.ts` shims were not added to the `files` list, so they were excluded from the published `10.53.0` tarball. This breaks downstream consumers like `@sentry/react-native` ([getsentry/sentry-react-native#6139](getsentry/sentry-react-native#6139)) — their TS compiler can't resolve `@sentry/core/browser`, causing `BaseTransportOptions` to become unresolvable and `ReactNativeTransportOptions` to fail the type constraint check: ``` error TS2344: Type 'ReactNativeTransportOptions' does not satisfy the constraint 'BaseTransportOptions'. Type 'ReactNativeTransportOptions' is missing the following properties from type 'BaseTransportOptions': url, recordDroppedEvent ``` ## Test plan - [ ] Verify `npm pack --dry-run` includes `browser.d.ts` and `server.d.ts` at the package root - [ ] Verify `@sentry/react-native` builds successfully against a patched `@sentry/core` 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch 6 times, most recently from 143a2a5 to 1494709Compare April 22, 2026 01:45

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch 5 times, most recently from d5dddbf to 8eba1e9Compare April 22, 2026 18:26

isaacs marked this pull request as ready for review April 22, 2026 18:26

cursorBot reviewed Apr 22, 2026
View reviewed changes

Comment threaddev-packages/rollup-utils/utils.mjs Outdated

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 8eba1e9 to 8ea4f5cCompare April 22, 2026 18:50

cursorBot reviewed Apr 22, 2026
View reviewed changes

Comment threaddev-packages/rollup-utils/npmHelpers.mjs

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 8ea4f5c to 787f44bCompare April 22, 2026 19:19

isaacs enabled auto-merge (rebase) April 22, 2026 19:19

isaacs disabled auto-merge April 22, 2026 19:19

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 787f44b to 7076f7cCompare April 22, 2026 19:20

cursorBot reviewed Apr 22, 2026
View reviewed changes

Comment threadpackages/core/src/shared-exports.ts
Comment threadpackages/core/src/integrations/http/client-subscriptions.ts

isaacs requested review from mydea and timfish April 23, 2026 14:24

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 7076f7c to e2cf052Compare April 23, 2026 14:34

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from e2cf052 to 67bf5c4Compare April 23, 2026 14:41

sentryBot reviewed Apr 23, 2026
View reviewed changes

Comment threadpackages/node-core/src/integrations/http/SentryHttpInstrumentation.ts

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from c1c9cf0 to 5beb2e3Compare April 29, 2026 17:22

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 5beb2e3 to ca38b53Compare April 29, 2026 20:43

sentryBot reviewed Apr 29, 2026
View reviewed changes

Comment threaddev-packages/rollup-utils/utils.mjs Outdated

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from ca38b53 to 24304feCompare April 29, 2026 20:52

cursorBot reviewed Apr 29, 2026
View reviewed changes

Comment threadpackages/solidstart/test/server/errorboundary.test.tsx Outdated

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 24304fe to da8cd5aCompare April 29, 2026 21:07

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from da8cd5a to 8fe31cbCompare April 29, 2026 21:19

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 8fe31cb to 28b47ecCompare April 30, 2026 00:05

sentryBot reviewed Apr 30, 2026
View reviewed changes

Comment threadpackages/core/src/server-exports.ts

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 28b47ec to a783c2eCompare April 30, 2026 00:25

JPeer264 reviewed Apr 30, 2026
View reviewed changes

Comment threadpackages/browser/test/tracing/setActiveSpan.test.ts

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from a783c2e to 6494082Compare May 4, 2026 16:27

JPeer264 approved these changes May 5, 2026
View reviewed changes

isaacs force-pushed the isaacschlueter/split-server-browser-core-exports branch from 6494082 to 5e89a33Compare May 9, 2026 22:22

isaacs enabled auto-merge (squash) May 9, 2026 22:54

isaacs merged commit 80f05ff into developMay 9, 2026
513 of 515 checks passed

isaacs deleted the isaacschlueter/split-server-browser-core-exports branch May 9, 2026 23:06

sentry-release-botBot mentioned this pull request May 12, 2026
publish: getsentry/sentry-javascript@10.53.0 getsentry/publish#8155
Closed
47 tasks

github-actionsBot mentioned this pull request May 12, 2026
Split @sentry/core exports up, adding ./server and ./browser exports #20434
Closed

antonis mentioned this pull request May 12, 2026
fix(core): Include subpath type shims in published package #20835
Merged
2 tasks

Navigation Menu

Uh oh!

Uh oh!

feat(core): split exports by browser/server for bundle size - #20435

feat(core): split exports by browser/server for bundle size#20435
isaacs merged 1 commit into
developfrom
isaacschlueter/split-server-browser-core-exports

isaacs commented Apr 21, 2026•
edited
Loading

Uh oh!

linear-codeBot commented Apr 21, 2026

Uh oh!

github-actionsBot commented Apr 22, 2026•
edited
Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursorBot left a comment

Uh oh!

Uh oh!

Uh oh!

JPeer264 left a comment

Uh oh!

Uh oh!

JPeer264 left a comment

Uh oh!

Uh oh!

isaacs commented May 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

isaacs commented Apr 21, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

linear-codeBot commented Apr 21, 2026

Uh oh!

github-actionsBot commented Apr 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

size-limit report 📦

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

JPeer264 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

JPeer264 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

isaacs commented May 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

isaacs commented Apr 21, 2026•
edited
Loading

github-actionsBot commented Apr 22, 2026•
edited
Loading