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

@netpulse/tracing

v2.1.1

Published

Backend monitoring to generate Next.js trace data for server side api and database calls

Downloads

2

Readme

NetPulse: Next.js Server Side Observability

Getting Started

Install the following two NetPulse npm packages:

npm install @netpulse/tracing @netpulse/dashboard

Create a tracing.js file in the root directory of your project.

Add the following code to tracing.js:

const tracing = require('@netpulse/tracing');
tracing();

Inside the app or pages directory (depending on if you are using beta) create a file Dashboard.tsx and add the following code:

'use client';
import dynamic from 'next/dynamic';
const DashboardUI = dynamic(() => import('@netpulse/dashboard'), { ssr: false });
export default function Home() {
    return <DashboardUI/>;
}

Finally, in your package.json add the following start script:

"tracing": "node --require ./tracing.js ./node_modules/.bin/next dev"

You can now run your Next.js application:

npm run tracing

Open http://localhost:3000/Dashboard in the browser to view traces related to server side api calls and NoSQL / SQL database calls.

Notes

API Compatibility:

  • node-fetch
  • xmlHttpRequest
  • Node HTTP

Note: The current version of Next.js (13.2.4) uses an older version of node-fetch. As such, node-fetch (>=3.3.1) must be manually installed and imported into components that require monitoring of fetch calls

Database Compatibility:

  • MongoDB (Mongoose): >=5.9.7 <7
  • Postgresql (Pg): >=8 <9

Coming soon

As an open source project we are open to pull requests or feature requests from the developer community!

Currently prioritized features:

  • Dashboard containerization through DockerHub
  • Compatiblity with additional databases / drivers
  • Compatability with native Next.js fetch
  • Build tool update for better compatibility with ES modules (Non-dynamic import of Dashboard)