← All platforms

Solid error tracking

Fine-grained reactivity. A clear report when something breaks. Use the Sentry Solid SDK to keep component error reports on your Telebugs server.

~/hoofnotes  npm install @sentry/solid
~/hoofnotes  nvim src/index.tsx
import * as Sentry from "@sentry/solid";
Sentry.init({
// Copy the complete Telebugs DSN, key and path included.
dsn: "YOUR_TELEBUGS_DSN",
});
import { render } from "solid-js/web";
import { ErrorBoundary } from "solid-js";
import App from "./App";
const ReportingBoundary = Sentry.withSentryErrorBoundary(ErrorBoundary);
render(() => (
<ReportingBoundary fallback={<p>We couldn’t open your notes</p>}>
<App />
</ReportingBoundary>
), document.getElementById("app")!);
~/hoofnotes  npm run dev

Hang on, I already use Sentry

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

Can the error boundary show a fallback and report?

Yes. Sentry’s wrapper connects Solid’s error boundary to the SDK. Your visitor gets a fallback while the exception goes to Telebugs.

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.