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

@shoptet/ui

v0.18.1-beta

Published

This repository contains a collection of reusable React components that are purely visual. These components are designed to be used across multiple projects and should not handle data fetching, routing, or translations.

Readme

Reusable UI Library

This repository contains a collection of reusable React components that are purely visual. These components are designed to be used across multiple projects and should not handle data fetching, routing, or translations.

Caution: This is an early-stage development version of the Shoptet UI kit package

Please be aware that this version may contain bugs, incomplete features, or undergo significant changes before reaching a stable release. Use it at your own risk and for testing and development purposes only. Your feedback and contributions are appreciated to help improve the stability and functionality of the package. Refer to the documentation and release notes for more information on the current state of development. Thank you for your understanding.

Storybook

We have written a Storybook for the components to demonstrate how to use them.

The internal public version is currently available here: https://react.shoptet.cz/

Localization

The components come with a built-in localization in 8 languages: cs-CZ, de-DE, en-US, hu-HU, pl-PL, ro-RO, sk-SK, and vi-VN. It is necessary to wrap your application with the LocalizationProvider component from the library and provide the locale prop with one of the supported locales.

Bundling

This library is build on top of @react-aria which includes localized messages for various languages. In order to avoid bundling all the languages some of which you might not need, you can define your own build plugin to strip away the translations. Here is an example of such a vite plugin:

export const uiTranslations = ({ locales }: Options): Plugin => {
  const intlLocales = locales.map(l => new Intl.Locale(l));

  return {
    name: 'vite-plugin-ui-translations',
    transform(_, id) {
      if (!id || !/[/\\](@react-stately|@react-aria|@react-spectrum|react-aria-components)[/\\]/.test(id)) {
        return;
      }

      const match = id.match(/[a-z]{2}-[A-Z]{2}/);

      if (match) {
        const locale = new Intl.Locale(match[0]);
        if (!intlLocales.some(l => localeMatches(locale, l))) {
          return {
            code: `export default {};`,
            map: null,
          };
        }
      }

      return;
    },
  };
};

function localeMatches(localeToMatch: Intl.Locale, includedLocale: Intl.Locale) {
  return (
    localeToMatch.language === includedLocale.language &&
    (!includedLocale.region || localeToMatch.region === includedLocale.region)
  );
}

And then you can use it in your vite.config.ts like this:

import { defineConfig } from "vite";
import { uiTranslations } from './vite-plugin-ui-translations';

export default defineConfig({
  plugins: [
    uiTranslations({
      locales: ["en-US", "cs-CZ"], // Specify the locales you want to bundle
    }),
  ],
});

Make sure not to set the library language to any of the locales you are stripping away, otherwise the library will not work properly.