Repository navigation
feat(astro): Add @sentry/astro/integration entry for the Astro integration - #25726
Merged
Conversation
isaacs
requested review from
chargome and
s1gr1d
and removed request for
a team
October 23, 2026 21:20
Contributor
size-limit report 📦Compared: 80ea09f (PR test merge using develop at db8b096) Against: c9b4058 (develop) · base run #64518
|
Contributor
Optional E2E testsSome optional checks were not successful. They do not block the merge. 3 not successful, 51 successful. See the run.
Successful checks
|
isaacs
requested review from
andreiborza,
logaretm,
msonnb and
mydea
and removed request for
a team
October 29, 2026 18:13
…gration The root entry of `@sentry/astro` is both the server runtime SDK and, through its default export, the Astro integration for `astro.config`. The integration imports `@sentry/bundler-plugins/vite`, the orchestrion Vite plugin, `fs` and `createRequire`, so the server runtime entry reaches all of them. Any tool that traces or bundles the server entry then pulls that tooling in. The new `@sentry/astro/integration` entry exports the integration as its default and as `sentryAstro`. The root default export stays, deprecated, until the next major version, so existing `astro.config` files keep working. The E2E apps use the new entry. The new entry has a `node` condition that points at the ESM build, the same as `./middleware`. The CJS build of `@sentry/astro` does not load under the package's `"type": "module"`, and the existing entries avoid it the same way. Refs #25676 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
isaacs
force-pushed
the
isaacschlueter/js-3989-guard-server-runtime-entries-against-pulling-in-build-time
branch
from
October 29, 2026 18:14
935b98a to
39bcd92
Compare
isaacs
enabled stacked auto-merge (squash)
October 30, 2026 19:08
isaacs
deleted the
isaacschlueter/js-3989-guard-server-runtime-entries-against-pulling-in-build-time
branch
October 30, 2026 21:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The root entry of
@sentry/astrois both the server runtime SDK and, through its default export, the Astro integration forastro.config. The integration imports@sentry/bundler-plugins/vite, the orchestrion Vite plugin,fsandcreateRequire, so the server runtime entry reaches all of them. Any tool that traces or bundles the server entry then pulls that tooling in.The new
@sentry/astro/integrationentry exports the integration as its default and assentryAstro. The root default export stays, deprecated, until the next major version, so existingastro.configfiles keep working. The E2E apps use the new entry.The new entry has a
nodecondition that points at the ESM build, the same as./middleware. The CJS build of@sentry/astrodoes not load under the package's"type": "module", and the existing entries avoid it the same way.Fixes #25676
Stack created with GitHub Stacks CLI • Give Feedback 💬