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

@axmit/flow-helper

v1.4.17

Published

To start using:

Readme

flow-helper

To start using:

  • yarn add --dev @axmit/flow-helper

  • Start using

yarn new FE | BE | MOB - create empty project

yarn sync FE | BE - sync config files

yarn mr - create new MR

yarn figma2style - get styles/variables from Figma

Figma to Style

Introduction

First, you should create a .env file, where you write access token key

FIGMA_DEV_TOKEN=11111-38ebb60d-baf8-455f-808c-f9a2519a1c7c
FIGMA_FILE_KEY=
FIGMA_TYPE=
FIGMA_SPACER_ARG=

Then change <YOUR_TOKEN> in .env file to your personal access token key

Token key you can take in this. You can create a temporary access token by clicking right there on Get personal access token or read how to make permanent access token.

Install

Run this command:

yarn install

Then, you should run the script and you will need a file key. The file key can be parsed from any Figma file url: https://www.figma.com/file/${file_key}/${title}.

Run command in terminal

yarn figma2style

Wait for the script to finish...

In root directory you can see folder src/app/assets/sass/figma where are the generated scss file.

Options (NOT IMPLEMENTED YET)

If you work in Figma with a big team, and you have team styles, you can take them. The teams key can be parsed from any Figma team url: https://www.figma.com/files/team/${teams_key}/${title}

node main.js ${teams_key} teams

If your Figma file has a "node element" with "spacers geometry", you can also add them to generate styles.

node main.js ${file_key} files spacers=${node_id}

The node_id key can be parsed from any Figma team url: https://www.figma.com/file/${file_key}/${title}?node-id=${node_id}

If you want to customize more accurate style generation and not only on Web but also iOS and Android.

Change the configuration in the file config.json

Read more about all possible settings here in Style Dictionary

Version

yarn -v 1.16.0

node -v 10.16.0