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

@memobit/themes

v1.0.3

Published

65 themes for the Memobit apps — each published as its own stylesheet so an app loads only the one it is showing, with preview palettes for the theme picker.

Readme

@memobit/themes

64 themes for the Memobit apps. Each is published as its own stylesheet, so an app loads only the one it is showing instead of all of them.

Extracted from @memobit/libs in v3.0.0 of that library.

Why

Themes used to ship as a single aggregate stylesheet that every app imported wholesale — ~618 KB of which exactly one theme is ever active. Splitting them took one app's CSS from 866 KB to 295 KB.

Install

npm install @memobit/themes

Usage

Add the Vite plugin. It emits each theme as a separate asset and tells @memobit/libs where to find them, so ThemeProvider fetches the selected theme and nothing else.

import { memobitThemes } from '@memobit/themes/vite';

export default defineConfig({
    plugins: [react(), memobitThemes({ root: __dirname })],
});

Without the plugin nothing breaks: the library falls back to assuming the aggregate stylesheet was imported the old way.

import '@memobit/themes/themes.css';

Note that the aggregate no longer pulls in base.scss and scrollbars.scss. Those are not themes, they stay in @memobit/libs, and an app must import them directly:

import '@memobit/libs/dist/styles/base.scss';
import '@memobit/libs/dist/styles/scrollbars.scss';

Exports

import {
    FAVORITE_THEMES,
    getThemeAppearance,
    getThemeConfig,
    LIGHT_THEMES,
    previewPalettes,
    THEME_CONFIGS,
} from '@memobit/themes';

previewPalettes holds the six colours the theme picker needs to draw a swatch for a theme whose stylesheet is not loaded. It is generated from the compiled CSS, because ten themes build their tokens through the _profile-theme mixin rather than declaring them literally.

Adding a theme

  1. Add src/theming/<name>.scss, scoped to [data-theme='<name>'].
  2. Add a @use line in src/themes.scss.
  3. Add an entry to THEME_CONFIGS in src/themeConfig.ts, with its font URLs.
  4. Add it to LIGHT_THEMES if it is a light theme.
  5. Run npm run build — the per-theme stylesheet and its preview palette are generated.

The build fails if a theme is missing any of the six preview tokens, so a new theme cannot ship with a broken swatch.

License

Apache-2.0