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

@frontier-fi/sdk

v0.3.1

Published

SDK for interacting with the Frontier protocol

Readme

Frontier SDK

npm version

TypeScript SDK for interacting with the Frontier V3 protocol on supported chains (Ethereum, Base, and Sepolia).

Installation

pnpm add @frontier-fi/sdk

Local Setup

pnpm install

Requirements

  • fetch

Polyfill

If your platform does not support one of the required features, it is also possible to import a polyfill.

Testing

pnpm test:release runs the consumer regression suite without RPC access or Anvil. pnpm check-types:release checks production sources. Release checks also build the package and verify its CommonJS and ESM imports. These checks do not replace transaction execution against a fork of Frontier's deployed contracts.

pnpm test:no-integration excludes fork integration tests and live API contract tests (*.integration.test.ts and *.contract.test.ts). It still validates configured deployments via RPC and chain setup against the Frontier API. pnpm test:all includes Anvil fork integration tests and live API contract tests.

pnpm test

Testing runs against a local Anvil fork and resolves RPC URLs in order: per-chain *_RPC_URL, DRPC_API_KEY (via dRPC across all supported chains), then public RPC fallbacks:

DRPC_API_KEY
# Optional per-chain overrides:
ETHEREUM_RPC_URL
BASE_RPC_URL
SEPOLIA_RPC_URL

Anvil Client

To download and install the anvil client, run the following commands (MacOS):

  • curl -L https://foundry.paradigm.xyz | bash
  • brew install libusb
  • source /Users/$(whoami)/.zshenv
  • foundryup

Releases

The release.yml workflow runs on pushes to main and can be retried manually on main. Pending Changesets open a version PR; when none remain, it publishes the version in package.json if that version is absent from npm. Releases use @frontier-fi/sdk@<version> tags, avoiding the inherited Balancer tags.

For subsequent changes, run pnpm changeset, select @frontier-fi/sdk, and commit the generated changeset with the fix. Merge the resulting version PR to publish. Only stable versions are published to latest by this workflow.

Publishing runs the source typecheck, consumer tests, and tsup through prepublishOnly. It uses the checked-in generated GraphQL types; refreshing those types with pnpm codegen is a separate, reviewed source change.

One-time setup, matching the maths repository:

  1. Install the maxyz-actions GitHub App on frontier-fi/sdk, grant contents and pull-request write access, and make MAXYZ_ACTIONS_PRIVATE_KEY available to the workflow.
  2. Configure the GitHub environment release to allow deployments from main.
  3. Bootstrap the npm package with an authenticated maintainer's initial npm publish --access public from a reviewed checkout after installing the locked dependencies. The package must exist before configuring its publisher.
  4. Configure an npm trusted publisher for @frontier-fi/sdk: organization frontier-fi, repository sdk, workflow release.yml, environment release, with direct npm publish allowed. Subsequent CI publications use OIDC and provenance, with no npm token secret.

Upstream documentation

In-depth documentation on this SDK is available at docs-v3.balancer.fi/developer-reference/sdk.