Lukas Stracke
Lukas Stracke
### Problem Statement From time to time we get reports about browser extensions using Sentry with global handler integrations installed. The consequences are that the extension SDK collides with an...
This PR explicitly sets Svelte 3 and 4 as peer dependencies for SvelteKit. We already require these versions in `@sentry/svelte` but this peer dep conflict goes unnoticed when installing `@sentry/sveltekit`....
### Describe the problem TL;DR: We (Sentry) propose `handleLoad` hooks for client and server to have a central hook to wrap users' `load` functions with common functionality. Hi, Sentry SDK...
Adds instructions for using other Nx Executors (Angular builders), especially for the esbuild-browser executor. Also rewords the guide a bit that the purpose of step one is to enable registering...
⚠️ Only merge when v8 is stable Updates SvelteKit docs to reflect Vite plugin 2.x bump. Also added a bunch of code block highlights - great stuff @a-hariti!
### Core or SDK? Platform/SDK ### Which part? Which one? @sentry/angular-ivy ### Description Since Angular 16 (I belive), entire Angular applications can created without declaring a single `NgModule`, by [only...
Our wizard should inject a commented `spotlight: true` flag to enable sending events from the SDK to the spotlight sidecar: ```js Sentry.init({ dsn: '...', //... // uncomment this to enable...
Right now, in the wizard we're still generating the old, user-scoped auth tokens. We recently introduced [Org-scoped auth tokens](https://github.com/getsentry/team-sdks/issues/6) which should be preferred over user-based tokens whenever possible. We therefore...
According to our documentation (e.g.[Readme](https://github.com/getsentry/sentry-wizard#options)), the wizard supports a few CLI args across the individual integration flows. This however is no longer true in the modern, clack-based wizard flows (Next,...
### Environment Latest source maps or sveltekit wizard. Note version is irrelevant. ### Steps to Reproduce 1. Create this config file: ```typescript // vite.config.ts import { somePlugin1, somePlugin2 } from...