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

@tandem-language-exchange/web-ui

v1.0.19

Published

Tandem Web UI Library

Readme

@tandem-language-exchange//web-ui

A React (with TypeScript) Component Library used for all Tandem Web Projects. This library is react meta-framework agnostic.


Storybook

The Private storybook can be viewed here: https://storybook.devtandem.net/


Installation

Install the private package from NPM by running the following command:

npm install @tandem-web/web-ui

You will need to have a .npmrc file with the npm token added to instal this package

Usage

Add SCSS files

Add the following to your global app tsx file (_app or root layout). It contains all the CSS token variables

@import '@tandem-web/web-ui/dist/styles/_tokens.scss';

In the _variables.scss, or any other scss file that you import into all other scss files, import the global partials file, containing all the necessary scss variables & mixins

@import '@tandem-web/web-ui/dist/styles/_config.scss';

Add the following to your global scss file. It contains all the base & reset styles. These are all non-pure selectors so it cannot be imported in a scss module.

@import '@tandem-web/web-ui/dist/styles/_base.scss';

Add Global Types

The UI Library relies on global types that need to be included. In the global.d.ts file of the consuming project, add the follwoing at the top:

/// <reference types="@tandem-web/web-ui/dist/global.d.ts" />

Update Synced Assets

This package also has certain static assets that need to be synced to the static directory if the consuming project.

This can be done by adding the following command to your package.json scripts:

"sync-assets": "sync-assets path=public/static"

The files will be saved inside a shared directory inside the path you provided

It is best practice to include this in your dev and prebuild scripts

Add Theme Provider

In your _app or root layout, wrap all the consuming components inside the ThemeProvider component

import { ThemeProvider } from '@tandem-web/web-ui';

<ThemeProvider
    defaultTheme="dark"
    localStorageKey="your_localStorage_key"
  >
    {children}
  </ThemeProvider>

Publishing Changes

This package requires an .npmrc file in the root of the project to authorize publishing changes to NPM. See docs.

To publish changes to this package:

  1. Make the relevant changes
  2. Increment the version number in the package.json
  3. Commit the changes & push to the remote origin
  4. Run npm publish

Should you get a 403 or 404, it can be that the token you specified in the .npmrc file is not valid or does not have write permissions. Sometimes the npm cli throws an error even if the changes are published. Juts wait a few seconds and refresh the for this package on NPM to see if the version umber incremented