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

@lareys/laxa-ui

v0.1.0

Published

Host shadcn UI primitives for authoring Laxa admin panel plugins. Maps to the host's window.LaxaUI at build time.

Readme

@lareys/laxa-ui

Host shadcn UI primitives for authoring Laxa admin-panel plugins.

A distributed (Composer-packaged, dist-built) plugin can't bundle its own copy of the host's shadcn components without shipping a second React tree and duplicate styles. This package is a thin shim: at build time your plugin externalizes it to the host's window.LaxaUI global, so import { Button } from '@lareys/laxa-ui' resolves to the host's single live component instead of a bundled duplicate.

import { Button, Card, CardContent } from '@lareys/laxa-ui';

export default function MyPluginPage() {
    return (
        <Card>
            <CardContent>
                <Button variant="outline">Host UI button</Button>
            </CardContent>
        </Card>
    );
}

Build setup

The laxa:plugin scaffold wires this up for you. In a hand-rolled plugin build, externalize the module and map it to the window.LaxaUI global:

// vite.config.ts (library mode)
rollupOptions: {
    external: ['react', 'react-dom', '@lareys/laxa-extensions', '@lareys/laxa-ui'],
    output: {
        globals: {
            react: 'React',
            'react-dom': 'ReactDOM',
            '@lareys/laxa-extensions': 'window',
            '@lareys/laxa-ui': 'window.LaxaUI',
        },
    },
},

What's included

A curated set of lightweight primitives: Accordion, Alert, AlertDialog, Avatar, Badge, Button, Card, Checkbox, Dialog, DropdownMenu, Input, Kbd, Label, Popover, Progress, RadioGroup, Select, Separator, Sheet, Skeleton, Slider, Spinner, Switch, Table, Tabs, Textarea, Tooltip (and their sub-components / variant helpers).

Components with heavy transitive dependencies are intentionally not exposed, so the host's eager bundle stays lean: chart (recharts), calendar (react-day-picker), carousel (embla), command / combobox (cmdk / @base-ui), code-editor, drawer (vaul), resizable, input-otp, and sidebar. A plugin that needs one of those should bundle it directly.

In-app extensions (built with the host via @lareys/laxa-vite-plugin) are unaffected — they import any component directly through the @laxa/ui/* alias.