The glitchtip module adds the Sentry SDK to apps/api (@sentry/bun) and to apps/web and apps/dashboard (@sentry/nextjs), pointed at a self-hosted GlitchTip. It is off by default.
findplate create my-app --modules glitchtipWhat it adds
Files and folders:
apps/web/instrumentation-client.tsapps/dashboard/instrumentation-client.ts
Lines in apps/web/instrumentation.ts and apps/dashboard/instrumentation.ts, which stay in every project as the hook other modules share.
Packages:
@sentry/bun@sentry/nextjs
Env keys
GLITCHTIP_DSN=
NEXT_PUBLIC_GLITCHTIP_DSN=GLITCHTIP_DSN is used on the server and NEXT_PUBLIC_GLITCHTIP_DSN in the browser, inlined at build. Empty means no events are sent. A compose file is in self-hosted tools.
Remove
Run findplate remove glitchtip in the project, see add and doctor. It deletes the files the module owns, strips its code from shared files and drops its packages, only where you haven't edited them.
If you'd rather do it by hand: for a new project leave glitchtip out of --modules. In a project that already exists, delete the paths above, drop its packages from the package.json files, remove its env block and fix what pnpm check-types reports.
Swap
GlitchTip speaks the Sentry protocol, so a Sentry project DSN works in the same two keys.