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 πŸ™

Β© 2025 – Pkg Stats / Ryan Hefner

spinarch

v0.0.16

Published

πŸ₯¬ Spin local Archway testnet for faster dApps development πŸš€

Readme

πŸ₯¬ SpinArch

asciicast

About

SpinArch (c) 2022, Surya Handika Putratama [email protected]

Spin local Archway testnet for faster dApps development

⚠️ This application is in early development

Features

  • Run persistent/non-persistent local testnet node
  • Generate pre-funded accounts
  • Take snapshot of running node

Requirements

  • Linux/macOS (not tested on Windows yet).
  • Node.js (>= 16) and NPM
  • Docker

Installation

npm install -g spinarch

Usage

Usage: spinarch [options]

πŸ₯¬ Spin local Archway testnet for faster dApps development πŸš€

Options:
  -V, --version            output the version number
  --project-id <string>    Your project ID
  --chain-id <string>      Chain ID (default: "spinarch-1")
  --num-accounts <number>  Number of accounts to generate (default: 10)
  --balance <number>       Default balance of each generated account (default: 1000000000)
  --update-image           Update the Archway image to latest version
  --reset-state            Reset the blockchain to the genesis state
  -h, --help               display help for command

1. Run a throwaway node

This command will run a temporary, non-persistent Archway node. Node's data will be deleted on exit.

spinarch

2. Run a persistent node

Specify a project ID if you want to run a persistent Archway node. Node's data is saved to disk and can be loaded again next time you run SpinArch with the same project ID.

spinarch --project-id my-dapp

3. Reset a persistent node

Saved state will be reset to the genesis.

spinarch --project-id my-dapp --reset-state

4. Run with custom chain ID

You can run a node with a custom chain ID by specifying --chain-id option. This applies to both throwaway and persistent node.

spinarch --chain-id mainnet-1

5. Run with N number of prefunded accounts

By default, SpinArch will generate 10 prefunded accounts. You can generate an N number of accounts with B balance by specifying --num-accounts and/or --balance.

spinarch --num-accounts 5 --balance 10000000

Troubleshooting

Cannot store/compile Wasm contract because of missing AVX instruction

If you are running SpinArch on Apple Silicon (M1 CPU family), try enabling native binary.

$ USE_NATIVE=1 spinarch --project-id my-project

Contract size exceeds limit

By default, Wasm code size is limited to 1228800 bytes (~1.2 mbytes). To change this, you need to run a persistent project (with --project-id), stop it, edit genesis.json, and do a state reset with --reset-state. For example:

Run a persistent node:

$ spinarch --project-id my-project

Stop SpinArch (Ctrl-C) after node is running and then edit genesis.json.

$ nano ~/.spinarch/my-project/config/genesis.json

Look for "max_wasm_code_size" and change the value to higher number like 12288000. After that, run the same project with --reset-state to reset the blockchain.

$ spinarch --project-id my-project --reset-state