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

my-next-plugin

v1.0.6

Published

Mon plugin Next.js

Readme

my-next-plugin

Plugin Next.js avec composants Tailwind CSS (sans dépendance Tailwind)

Installation

npm install my-next-plugin

Configuration Tailwind CSS

Ce plugin utilise des classes Tailwind CSS mais ne contient pas Tailwind comme dépendance. Vous devez configurer Tailwind dans votre application pour scanner les fichiers du plugin.

Option 1 : Configuration dans tailwind.config.ts (Recommandé)

Ajoutez le chemin du plugin dans votre tailwind.config.ts :

import type { Config } from 'tailwindcss';

const config: Config = {
  content: [
    // Vos fichiers existants
    './src/**/*.{js,ts,jsx,tsx,mdx}',
    './app/**/*.{js,ts,jsx,tsx,mdx}',
    // Ajoutez cette ligne pour scanner le plugin
    './node_modules/my-next-plugin/dist/**/*.{js,jsx,ts,tsx}',
  ],
  theme: {
    extend: {},
  },
};

export default config;

Option 2 : Configuration dans le CSS (Tailwind v4)

Si vous utilisez Tailwind CSS v4, vous pouvez aussi utiliser la directive @source dans votre fichier CSS :

@import "tailwindcss";

@source "./node_modules/my-next-plugin/dist";

Utilisation

import { MyComponent, AnotherComponent } from 'my-next-plugin';

export default function Page() {
  return (
    <div>
      <MyComponent />
      <AnotherComponent />
    </div>
  );
}

Développement

# Build
npm run build

# Watch mode
npm run watch:all

Structure

my-next-plugin/
├── src/
│   ├── components/
│   │   ├── MyComponent.tsx
│   │   └── AnotherComponent.tsx
│   └── index.tsx
├── dist/           # Fichiers compilés
└── package.json

Notes importantes

  • Ce plugin ne compile pas de CSS Tailwind
  • Les classes Tailwind utilisées dans les composants seront compilées par votre application
  • Assurez-vous que Tailwind est configuré dans votre projet pour scanner node_modules/my-next-plugin/dist