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

figmake

v0.0.4

Published

A tiny CLI for making Figma plugins with HTML, CSS, and vanilla JavaScript

Downloads

16

Readme

Figmake npm Version build

A tiny CLI for making Figma plugins with HTML, CSS, and vanilla JavaScript

  • Stitches together ui.html, ui.scss, and ui.js into a single HTML file for your plugin UI
  • Automatically inlines any image assets into the generated HTML file

Goals

  • As few files as possible
  • No package.json or node_modules
  • No TypeScript
  • No JavaScript UI framework; just use figma-plugin-ds
  • No API; just use the Figma plugin API
  • Tiny CLI that just does one thing

Quick start

Requires Node.js.

First:

$ npm i -g figmake

Figmake assumes that your plugin code comprises the following files:

main.js
manifest.json
ui.scss
ui.html
ui.js

(Of these, only main.js and manifest.json are mandatory.)

manifest.json should look something like:

{
  "name": "My Plugin",
  "id": "314159265358979323",
  "api": "1.0.0",
  "main": "build/main.js",
  "ui": "build/ui.html"
}

To build the plugin:

$ figmake

This will generate the following two files:

  • build/main.js — The plugin entry point, built from main.js.
  • build/ui.html — HTML file for the plugin UI, stitched together from ui.html, ui.scss, and ui.js.
    • ui.scss will be compiled down to CSS.
    • Image assets referenced in ui.html and ui.scss will be inlined into the resulting HTML file.

To watch for code changes and rebuild the plugin automatically:

$ figmake -w

To minify the output files:

$ figmake -m

See also

License

MIT