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

acode-pluginx

v1.1.0

Published

CLI starter bundled with esbuild

Readme

acode-pluginx

CLI to scaffold a new Acode plugin project (JS/TS) with optional SCSS support. It also allows to add codemirror types for better autocompletion.

Requirements

  • Node.js 18+ (recommended)
  • One of: npm, pnpm, yarn, or bun

Install / run

You can run it without installing globally:

npx acode-pluginx <projectName> <pluginId> [options]

If you are developing this repo locally, you can run it from the project folder:

npx . <projectName> <pluginId> [options]

Quick examples

Create a TypeScript plugin using Bun and SCSS:

npx acode-pluginx myPlugin com.plugin.acode --ts --use-bun --scss

Create a JavaScript plugin using pnpm (no prompts for package manager):

npx acode-pluginx myPlugin com.plugin.acode --js --use-pnpm

Create inside the current directory (will warn if it’s not empty):

npx acode-pluginx . com.plugin.acode --ts --use-npm

Options

  • --ts: Generate a TypeScript plugin project
  • --js: Generate a JavaScript plugin project
  • --scss: Include src/style.scss
  • --use-bun: Use Bun in the generated project
  • --use-pnpm: Use pnpm in the generated project
  • --use-npm: Use npm in the generated project
  • --use-yarn: Use Yarn in the generated project
  • --cm-types: (Experimental) Generate codemirror packages types

Notes:

  • Don’t pass both --ts and --js (it will error).
  • If you don’t pass a package-manager flag, you’ll be prompted to choose one.

What it generates

In the new project folder, the CLI creates:

  • src/main.ts or src/main.js (plugin entry)
  • plugin.json (plugin metadata)
  • esbuild.config.mjs (build + dev server + zip pack hook)
  • pack-zip.js (creates dist.zip)
  • tsconfig.json (when using TypeScript)
  • icon.png (default icon)
  • src/style.scss (only when --scss is used)

After generating a project

From the printed “Next steps”, you’ll typically do:

cd <projectName>
<packageManager> install
<packageManager> dev

License

ISC