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

@tinytrack/nextjs

v0.1.5

Published

TinyTrack server-side analytics, first-party tracking endpoints, and automatic browser tracker injection for Next.js.

Readme

@tinytrack/nextjs

TinyTrack analytics with the tracker and events served through your own domain.

Requirements:

Install

1. Install tinytrack package

npm install @tinytrack/nextjs

2. Add the proxy

Next.js 16: create proxy.ts at the root of src/:

// src/proxy.ts
import { createTinyTrackProxy } from '@tinytrack/nextjs';

export const proxy = createTinyTrackProxy({ websiteId: 'your_website_id' });

export const config = {
	matcher: ['/((?!_next/static|_next/image).*)'],
};

Next.js 14+: use middleware.ts at root of src/ with a middleware export instead:

// src/middleware.ts
import { createTinyTrackMiddleware } from '@tinytrack/nextjs';

export const middleware = createTinyTrackMiddleware({ websiteId: 'your_website_id' });

export const config = {
	matcher: ['/((?!_next/static|_next/image).*)'],
};

Already have middleware or a proxy? Rename your existing handler to appMiddleware and wrap it using the named import:

import { withTinyTrackMiddleware } from '@tinytrack/nextjs';

export const middleware = withTinyTrackMiddleware(appMiddleware, {
	websiteId: 'your_website_id',
});

For proxy.ts, export proxy instead. Keep your existing matcher entries and add /_tinytrack/:path*.

3. Add the tracker

Choose your router and add the component once.

App Router

Add the tracker inside your existing server layout's <body>:

// app/layout.tsx
import type { ReactNode } from 'react';
import { TinyTrack } from '@tinytrack/nextjs/react';

export default function RootLayout({ children }: { children: ReactNode }) {
	return (
		<html lang="en">
			<body>
				{children}
				<TinyTrack websiteId="your_website_id" />
			</body>
		</html>
	);
}

Pages Router

Add the tracker alongside your page component:

// pages/_app.tsx
import type { AppProps } from 'next/app';
import { TinyTrack } from '@tinytrack/nextjs/react/client';

export default function App({ Component, pageProps }: AppProps) {
	return (
		<>
			<Component {...pageProps} />
			<TinyTrack websiteId="your_website_id" />
		</>
	);
}

Optional: environment variable

Omit websiteId from both the middleware and tracker, and set this in .env.local and your hosting environment before building:

TINYTRACK_WEBSITE_ID=your_website_id

Pages Router only: also add this env entry to your Next.js config so the tracker can read the ID in the browser:

// next.config.mjs
export default {
	env: { TINYTRACK_WEBSITE_ID: process.env.TINYTRACK_WEBSITE_ID },
};