You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/js/examples/chrome-extension/README.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,9 @@ In the <strong>Extensions</strong> page (`chrome://extensions`), click on the re
22
22
There are multiple ways to report an error, showcasing the different execution contexts in a chrome extension:
23
23
- An error is automatically reported from the background worker (`background.js`) as soon as it's loaded. This is how you know Honeybadger was loaded successfully in the worker.
24
24
- An error is automatically reported from the content script (`content.js`) as soon as it's loaded. This is how you know Honeybadger was loaded successfully in the content script.
25
-
- To report an error from the options page (`options.html` and `options.js`):
25
+
- To report an error from the options page (`options.html` and `options.js`) or the popup (`popup.html` and `popup.js`):
26
26
1. Open `error-reporting.js` and replace `YOUR_API_KEY` with your Honeybadger.js API key.
27
27
2. Make sure to reload the extension (see above).
28
28
3. Open the Options page and click on the Report Error button.
29
+
Or click on the extension icon to open the popup and click on the Report Error button.
29
30
4. Check your Honeybadger.js dashboard. The error should show up after a few seconds.
0 commit comments