No crash reporting

This is the no-op crash option: no SDK, no DSN, nothing leaving the device. It owns src/lib/crash.ts as a re-export of the core shim, so @/lib/crash keeps the same API whichever option you pick - crash.capture(err, ctx) does nothing beyond a console.error in dev. Pick this while you're building alone; pick Sentry before real users can hit a bug you can't reproduce.

SetupCopy Anchor Link

bun run setup --crash none

There's nothing to configure and no keys to paste.

When you want the reports, switch with bun run setup --crash sentry.

UsageCopy Anchor Link

The call exists and is safe to write today, so screens don't need rewriting when you switch:

import { crash } from "@/lib/crash";

crash.capture(err, { screen: "checkout", orderId }); // logs in dev, no-op otherwise

GotchasCopy Anchor Link

• The shim has no CrashBoundary, so don't import one - that component comes with crash/sentry. An unhandled render error takes down the tree it's in.
• Nothing here needs a dev build; Expo Go is fine.

ReferenceCopy Anchor Link

Everything below is generated from modules/crash/none/module.json - the same file bun run setup reads, so it is what actually lands in your repo.

InstallCopy Anchor Link

bun run setup --crash none

Module id: crash/none.

FilesCopy Anchor Link