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

@mosetta/ide-plugin-theme

v0.0.14

Published

Darcula, as a palette of CSS variables — and the shared look of fields, buttons and scrollbars.

Readme

Theme

@mosetta/ide-plugin-theme · Darcula, as a palette of CSS variables — and the shared look of fields, buttons and scrollbars.

What it does

The theme gives the IDE its colours: Darcula as in WebStorm, with the values taken from JetBrains' own scheme rather than picked by eye from a screenshot. It sets them as CSS variables (--bg, --fg, --selection, --git-modified, …) on the IDE's root and styles the shared elements — the input field, the button, the checkbox, the scrollbars. Code colours come from the same palette through the code display plugin, so every view of code changes together.

Without the theme the IDE still works; it just looks like a plain web page.

Screenshots and demos

Darcula across the tree, the editor and a popup

Try it in the browser

Using it from another plugin

Style your plugin with the variables, never with colours of your own, and it will follow any theme:

this.ide.css(`
  .notes-row { color: var(--fg); background: var(--panel-bg); }
  .notes-row.is-new { color: var(--git-added); }
  .notes-row:hover { background: var(--control-bg-hover); }
`);

ide.css() fences your rules in to the IDE's root, so a class name of yours never reaches the page the IDE is embedded in, and a :root rule lands on the root itself.

The palette itself, for code drawn outside CSS (a canvas, an SVG):

import ThemePlugin from '@mosetta/ide-plugin-theme';

const theme = this.ide.getPlugin(ThemePlugin);
theme.palette.keyword; // '#CC7832'
theme.codeFont;        // the code font stack
theme.dark;            // true — CodeMirror picks its base colours to match

A different theme is a plugin with the same shape — a palette, a codeFont, dark, and its variables — put in place of this one in the plugins setting.