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

@mattdesl/fika

v1.1.1

Published

A figma plugin generator

Readme

fika

A small figma plugin generator using Parcel.

1. Install

npm install @mattdesl/fika -g

2. Create an Empty Folder

Create and move into an empty folder where you'd like to keep all your plugins:

mkdir figma-plugins
cd figma-plugins

Or, you can create a new folder repository per plugin.

3. Generate a new Plugin

The following will generate ./src/my-plugin and start a development server.

fika my-plugin --init

Or, omit the --init flag to continue developing an existing plugin.

Other examples:

# use a different name when generating the plugin
fika some-plugin --init --name="My Cool Plugin"

# generate a plugin without HTML
fika my-cool-plugin --init --no-ui

# continue developing an existing plugin
fika my-existing-plugin

# use a different root folder than ./src
fika lib/my-plugin --init

You can open http://localhost:9966/ to test your UI, and edit the files inside ./src/my-plugin to see them reload.

4. Test Build in Figma

Once you've generated a ./dist folder, open a project in Figma Desktop, select Menu > Plugins > Development > New Plugin. Click "Choose a manifest.json" and find the manifest.json file in ./dist/my-plugin/manifest.json. (notice dist not src).

Now you can run the plugin via Menu or Right Click > Plugins > Image Palette. You can also open the Console via that context menu, and re-run the last plugin via Cmd + Option + P.

5. Build for Production

Kill the server and run the following to build a smaller and more optimized production plugin:

fika my-plugin --build

This will generate assets into ./dist/my-plugin. You can then publish your plugin!

License

MIT, see LICENSE.md for details.