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(svelte): Update component tracking docs with new withSentryConfig approach #5649

Merged
merged 4 commits into from Oct 21, 2022

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented Oct 14, 2022

⚠️ Only merge, once next SDK version is released!

This PR updates the Svelte component tracking docs with usage instructions for the new approach we recently introduced to the Svelte SDK. Instead of manually adding a preprocessor to their svelte config, users can now simply wrap their config with a Sentry wrapper function that takes care of adding this preprocessor for them. This new approach allows us to make more changes to the config in the future without asking our users every time to change something in their config.

ref: getsentry/sentry-javascript#5923

@vercel
Copy link

vercel bot commented Oct 14, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
sentry-docs ✅ Ready (Inspect) Visit Preview Oct 15, 2022 at 10:42AM (UTC)

Copy link
Contributor

@imatwawana imatwawana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple wording things, but otherwise LGTM!

Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>
@Lms24 Lms24 merged commit 15e464a into master Oct 21, 2022
@Lms24 Lms24 deleted the lms-svelte-withSentryConfig branch October 21, 2022 11:33
@github-actions github-actions bot locked and limited conversation to collaborators Nov 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants