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

@cowri/cowri-dapp-sdk

v0.1.6

Published

Cowri dapp sdk

Downloads

28

Readme

shell-manager

Shell Manager

Developer setup

git clone https://github.com/cowri/shell-manager.git
npm install
npm install -g download-cli extract-zip
npm run clean
npm run build
npm run test

Testing

  • Unit tests of the shell-manager run with Jest and depend on a local instance of Ganache-cli running as the Denise user. More information about Ganache-cli and our implementation can be found in Installation.MD.
  • Ensure download-cli is installed with npm install -g download-cli
  • Ensure extract-zip is installed with npm install -g extract-zip
  • Ensure the cowri_ganache.zip ganache snapshot is downloaded with npm run download-snapshot
  • To run the unit tests, ensure that Ganache-cli is running as denise with npm run ganache:denise, then in a separate terminal run npm run test:watch. This will open up an interactive test terminal and will automatically run tests whenever any file is saved.
  • You can reset the ganache instance at any time by exiting out of the running instance with ctrl-c and restarting the instance with npm run ganache:denise
  • Please keep in mind that Ganache-cli is essentially a persistent mock of the blockchain, so any updates to token balances or user shells will persist between tests. This won't be a problem as long as the unit tests either revert changes they make to users or their shells or if they never depend on hardcoded token balances.
  • If you run into a situation where you need to manually reset your ganache instance, you can do so with npm run reset-snapshot.

Pushing to NPM

npm publish

For the time being these two following commands are removed.
When the tests are completing healthily, they will be put back
in to the scripts portion of package.json, which will test 
the repository before publication of new versions.

  "prepare": "npm run build",
  "prepublishOnly": "npm run test && npm run lint",

Generating Documentation

Currently documentation generation is set up to go the gitbook repsoitory Publishing process

  1. Clone gitbook repsoitory into the same parent directory as shell-manager
  2. generate the documentation e.g. npm run docs ./src/provider/CowriWeb3Provider.ts
  3. Note
  • when using npm run docs you must specify the directory of file you want to create documentation for (as above)
  • If you would like to use a different destination directory for documentation you can use the following command .node_modules/.bin/typedoc --theme markdown --mdEngine gitbook --out ../gitbook/typedoc/ ./src/provider/CowriWeb3Provider.ts