7 |
8 | export default Test4
9 |
--------------------------------------------------------------------------------
/pages/client/test5.js:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 |
3 | // This code will run just fine on the server in Node.js, but process will be
4 | // undefined in a browser. Note that `isProd = process.env.NODE_ENV` would have
5 | // worked because Webpack's DefinePlugin will replace it with a string at build
6 | // time: https://nextjs.org/docs#build-time-configuration
7 | const env = process.env
8 | const isProd = env.NODE_ENV === 'production'
9 |
10 | const Test5 = () => (
11 |
12 |
7 | This example demonstrates how to record unhandled exceptions in your code
8 | with Honeybadger. There are several test pages below that result in various
9 | kinds of unhandled exceptions.
10 |
11 |
12 | Important: exceptions in development mode take a
13 | different path than in production. These tests should be run on a
14 | production build (i.e. 'next build').{' '}
15 | Read more
16 |
17 |
18 |
Server exceptions
19 |
20 |
21 | getInitialProps throws an Error. This should cause _error.js to render
22 | and record Error('Server Test 1') in Honeybadger.{' '}
23 |
24 | Open in a new tab
25 |
26 |
27 |
28 | getInitialProps returns a Promise that rejects. This should cause
29 | _error.js to render and record Error('Server Test 2') in Honeybadger.{' '}
30 |
31 | Open in a new tab
32 |
33 |
34 |
35 | getInitialProps calls a Promise that rejects, but does not handle the
36 | rejection or await its result (returning synchronously).{' '}
37 | Honeybadger shouldrecord Error('Server Test 3').{' '}
38 |
39 | Open in a new tab
40 |
41 |
42 |
43 | There is a top-of-module Promise that rejects, but its result is not
44 | awaited. Honeybadger should record Error('Server Test 4'). Note this will
45 | also be recorded on the client side, once the page is hydrated.{' '}
46 |
47 | Open in a new tab
48 |
49 |
50 |
51 |
52 |
Client exceptions
53 |
54 |
55 | getInitialProps throws an Error. This should cause _error.js to render
56 | and record Error('Client Test 1') in Honeybadger.{' '}
57 |
58 | Perform client side navigation
59 |
60 |
61 |
62 | getInitialProps returns a Promise that rejects. This should cause
63 | _error.js to render and record Error('Client Test 2') in Honeybadger.{' '}
64 |
65 | Perform client side navigation
66 |
67 |
68 |
69 | getInitialProps calls a Promise that rejects, but does not handle the
70 | rejection or await its result (returning synchronously). Honeybadger should
71 | record Error('Client Test 3').{' '}
72 |
73 | Perform client side navigation
74 |
75 |
76 |
77 | There is a top-of-module Promise that rejects, but its result is not
78 | awaited. Honeybadger should record Error('Client Test 4').{' '}
79 |
80 | Perform client side navigation
81 | {' '}
82 | or{' '}
83 |
84 | Open in a new tab
85 |
86 |
87 |
88 | There is a top-of-module exception. _error.js should render and record
89 | ReferenceError('process is not defined') in Honeybadger.{' '}
90 |
91 | Perform client side navigation
92 | {' '}
93 | or{' '}
94 |
95 | Open in a new tab
96 |
97 |
98 |
99 | There is an exception during React lifecycle that is caught by
100 | Next.js's React Error Boundary. In this case, when the component
101 | mounts. This should cause _error.js to render and record Error('Client
102 | Test 6') in Honeybadger.{' '}
103 |
104 | Perform client side navigation
105 | {' '}
106 | or{' '}
107 |
108 | Open in a new tab
109 |
110 |
111 |
112 | There is an unhandled Promise rejection during React lifecycle. In
113 | this case, when the component mounts. Honeybadger should record
114 | Error('Client Test 7').{' '}
115 |
116 | Perform client side navigation
117 | {' '}
118 | or{' '}
119 |
120 | Open in a new tab
121 |
122 |
123 |
124 | An Error is thrown from an event handler. Honeybadger should record
125 | Error('Client Test 8').{' '}
126 |
127 | Perform client side navigation
128 | {' '}
129 | or{' '}
130 |
131 | Open in a new tab
132 |
133 |