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

@effectstream/frontend-sdk

v0.101.1

Published

React frontend SDK for EffectStream

Readme

@effectstream/frontend-sdk

Umbrella name for EffectStream's frontend code. Currently re-exports everything from @effectstream/wallets. Depend on this if you want a stable frontend namespace; import @effectstream/wallets directly if you prefer.

Install

bun add @effectstream/frontend-sdk
# or
npm install @effectstream/frontend-sdk

Usage

The export surface is exactly @effectstream/wallets:

import {
  allInjectedWallets,
  walletLogin,
  WalletMode,
} from "@effectstream/frontend-sdk";

const available = await allInjectedWallets({
  signatureSupport: true,
  transactionSupport: true,
});
const evmOption = available[WalletMode.EvmInjected][0];

const { provider, signedLogin } = await walletLogin({
  preference: { name: evmOption.metadata.name },
  mode: WalletMode.EvmInjected,
});

Browser only. Like @effectstream/wallets, this package depends on injected wallet APIs (window.ethereum, CIP-30, …) and won't load in plain Node.

Inside EffectStream

A thin re-export of @effectstream/wallets. If/when frontend-only helpers (React context providers, batcher submission hooks, event subscribers wired to React) ship, they'll live here without breaking app code that depended on the umbrella name.

Key exports

Everything @effectstream/wallets exports. The most-imported symbols across templates are:

  • walletLogin(...) - one-call wallet connection + signed batcher message.
  • WalletMode - enum of supported wallet types.
  • Wallet - type for a connected wallet.
  • EffectstreamConfig - runtime config the wallet helpers consume.
  • sendTransaction, sendBatcherTransaction, signMessage, waitForEffectstreamBlockProcessed - send/wait helpers.
  • allInjectedWallets, getAddressType, WalletNameMap - discovery + identification helpers.

For lower-level connector machinery (connectInjectedWallet, WalletModeMap, IProvider, IConnector, IInjectedConnector), import from @effectstream/wallets directly.

Examples

Runnable: test/examples.test.ts.

Real-world: every frontend in templates/ demonstrates the same surface.

Links

  • Docs: https://effectstream.github.io/docs/packages/tools/frontend-sdk
  • Source: https://github.com/effectstream/effectstream/tree/main/packages/frontend