feat: nextjs integration #1030
Merged
feat: nextjs integration #1030
Task list completed / task-list-completed
Started
2023-12-01 17:52:29
ago
14 / 15 tasks completed
1 task still to be completed
Details
Required Tasks
| Task | Status |
|---|---|
| server integration | Incomplete |
| client integration | Incomplete |
| source map upload | Incomplete |
| Publish alpha version of the package so it can be installed on a Vercel deployment | Completed |
| Webpack config to configure Honeybadger based on runtime | Completed |
| Honeybadger Edge API client (Server client may not work) - made it work with the browser client | Completed |
| Source map upload with webpack plugin | Completed |
| Tests | Incomplete |
| README.md | Completed |
| Documentation - include known limitations | Completed |
| cli command to generate config files | Completed |
| Manual Testing with deployments to Vercel | Completed |
| Manual Testing with deployments to Heroku | Completed |
| Manual Testing with deployments to self-hosted server (?) | Completed |
| Add @honeybadger-io/nextjs in pull-package-versions workflow | Completed |
| Create issues on github to address limitations (#1055, #1056) | Completed |
| Verify that HoneybadgerErrorBoundary React component provides additional React contextual information | Completed |
| Update nextjs example repo to use this package - honeybadger-io/nextjs-with-honeybadger#13 | Completed |
| The HB client can now report errors either from server, browser or vercel edge. | Incomplete |
| However, it won't always work because of some strange caveats of Nextjs/Vercel. For example, this one makes it difficult to report an error that comes from an error thrown in an api route, because Nextjs renders a 404 status code 🤷 . Additionally, there is no information about the error at all. As a result, a different way is to be implemented to handle those cases, which I plan to do with a separate issue/PR. | Incomplete |
Loading