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

@formfactory-dev/toolkit

v0.4.0

Published

Shared toolkit primitives for Form Factory packages: Atlassian/GitHub helpers, document-format converters.

Downloads

238

Readme

@formfactory-dev/toolkit

Shared API primitives for @formfactory-dev/cli and @formfactory-dev/workflows. Most users get this transitively. Install directly when writing custom workflow code that wants these primitives without the agent/sandbox runtime:

pnpm add @formfactory-dev/toolkit

Everything is exported from the package root — import { ... } from "@formfactory-dev/toolkit".

Surface

Jira

import { fetchJiraTicket, type JiraTicket } from "@formfactory-dev/toolkit"

// Use the operator's current acli site:
const ticket = await fetchJiraTicket("ENG-17")

// Or pin a site explicitly (required for multi-site operators):
const sameTicket = await fetchJiraTicket("ENG-17", { site: "formfactory" })
// → { key, summary, descriptionMarkdown, issueType?, status?, assigneeDisplayName? }

Shells out to acli jira workitem view <key> --json; the ADF description is flattened to Markdown. With options.site, runs acli jira auth switch first and serializes concurrent calls so different-site invocations can't interleave. Without it, uses the operator's current acli auth state as-is.

Confluence

import {
  fetchConfluencePage,
  ConfluenceFetchError,
  parseConfluenceUrl,
  type ConfluencePage,
} from "@formfactory-dev/toolkit"

const page = await fetchConfluencePage({
  url: "https://acme.atlassian.net/wiki/spaces/DEV/pages/123456",
  credentials: { email: "[email protected]", apiToken: "..." },
})
// → { id, title, spaceKey, version, markdown, url }

const { host, pageId } = parseConfluenceUrl(url)

Hits the Confluence Cloud REST API v1 with Basic auth (acli doesn't cover Confluence content). HTTP errors throw ConfluenceFetchError with status so callers can tailor on 401 / 403 / 404.

Credentials

import type { AtlassianCredentials } from "@formfactory-dev/toolkit"
// { email: string; apiToken: string }

Plain credential type used by fetchConfluencePage. Callers pass credentials in; toolkit stays free of settings-tier semantics.

ADF

import { adfToMarkdown } from "@formfactory-dev/toolkit"

Atlassian Document Format → Markdown. Handles headings, paragraphs, lists, code blocks, blockquotes, tables, panels, and inline marks (bold/italic/code/strike/underline/link).

Publishing

Published via pnpm publish from GitHub Actions using OIDC (the npm scope is configured as a "trusted publisher" tied to this repo and the release workflow — local publishes are rejected). pnpm publish rewrites catalog: and workspace: protocol references in package.json to concrete version ranges before upload, so consumers installing via npm, yarn, pnpm, or bun see normal version strings.

License

MIT — see LICENSE.