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

@titania/ui

v0.0.5

Published

Out of the box the components render English and need no i18n library. For multilingual sites you can opt in to [Paraglide](https://inlang.com/m/gerre34r/library-inlang-paraglideJs): all strings the components render (accessible names, sr-only status word

Readme

@titania/ui

Translations (optional)

Out of the box the components render English and need no i18n library. For multilingual sites you can opt in to Paraglide: all strings the components render (accessible names, sr-only status words, error counts) are messages prefixed ui_, compiled and tree-shaken together with your own messages at build time. The library adds no runtime i18n code of its own.

  1. Add the library's message files to your inlang project's pathPattern (project.inlang/settings.json):

    "plugin.inlang.messageFormat": {
    	"pathPattern": ["./messages/{locale}.json", "./node_modules/@titania/ui/messages/{locale}.json"]
    }
  2. Add the Vite plugin after Paraglide's, pointing at its generated messages module:

    import { titania } from '@titania/ui/vite';
    
    plugins: [
    	paraglideVitePlugin({ project: './project.inlang', outdir: './src/lib/paraglide' }),
    	titania({ messages: './src/lib/paraglide/messages.js' }),
    	sveltekit()
    ];

Switching the locale is then plain Paraglide (setLocale). Shipped locales: en, de. Messages live in messages/{locale}.json (inlang message format) and are compiled by the real Paraglide compiler (npm run paraglide, run automatically by dev, check and prepack). Add a locale by adding a messages/<locale>.json. Individual strings can still be overridden per instance (pendingLabel, statusLabel, title, announceErrors, aria-label).