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

@pantoken/vitepress

v0.2.3

Published

Theme a VitePress site with Instructure tokens: maps VitePress --vp-* CSS variables to var(--instui-*).

Readme

@pantoken/vitepress

Theme a VitePress site with Instructure tokens. VitePress theming is driven by --vp-* CSS variables; this points them at var(--instui-*), so the docs pick up the Instructure look and stay in sync with the appearance toggle.

Install

npm i @pantoken/vitepress @pantoken/css

Also available as pantoken/vitepress.

Usage

Register a theme CSS file (.vitepress/theme/custom.css) from your theme's index.ts, and import both the token layer and the bridge:

/* .vitepress/theme/custom.css */
@import "@pantoken/css/style.css"; /* defines the --instui-* custom properties */
@import "@pantoken/vitepress/custom.css"; /* maps VitePress --vp-* → var(--instui-*) */

Or generate the bridge yourself:

import { toVitePressCss } from "@pantoken/vitepress";

const css = toVitePressCss();

Light and dark flow through the --instui-* tokens (which use light-dark()), so VitePress's appearance toggle stays in sync. VitePress uses --vp-c-brand-1/2/3 for accent, hover, and solid states; this bridge points them all at the brand color, so override individual shades in your custom.css for distinct states. Because the values are var(--instui-*) references, @pantoken/css must be present to define them.

API

  • toVitePressCss(options?): string — emit the VitePress → Instructure bridge CSS. Pass { selector } to change the wrapping selector (default ":root").
  • vitePressCss: string — the ready-made bridge stylesheet.
  • VITEPRESS_TO_INSTUI — the frozen map of VitePress CSS variable to the Instructure token it resolves to.
  • ToVitePressCssOptions — options type for toVitePressCss.
  • ./custom.css — the generated static bridge stylesheet, for @import from your custom.css.

Related

  • Pairs with @pantoken/css for the --instui-* custom properties the bridge points at.

License

MIT