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 🙏

© 2026 – Pkg Stats / Ryan Hefner

nuxt-newrelic

v1.0.1

Published

Nuxt module to integrate New Relic

Readme

Nuxt New Relic

This Nuxt module provides a better integration with New Relic.

Features

  • Naming transactions based on the path of the request
  • Providing newrelic agent with error objects

Setup

Installation

  1. npx nuxi module add nuxt-newrelic
  2. npm run build
  3. Create and copy a New Relic licence key here and decide on a app name.

Configure newrelic agent

There are two ways to configure the newrelic agent:

ENV variables (recommended)

Set the NEW_RELIC_APP_NAME and NEW_RELIC_LICENSE_KEY ENV variables so that node has access to them.

newrelic.cjs in root

  • cp node_modules/newrelic/newrelic.js ./newrelic.cjs
  • In the new file newrelic.cjs set app_name and license_key accordingly.

You can also mix the two approaches. You could configure the agent in newrelic.cjs and just set the licence key using a ENV variable.

Running Nuxt with the newrelic agent

Run our application using one of the following options:

Testing

Test your setup by providing the ENV variables direclty when runing node:

NEW_RELIC_LICENSE_KEY=XXXXXX NEW_RELIC_APP_NAME=APPNAME node --experimental-loader newrelic/esm-loader.mjs -r newrelic .output/server/index.mjs

You can use this to test your setup locally.

Prodction

Set the env variables so that they are available to node and run.

node --experimental-loader newrelic/esm-loader.mjs -r newrelic .output/server/index.mjs

This is recommended to use in production.

Limitations

  • Currently only works when using newrelic like recommended way of installing the newrelic agent by running nuxt using something like node -r newrelic ./.output/server/index.mjs
  • The --experimental-loader newrelic/esm-loader.mjs flag is required, since we need to import the newrelic agent. That is needed according to the docs.

Roadmap

  • Instrument Nuxt
  • Source maps
  • Exclude expected errors (4xx)
  • Disable default error tracking since there is basically no information available
  • Write tests

Contribution

# Install dependencies
npm install

# Generate type stubs
npm run dev:prepare

# Develop with the playground
npm run dev

# Build the playground
npm run dev:build

# Run ESLint
npm run lint

# Run Vitest
npm run test
npm run test:watch

# Release new version
npm run release