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

@waves/surfboard

v2.3.1-beta.1

Published

Surfboard =========

Downloads

117

Readme

Surfboard

Surfboard is a command line interface for working with RIDE programming language. Surfboard allows to compile RIDE scripts, deploy and run tests.

Surfboard requires nodejs.

The full manual how to use different tools for Waves dApps you can find here

oclif Version Downloads/week License

Installation

Surfboard is distributed as npm package. To install run npm i -g @waves/surfboard

Usage

For all commands surboard tries to use surfboard.config.json. If it is not present, surfboard falls back to global config. You can change global config by using config:change with -g flag

$ npm install -g @waves/surfboard
$ surfboard COMMAND
running command...
$ surfboard (-v|--version|version)
@waves/surfboard/2.3.1-beta.1 darwin-x64 node-v17.0.1
$ surfboard --help [COMMAND]
USAGE
  $ surfboard COMMAND
...

Commands

surfboard compile FILE

compile ride file

USAGE
  $ surfboard compile FILE

ARGUMENTS
  FILE  path to ride file

OPTIONS
  --fullInfo  outputs JSON with additional info. Such as complexity, size etc.

See code: src/commands/compile.ts

surfboard config:change KEY VALUE

change config

USAGE
  $ surfboard config:change KEY VALUE

ARGUMENTS
  KEY    config option key in dot notion
  VALUE  config option value

OPTIONS
  -g, --global  change global config

See code: src/commands/config/change.ts

surfboard config:show [KEY]

show config

USAGE
  $ surfboard config:show [KEY]

ARGUMENTS
  KEY  Config option key in dot notation

OPTIONS
  -g, --global  Show global config

See code: src/commands/config/show.ts

surfboard help [COMMAND]

display help for surfboard

USAGE
  $ surfboard help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

surfboard init

initialize new Ride project

USAGE
  $ surfboard init

See code: src/commands/init.ts

surfboard repl

run ride repl

USAGE
  $ surfboard repl

OPTIONS
  --env=env  which environment should be used for test

See code: src/commands/repl.ts

surfboard run FILE

run js script with with blockchain context

USAGE
  $ surfboard run FILE

ARGUMENTS
  FILE  path to script

OPTIONS
  --env=env              which environment should be used

  --variables=variables  env variables can be set for usage in script via env.{variable_name}. E.g.: MY_SEED="seed
                         phraze",DAPP_ADDRESS="xyz"

See code: src/commands/run.ts

surfboard test [FILE]

run test

USAGE
  $ surfboard test [FILE]

ARGUMENTS
  FILE  path to test file

OPTIONS
  -v, --verbose          logs all transactions and node responses
  --env=env              which environment should be used for test

  --variables=variables  env variables can be set for usage in tests via env.{variable_name}. E.g.: MY_SEED="seed
                         phraze",DAPP_ADDRESS=xyz, AMOUNT=1000

See code: src/commands/test.ts