@@ -9,8 +9,8 @@ export default function HomePage() {
99 < p className = "eyebrow" > Exceptionless for Next.js</ p >
1010 < h1 > Client and server monitoring for Next.js.</ h1 >
1111 < p >
12- This reference app keeps the setup small, but still captures the important Exceptionless signals across browser and
13- server paths: logs, handled errors, unhandled errors, request metadata, and App Router error boundaries.
12+ This reference app keeps the setup small, but still captures the important Exceptionless signals across browser and server paths: logs, handled
13+ errors, unhandled errors, request metadata, and App Router error boundaries.
1414 </ p >
1515 < div className = "hero-meta" >
1616 < span > Deployment target: { deploymentTarget } </ span >
@@ -25,9 +25,8 @@ export default function HomePage() {
2525 < div className = "panel-body" >
2626 < h2 > What the integration covers</ h2 >
2727 < p >
28- The client path uses browser startup plus route boundaries. The server path uses `onRequestError`, explicit queue
29- flushes, and a small request adapter so Exceptionless can attach rich request metadata to the same event builders we
30- already use elsewhere.
28+ The client path uses browser startup plus route boundaries. The server path uses `onRequestError`, explicit queue flushes, and a small request
29+ adapter so Exceptionless can attach rich request metadata to the same event builders we already use elsewhere.
3130 </ p >
3231 < ul className = "note-list" >
3332 < li > `instrumentation-client.js` starts Exceptionless before the app becomes interactive and logs route transitions.</ li >
0 commit comments