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

@cartridge/connector

v0.13.16

Published

Cartridge Controller Connector

Readme

@cartridge/connector

Cartridge Controller connector for starknet-react and other StarkNet wallet libraries.

Why this package needs to be instantiated

The Cartridge Controller is iframe-based and requires per-app configuration (chains, paymaster, preset, etc.). Unlike browser-extension wallets, it cannot auto-inject itself at page load — the dapp must construct it once at app startup.

When ControllerConnector is instantiated, it:

  • Sets window.starknet_controller so legacy window.starknet_* discovery finds it.
  • Calls @wallet-standard/wallet's registerWallet(...) so any wallet-standard consumer (e.g. starknet-start via @starknet-io/get-starknet-core) discovers it through the standard event channel.

After that, discovery and disconnect work without further setup.

Integration paths

starknet-react v5

import ControllerConnector from "@cartridge/connector";
import { StarknetConfig, publicProvider } from "@starknet-react/core";

const connectors = [new ControllerConnector(options)];

<StarknetConfig connectors={connectors} provider={publicProvider()}>
  <App />
</StarknetConfig>;

starknet-start (@starknet-react/start)

Instantiate ControllerConnector once at app startup with your config. You don't need to pass it anywhere — the constructor side effect registers Cartridge with starknet-start's discovery.

import ControllerConnector from "@cartridge/connector";

new ControllerConnector(options);

For recommendedWallets lists, use id: "controller".

Vanilla get-starknet / wallet-standard

Same pattern — instantiating ControllerConnector registers the wallet via @wallet-standard/wallet.

controller.asWalletStandard() is also exposed on the underlying ControllerProvider for callers that want the WalletWithStarknetFeatures wrapper directly without going through discovery.