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

@shiage/vite

v0.1.1

Published

Vite plugin for Shiage — inspect and edit CSS in Chrome DevTools, save changes to source as Tailwind classes.

Readme

@shiage/vite

Vite plugin for Shiage — inspect and edit CSS in Chrome DevTools, save changes to source as Tailwind classes.

Install

pnpm i -D @shiage/vite

You'll also need Tailwind CSS (v3 or v4) somewhere in your build.

Use

// vite.config.ts
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import tailwindcss from '@tailwindcss/vite'
import shiage from '@shiage/vite'

export default defineConfig({
  plugins: [react(), tailwindcss(), shiage()],
})

That's it. Run pnpm dev, open your site, then edit any element's CSS in real Chrome DevTools (right-click → Inspect). Shiage picks the change up automatically — no element to "pick" first — and the pill (bottom-right) shows "Save N changes." Click Save: the diff panel shows the proposed Tailwind class edit, confirming rewrites the source file on disk, HMR repaints.

The plugin is apply: 'serve' and enforce: 'pre'. It's a true no-op in production builds and stamps source locations before @vitejs/plugin-react compiles the JSX away (so plugin order doesn't matter).

Options

shiage() accepts none in v0.1 — sensible defaults out of the box. Detection of Tailwind v3 vs v4 is automatic.

What's supported / not

See the main README and SUPPORTED_PROPERTIES.md for the full list, plus FAQ.

License

MIT — © 2026 Horace Choi.