You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First Step to the new SvelteKit SDK: Setting up the package and figuring out how we can provide the best SDK init DX.
Ideally, we'd like to achieve similar DX as in the NextJS SDK: Users provide sentry.(server|client).config.(ts|js) config files with a Sentry.init call to the respective SDK. These files are added to the entry points of the client/server bundles and that's how we initialize the SDK as early as possible in the application life cycle.
The content you are editing has changed. Please copy your edits and refresh the page.
If the "entry point injection" doesn't work, we can still resort to initializing the SDKs in hooks.(client|server).ts files, which are part of SvelteKit and initialize very early in the life cycle.
Once we have a working auto-wrapping approach, we could theoretically also explore injecting the init call into the hooks files.
The text was updated successfully, but these errors were encountered:
First Step to the new SvelteKit SDK: Setting up the package and figuring out how we can provide the best SDK init DX.
Ideally, we'd like to achieve similar DX as in the NextJS SDK: Users provide
sentry.(server|client).config.(ts|js)
config files with aSentry.init
call to the respective SDK. These files are added to the entry points of the client/server bundles and that's how we initialize the SDK as early as possible in the application life cycle.Tasks
require
calls #7377Sentry.init
calls into server and client bundles #7391init
functions #7408Alternative Approach:
If the "entry point injection" doesn't work, we can still resort to initializing the SDKs in
hooks.(client|server).ts
files, which are part of SvelteKit and initialize very early in the life cycle.Once we have a working auto-wrapping approach, we could theoretically also explore injecting the init call into the hooks files.
The text was updated successfully, but these errors were encountered: