usetraceforge-cli 0.1.8 → 0.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -60,6 +60,7 @@ ${folderStructure}
|
|
|
60
60
|
|
|
61
61
|
Here is the documentation for usetraceforge:
|
|
62
62
|
- Next.js 15+ Server: Create 'instrumentation.ts' (or 'src/instrumentation.ts') exporting 'register' and 'onRequestError(err, request)' which calls 'TraceForge.captureException(err, { tags: { route: request.url } })'.
|
|
63
|
+
- Next.js App Router API Routes: If developers use try/catch in their API routes, they must wrap their route export with 'withTraceForgeRoute' from 'usetraceforge/next' to auto-initialize and catch errors (e.g. 'export const GET = withTraceForgeRoute(async (req) => { ... })').
|
|
63
64
|
- Next.js Client: Wrap your app with '<TraceForgeProvider>' from 'usetraceforge/react'.
|
|
64
65
|
- Express: Call 'app.use(TraceForge.expressErrorHandler())' AFTER all routes but BEFORE custom error handlers.
|
|
65
66
|
- Initialization: You must always call 'TraceForge.init({ apiKey, endpoint })' as early as possible.
|