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

@vitral/nuxt

v0.2.0

Published

The Nuxt module for Vitral: the plugin from nuxt.config, auto-imported components and composables, the theme rendered on the server and the colour scheme in a cookie.

Readme

@vitral/nuxt

The Nuxt module for Vitral.

pnpm add @vitral/nuxt @vitral/vue
export default defineNuxtConfig({
    modules: ['@vitral/nuxt'],
    vitral: { preset: 'Prism', colorScheme: 'system' }
});

That is the whole setup. <VtButton>, <VtInputText>, useTheme() and the rest are auto-imported, the stylesheets go into the head of the page the server sends, and the colour scheme is kept in a cookie so the server renders the one the reader picked instead of flashing the wrong one.

| Option | What it does | | ------ | ------------ | | preset | A shipped preset by name ('Prism', 'Ink', 'Avalonia', 'Simple', 'Astra'), a module that default-exports one, or false | | colorScheme | 'light', 'dark' or 'system' | | cookie | Where the reader's choice is kept, so the server can read it. false forgets it | | darkModeSelector | Where the dark scheme applies: a class, an attribute, 'system' or false | | locale | 'en', 'ptBR', or a module that default-exports a locale | | prefix | The prefix on registered components. 'Vt' by default, '' for <Button> | | components, composables | Register them globally. Off means importing by hand | | cssLayer, inputVariant, unstyled | The same options the Vue plugin takes |

Directives keep their plain names (v-tooltip), because they are registered on the application rather than auto-imported.

Documentation

LGPL-3.0-or-later. Part of the Vitral monorepo.