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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@statechannels/xstate-wallet

v0.3.0-hyperspace

Published

State channel wallet using xstate.

Downloads

1

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

tashieugyaltashieugyalgill93gill93nilocknilockgeokneegeokneekerzhnerkerzhnerlagaplagap

Keywords

Readme

🌐 Browser wallet

State channels wallet.

Currently, an application should run this wallet inside an iFrame and communicate with it via @statechannels/iframe-channel-provider and @statechannels/channel-client.

See https://docs.statechannels.org

Netlify Status

Configurable Environment Variables

| Variable | Possible Values | Description | | ------------------------- | ---------------------- | ---------------------------------------------------------------- | | LOG_DESTINATION | "console", a file name | When running tests, use console.log or to a file | | USE_INDEXED_DB | empty, or truthy value | If truthy, uses IndexedDB in the browser and in-memory otherwise | | CLEAR_STORAGE_ON_START | empty, or truthy value | If truthy, clears any data in the store before start | | NITRO_ADJUDICATOR_ADDRESS | address | Address of NitroAdjudicator contract on-chain | | ETH_ASSET_HOLDER_ADDRESS | address | Address of ETHAssetHolder contract on-chain | | HUB_ADDRESS | address | Signing address of firebase:simple-hub participant | | HUB_DESTINATION | empty or bytes32 | Destination of firebase:simple-hub participant | | CHAIN_NETWORK_ID | string or integer | Chain identifier e.g., 3 for Ropsten |

Why are webpack loaders in dependencies?

Currently the e2e-tests package relies on xstate-wallet to run. Since we use environment variables as configuration options, and these are baked into the webpack builds at compile-time, we instead distribute the entire webpack dev server environment over npm to simplify things. We should move configuration options to be something declared at runtime.