npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@honeybadger-io/nextjs

v5.9.10

Published

Next.js integration for Honeybadger

Downloads

11,236

Readme

Honeybadger Next.js Integration

Node CI npm version npm dm npm dt

Documentation and Support

For comprehensive documentation and support, check out our documentation site.

The documentation includes a detailed Next.js integration guide.

Project Goals

The goal is to provide an idiomatic, simple integration of Honeybadger's exception monitoring service with Next.js applications.

Project Status

This version is considered suitable for preview.

Features

  • Automatic reporting of uncaught exceptions (see Limitations)
  • Breadcrumbs
  • Source map upload to Honeybadger
  • CLI command to generate Honeybadger configuration files for Next.js runtimes

Limitations

The following limitations are known to exist and will be tackled in future releases:

  • Issue link: A custom error component is used to report uncaught exceptions to Honeybadger. This is necessary because Next.js does not provide a way to hook into the error handler. This is not a catch-all errors solution.
    If you are using the Pages Router, there are some caveats to this approach, as reported here. This is a limitation of Next.js, not Honeybadger's Next.js integration. Errors thrown in middlewares or API routes will not be reported to Honeybadger, since when they reach the error component, the response status code is 404 and no error information is available. Additionally, there is an open issue about 404 being reported with Next.js apps deployed on Vercel, when they should be reported as 500.
    If you are using the App Router, these limitations do not apply, because errors thrown in middlewares or API routes do not reach the custom error component but are caught by the global window.onerror handler. However, some other server errors (i.e. from data fetching methods) will be reported with minimal information, since Next.js will send a generic error message to this component for better security.
  • Issue link: Source maps for the Edge runtime are not supported yet.

Example app

A separate repository, nextjs-with-honeybadger exists with an example app using this package. Follow the README instructions to run the example app.

Development

# install dependencies
npm install

# build for production
npm run build

License

This package is MIT licensed. See the MIT-LICENSE file in this folder for details.