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

@curvenote/styles

v2.2.1

Published

Shared CSS and Tailwind theme extensions for Curvenote apps, including a vendored copy of @myst-theme/styles

Readme

@curvenote/styles

Shared CSS and Tailwind theme extensions for the Curvenote apps.

  • index.css — the stylesheet entry every app imports.
  • theme-extensions.cjs — grid templates, column names, keyframes and animations that the CSS @applys. Previously copy-pasted into all nine app configs.
  • theme.css — Tailwind @theme inline mappings binding --color-* tokens to the palette.
  • colors.css — the default light/dark palette (:root and .dark).
  • typography.cjs — proseCss(), the shared @tailwindcss/typography rules.
  • myst/ — a vendored copy of @myst-theme/styles. See UPSTREAM.md.

There is no build step; the files are consumed as source.

Using it

In an app's app/app.css:

@import '@curvenote/styles/index.css';
@import '@curvenote/styles/theme.css';
@import '@curvenote/styles/colors.css';

Add brand colors after the import, and map them into Tailwind:

:root {
  --curvenote-blue: #235f9c;
}
.dark {
  --curvenote-blue: #5da8e6;
}
@theme inline {
  --color-curvenote-blue: var(--curvenote-blue);
}

An app with a wholly different palette omits colors.css and defines its own :root and .dark — apps/packager is the only one that does.

In its tailwind.config.js:

const {
  gridTemplateColumns,
  gridColumn,
  keyframes,
  animation,
} = require('@curvenote/styles/theme-extensions');

module.exports = {
  theme: { extend: { gridTemplateColumns, gridColumn, keyframes, animation } },
};

Override individual keys where an app genuinely differs, rather than forking the object — apps/openrxiv is the only one that does today:

gridColumn: { ...gridColumn, 'margin-right-lg': 'body-end / page-end' },

For .prose, proseCss() returns the shared rules and takes what differs:

const { proseCss } = require('@curvenote/styles/typography');

typography: (theme) => ({
  DEFAULT: { css: proseCss({ fontFamily: '"Noto Sans", sans-serif', proseCode: theme('colors.pink[700]') }) },
  invert: { css: { '--tw-prose-code': theme('colors.pink[400]') } },
}),

Changing the vendored CSS

Edits to myst/ are fine — that is the point of vendoring — but record each one in the table at the bottom of UPSTREAM.md so the upstream diff stays readable.