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

@connext/cf-apps

v0.4.1

Published

Collection of various apps built on Counterfactual

Downloads

10

Readme

Updating the Contracts

When any of the contracts get updated, their corresponding expected build artifacts need to be updated as well.

To do make this update, run:

yarn build

Migrations

The networks folder contains the migration files for the different Ethereum networks the contracts have been migrated to. The ID of the respective networks are used as file names. The mapping of some of the major Ethereum network IDs to network names is:

| Network ID | Network Name | | ---------- | --------------- | | 1 | Main net | | 3 | Ropsten testnet | | 4 | Rinkeby testnet | | 42 | Kovan testnet |

Not all of the networks will be used for the Counterfactual contracts, but you can find a more comprehensive list here. To run a migration against a target network:

  • make sure the target network configuration exists in truffle.js (or truffle-config.json for Windows)
  • cp .env.example .env and make sure the right env vars are set in .env
    • note that the address of the account that needs to be funded to deploy the contracts is derived (in a node.js REPL) via: require('ethers').Wallet.fromMnemonic('ETH_ACCOUNT_MNENOMIC')
  • the network account you're using to send transactions from is funded (eg. for Rinkeby: https://faucet.rinkeby.io/)
  • run: yarn migrate --network <network name>