docs(astro): Document build-time vs runtime setup in the SDK README - #23430
Draft
RulaKhaled wants to merge 1 commit into
Draft
docs(astro): Document build-time vs runtime setup in the SDK README#23430RulaKhaled wants to merge 1 commit into
RulaKhaled wants to merge 1 commit into
Conversation
sentry() no longer accepts runtime options like dsn after #23270, but the package README still showed the old pattern.
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
1 participant
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.
Updates the
@sentry/astroREADME so the getting-started examples match the v11 split from #23270.sentry()is build-time only (org,project,authToken). Runtime options likedsnlive insentry.client.config.ts/sentry.server.config.ts, which are optional: without them the SDK still initializes and readsPUBLIC_SENTRY_DSN.This was the remaining follow-up from the review on #23270.