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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@monoscopetech/next

v1.0.1

Published

<div align="center">

Readme

Monoscope's Logo Monoscope's Logo

NextJs SDK

APItoolkit SDK Join Discord Server APItoolkit Docs

APIToolkit NextJs Middleware is a middleware that can be used to monitor HTTP requests. It is provides additional functionalities on top of the open telemetry instrumentation which creates a custom span for each request capturing details about the request including request and response bodies.

Installation

Run the following command to install the neccessary package from your projects root:

npm install --save @monoscopetech/next @vercel/otel @opentelemetry/api

Setup Open Telemetry

Setting up open telemetry allows you to send traces, metrics and logs to the APIToolkit platform. Add the following environment variables to your .env file:

OTEL_EXPORTER_OTLP_ENDPOINT="http://otelcol.apitoolkit.io:4318"
OTEL_SERVICE_NAME="my-service" # Specifies the name of the service.
OTEL_RESOURCE_ATTRIBUTES="at-project-key=<YOUR_API_KEY>" # Adds your API KEY to the resource.
OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf" #Specifies the protocol to use for the OpenTelemetry exporter.

Then add the following to your intrumentation.ts|js file:

You can create the intrumentation.ts|js in the src directory of your project or root directory if you're not using a src directory.

import { registerOTel } from "@vercel/otel";

export function register() {
  registerOTel("<YOUR_PROJECT_NAME>");
}

HTTP Requests Monitoring

After setting up open telemetry. You can monitor http requests using APIToolkit's next middleware, this allows you to monitor all your http requests. including headers, response time, response status code, request body, response body, etc.

To monitor http requests, wrap your routes with the withMonoscopeAppRouter function if you're using the app router or withMonoscopePagesRouter if you're using the pages router.

Example App Router

import { withMonoscopeAppRouter } from "@monoscopetech/next";
import { NextRequest, NextResponse } from "next/server";
async function handleRequest(req: NextRequest) {
  return NextResponse.json({ message: "hello world" });
}

// Optional configuration
const config = {
  captureResponseBody: true,
  serviceName: "my-service",
}
export const GET = withMonoscopeAppRouter(handleRequest, config);

Example Pages Router

import type { NextApiRequest, NextApiResponse } from "next";
import { withMonoscopePagesRouter } from "@monoscopetech/next";

function handler(req: NextApiRequest, res: NextApiResponse) {
  res.status(200).json({ message: "Hello from Next.js!" });
}

// Optional configuration
const config = {
  captureResponseBody: true,
  serviceName: "my-service",
}

export default withMonoscopePagesRouter(handler, config);

Quick overview of the configuration parameters

An object with the following optional fields can be passed to the middleware to configure it:

| Option | Description | | --------------------- | ------------------------------------------------------------------------------------------------- | | debug | Set to true to enable debug mode. | | serviceName | A defined string name of your application. | | tags | A list of defined tags for your services (used for grouping and filtering data on the dashboard). | | serviceVersion | A defined string version of your application (used for further debugging on the dashboard). | | redactHeaders | A list of HTTP header keys to redact. | | redactResponseBody | A list of JSONPaths from the response body to redact. | | redactRequestBody | A list of JSONPaths from the request body to redact. | | captureRequestBody | Default false, set to true if you want to capture the request body. | | captureResponseBody | Default false, set to true if you want to capture the response body. |

[!IMPORTANT]

To learn more configuration options (redacting fields, error reporting, outgoing requests, etc.) and complete integration guide, please read this SDK documentation.