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

@design-parity/adapter-figma

v0.1.26

Published

Figma ReferenceAdapter: resolves a component to a Figma node via Code Connect, fetches the reference image + variables over the REST API, and normalizes to a DesignReference.

Readme

@design-parity/adapter-figma

The Figma ReferenceAdapter. Figma is the keystone source — the only one with a machine-resolvable design↔code link (Code Connect). This adapter uses the REST API + Code Connect, never the Dev Mode MCP server (that is local/desktop-session oriented and wrong for a hosted bot).

What it does

resolve(componentId, ref, ctx):

  1. Resolve the node. If ref is a handle (figma:<fileKey>/<nodeId> or a figma.com URL) it's parsed directly. Otherwise the adapter reads the repo's Code Connect output (figma.code-connect.json, or FIGMA_CODE_CONNECT_FILE) to map the component to a node.
  2. Fetch structureGET /v1/files/:key/nodes (padding, corner radius, fills, text style).
  3. Fetch variablesGET /v1/files/:key/variables/local, mapping collection modes (Light/Dark) to themed colors. Degrades gracefully to structure-only tokens when variables aren't entitled.
  4. Render the reference image(s)GET /v1/images, downloaded and written under outDir.
  5. Normalize to a DesignReference with linkMethod: "code-connect".

Auth

Reads credentials from AdapterContext.env:

  • FIGMA_OAUTH_TOKENAuthorization: Bearer (preferred), or
  • FIGMA_TOKEN / FIGMA_PAT / FIGMA_ACCESS_TOKENX-Figma-Token.

Missing credentials, 401/403, 429 (rate limit, with Retry-After), and a missing node each raise a typed FigmaError subclass.

Usage

import { createFigmaAdapter } from "@design-parity/adapter-figma";

const adapter = createFigmaAdapter({
  // optionally render one image per theme from separate frames
  resolveTargets: (ref) => [
    { nodeId: ref.nodeId, theme: "light", size: "compact" },
    { nodeId: "1:43", theme: "dark", size: "compact" },
  ],
});

const reference = await adapter.resolve(
  "ui/Button.kt#PrimaryButton",
  "figma:AbCdEf123456/1:42",
  { repoRoot: process.cwd(), env: process.env },
);

Network is injectable (fetch) and the client is mockable, so unit tests run fully offline (see test/).

Theming note

Figma's image render uses a node's default variable mode; the REST API can't switch modes per render. So themed tokens come from variables (all modes), while themed images come from rendering separate per-theme frames via resolveTargets.