← All platforms

SolidStart error tracking

Solid in the browser. Server rendering behind it. Use the Sentry SolidStart SDK to bring errors from both sides to your Telebugs server.

~/hoofnotes  npm install @sentry/solidstart
~/hoofnotes  nvim src/entry-client.tsx src/instrument.server.ts src/middleware.ts app.config.ts
import * as Sentry from "@sentry/solidstart";
Sentry.init({
// Copy the complete Telebugs DSN, key and path included.
dsn: "YOUR_TELEBUGS_DSN",
});
import { mount, StartClient } from "@solidjs/start/client";
mount(() => <StartClient />, document.getElementById("app")!);
import * as Sentry from "@sentry/solidstart";
Sentry.init({
// Copy the complete Telebugs DSN, key and path included.
dsn: "YOUR_TELEBUGS_DSN",
});
import { sentryBeforeResponseMiddleware } from "@sentry/solidstart";
import { createMiddleware } from "@solidjs/start/middleware";
export default createMiddleware({
onBeforeResponse: [sentryBeforeResponseMiddleware()],
});
import { withSentry } from "@sentry/solidstart";
import { defineConfig } from "@solidjs/start/config";
export default defineConfig(withSentry({
middleware: "./src/middleware.ts",
}));
~/hoofnotes  npm run dev

Hang on, I already use Sentry

Keep @sentry/solidstart and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.

Does server rendering have its own connection?

Yes. SolidStart’s SDK has client initialization and server instrumentation. Reports from either side can reach Telebugs, with the backtrace captured where the error happened.

Can a Solid error boundary report too?

Yes. The SDK’s withSentryErrorBoundary wrapper connects a Solid error boundary to reporting. You keep control of the fallback shown to visitors.

Will I recognize my source code?

Yes. Give Telebugs the matching source maps and it can show your original files and line numbers instead of a minified backtrace.