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

alpinejs-breakpoint

v1.0.1

Published

Alpine breakpoint plugin

Readme

Alpine.js Breakpoint Directive

A lightweight Alpine.js plugin that exposes CSS-like breakpoints directly to your Alpine components using a simple directive. It allows you to reactively track whether the viewport width matches a given breakpoint.

This plugin is framework-agnostic but pairs especially well with Tailwind-style breakpoint definitions.


Features

  • 📐 Reactive viewport breakpoint detection
  • ⚡ Minimal and lightweight
  • 🧩 Simple Alpine directive API
  • 🪄 Works with any breakpoint configuration (px, rem, em, etc.)
  • 🧼 Automatic cleanup on component removal

Installation

npm install alpinejs-breakpoint

or

yarn add alpinejs-breakpoint

Usage

1. Register the plugin

Import the plugin and register it with Alpine, passing your breakpoint configuration.

import Alpine from 'alpinejs';
import breakpoint from 'alpinejs-breakpoint';

Alpine.plugin(
    breakpoint({
        sm: '31.25rem',
        md: '43.75rem',
        lg: '62.5rem',
        xl: '87.5rem',
    })
);

Alpine.start();

💡 The values can be any valid CSS width units (px, rem, em, etc.).


2. Use the x-breakpoint directive

The directive syntax is:

x-breakpoint:<name>="<expression>"
  • <name> — the breakpoint key from your configuration
  • <expression> — an Alpine expression (usually a variable) that will be set to true or false

Example

<div
    x-data="{
        isSmall: false,
        isMedium: false,
        isLarge: false,
        isExtraLarge: false,
    }"
    x-breakpoint:sm="isSmall"
    x-breakpoint:md="isMedium"
    x-breakpoint:lg="isLarge"
    x-breakpoint:xl="isExtraLarge"
>
    <p><code>isSmall: <span x-text="isSmall"></span></code></p>
    <p><code>isMedium: <span x-text="isMedium"></span></code></p>
    <p><code>isLarge: <span x-text="isLarge"></span></code></p>
    <p><code>isExtraLarge: <span x-text="isExtraLarge"></span></code></p>
</div>

Each variable automatically updates when the viewport crosses its breakpoint threshold.


How It Works

  • Internally uses window.matchMedia() with modern range syntax:
(width >= breakpoint)
  • Evaluates immediately on initialization
  • Listens to resize events
  • Updates values with a small debounce (150ms)
  • Automatically removes event listeners when the element is destroyed

Notes

  • If a breakpoint name is not found in the configuration, the directive does nothing.
  • This plugin only checks minimum width (>=), similar to Tailwind's breakpoint behavior.
  • Designed for client-side usage only.