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

@flusterduck/nuxt

v0.5.2

Published

Flusterduck Nuxt module

Readme

@flusterduck/nuxt

Nuxt integration for Flusterduck. Provides a plugin factory for app-level initialization and standalone tracking functions for use in components and composables.

Installation

npm install flusterduck @flusterduck/nuxt

Setup

Create a Nuxt plugin that initializes Flusterduck on the client side. createFlusterduckPlugin returns a plugin function, so export it directly:

// plugins/flusterduck.client.ts
import { createFlusterduckPlugin } from '@flusterduck/nuxt';

export default createFlusterduckPlugin({
  key: 'fd_pub_...',
  environment: process.env.NODE_ENV,
});

The .client.ts suffix ensures this plugin only runs in the browser. The plugin also guards against SSR on its own, so a missing suffix degrades to a no-op rather than an error.

Initialization goes through the npm SDK only. Don't add the d.js script tag alongside this plugin; the two hold separate state and would double-track every visitor.

Configuration helper

Use defineFlusterduckConfig to build a typed config object for reuse:

// flusterduck.config.ts
import { defineFlusterduckConfig } from '@flusterduck/nuxt';

export default defineFlusterduckConfig({
  key: 'fd_pub_...',
  environment: 'production',
  sampleRate: 1,
  cookieless: false,
});

Tracking in components

<script setup lang="ts">
import { signal, track, identify } from '@flusterduck/nuxt';

function onPayClick() {
  signal('checkout_error', { element: '#pay-btn' });
}

function onPlanSelect(plan: string) {
  track('plan_selected', { plan });
  identify({ plan });
}
</script>

Consent

import { setConsent, optOut } from '@flusterduck/nuxt';

setConsent(true);
optOut();

API

defineFlusterduckConfig(options: NuxtFlusterduckOptions): NuxtFlusterduckOptions
createFlusterduckPlugin(options: NuxtFlusterduckOptions): () => Promise<void>
signal(name: string, data?: { element?: string; metadata?: Record<string, unknown>; weight?: number }): void
track(name: string, metadata?: Record<string, unknown>): void
identify(segment: Record<string, string>): void
setConsent(consented: boolean): void
optOut(): void

All Config options from the core flusterduck package are supported.