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

@onderwijsin/nuxt-tailwind-breakpoint

v0.1.0

Published

Nuxt UI badge showing the active Tailwind CSS breakpoint.

Readme

@onderwijsin/nuxt-tailwind-breakpoint

A fixed Nuxt UI badge showing the active Tailwind CSS breakpoint. It reads the application's computed --breakpoint-* CSS variables and reacts to viewport changes through VueUse.

Installation

Requires Node.js 24+, Nuxt 4, Nuxt UI 4, VueUse 14, Vue 3.5+, and Tailwind CSS 4.

pnpm add @onderwijsin/nuxt-tailwind-breakpoint @nuxt/ui @vueuse/core
export default defineNuxtConfig({
  modules: ["@onderwijsin/nuxt-tailwind-breakpoint"]
});

The module registers Nuxt UI as a module dependency. Follow Nuxt UI's normal application setup, including its CSS imports and <UApp> wrapper.

Usage

Place the auto-imported component once in your app or layout:

<template>
  <UApp>
    <NuxtPage />
    <TailwindBreakpoint />
  </UApp>
</template>

The component renders only on the client. It displays the largest matching breakpoint name, or base below the smallest breakpoint (also when no breakpoint variables are available). It uses a subtle neutral badge with the mdi:tailwind icon, fixed at the bottom left, ignores pointer events, and is hidden from assistive technology. Nuxt Icon must be able to resolve mdi:tailwind through its configured provider or local collection.

To show it only in development, use v-if="isDev" with const isDev = import.meta.dev in your app's <script setup>. An even simpler usage is with teh <DevOnly /> component:

<template>
  <UApp>
    <NuxtPage />
    <DevOnly>
      <TailwindBreakpoint />
    </DevOnly>
  </UApp>
</template>

Tailwind configuration

Tailwind normally omits unused theme variables. Emit your theme variables with theme(static) in the application's CSS so every breakpoint is available:

@import "tailwindcss" theme(static);
@import "@nuxt/ui";

@theme {
  --breakpoint-3xl: 120rem;
}

Custom breakpoint names are supported. Keep breakpoint units consistent, as required by Tailwind. Variables are read when the component mounts; runtime changes to breakpoint definitions require remounting it. There are no module options, custom props, or automatically injected overlays.