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

gdn-run-sdk

v0.6.42-beta

Published

Run SDK - GDN fork

Downloads

3

Readme

Forked version

This is a fork of run-sdk.

RUN SDK - 0.6.41 beta

tests codecov

Note: This project is no longer supported. The repository exists for reference only.

RUN is a token protocol to build whatever you dream up. A world of interactive apps and tokens.

To give it a go, visit https://run.network for tutorials and docs.

Installation

Run npm install to install node dependencies.

Then run npm run build to build the browser and node libraries.

Community

Join us in our Discord, Run Nation: https://run.network/discord. Here you'll meet other developers using Run, hear about cool projects launching, and know right away when there are new announcements.

Getting Help

Post what's on your mind in the "ask-for-help" channel in the Run Nation Discord.

Commands

  • npm run lint - Lint and automatically fix errors
  • npm run build - Build outputs
  • npm run test - Test library quickly
  • npm run test:node - Test the minified node build
  • npm run test:browser - Test the minified browser build (Chrome default)
  • npm run test:cover - Collect code coverage
  • npm run test test/plugins/local-purse.js - Run just the purse tests

Configuring the tests

Various environment variables may be used to configure the tests:

| Name | Description | Possible Values | Default | |-------------------|-------------------------------------------------|------------------------------------------------|-------------| | NETWORK | Network to test on | mock, main, test, stn | mock | | BROWSER | Browser used for testing | chrome, firefox, safari, MicrosoftEdge | chrome | | STRESS | Whether to run the stress tests | true, false | false | | PURSE_[network] | Purse key used on a specific network | your string privkey | undefined | | API | Blockchain API when not using the mock network | run, whatsonchain | undefined | | APIKEY_[api] | API key used with a specific blockchain API | your string api key | undefined | | LOGGER | Whether to log internal messages to the console | true, false | false |

Examples

  • env BROWSER=safari npm run test:browser - Test the browser build on Safari
  • env STRESS=1 npm run test - Test library with stress tests
  • env NETWORK=test env PURSE=<funded_private_key> npm run test - Run all tests on testnet

.env file

For ease of use, you may also store these variables in a .env file where the tests are run. Here's a sample:

BROWSER=safari
PURSE_MAIN=<your priate key>
PURSE_TEST=<your private key>
APIKEY_WHATSONCHAIN=<your api key>