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

@ama-styling/figma-extractor

v14.3.1

Published

Tools to extract Design Token from the Figma files

Readme

This package is an Otter Framework Module.

Description

Stable Version Bundle Size

This module will extract the Design Token metadata from a given Figma file.

How to execute

The package exposes to commands: extract-file and extract-project.
The 2 commands extract the Design Tokens from a single file but the extract-project will determine the file to extract based on the filename pattern and the versions extract from it.

Common Options

| Option | Env Variables | Descriptions | | -- | -- | -- | | --help | | Show help | | -a, --accessToken [string] | FIGMA_TOKEN | Access Token to read the Figma File information | | -o, --output [string] | FIGMA_OUTPUT | Folder to extract the Design Token to | | -n, --name [string] | FIGMA_DT_NAME | Name of the Design Token collection (default: "Design Tokens") | | --verbose | | Determine if the logger display debug messages (default: false) | | -q, --quiet | | Determine if it should ignore message in the console (default: false) | | -g, --generatePackage | | Request the generation of the NPM package.json (default: false) | | --packageName [string] | | Version of the Design Token collection (if not provided, the name option value will be used) |

Extract single Figma File

Extract the Design Tokens from a single Figma file.

npx @ama-styling/figma-extractor extract-file <fileKey> [options]

Extract Figma Project

Extract the Design Tokens from a Figma file part of a project.

npx @ama-styling/figma-extractor extract-project <projectKey> [options]

The following options are dedicated to the extract-project command:

| Option | Env Variables | Descriptions | | -- | -- | -- | | -P, --filenamePattern [string] | FIGMA_PROJECT_FILENAME_MATCHER | Pattern of the filename, capturing its version, to match in the project (default: "v((?:[0-9]+\.){0,2}[0-9]+(?:-[^ ]+)?)$") | | --versionRange | | Restricted range of versions of the File to be considered | | projectKey [string] | FIGMA_PROJECT_KEY | Figma Project Key where is the file to extract |

Setup automation

A complete documentation is available on Figma Extractor documentation