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 🙏

© 2026 – Pkg Stats / Ryan Hefner

brah-weiroll-sdk

v1.1.0

Published

Brahma's Weiroll Development SDK

Downloads

8

Readme

Brahma Weiroll SDK

An SDK to work with weiroll scripting to generate bytecode.

Installation

npm i --save-dev brah-weiroll-sdk

(or)

yarn add -D brah-weiroll-sdk

Setup

Setup primarily requires 2 config files that are defined to comply with their interfaces -

  1. Main config

    • File name: brah-weiroll.config.json
    • Location: Directory root
    • Definition:
    interface ConfigFile {
      abiKey?: string; /// key pointing to contract abi, if the JSON file containing ABI has other data as well
      contracts: string; /// string path to contracts Config
      useForge: boolean; /// true or false to use forge file structure (abi will be read from ./out folder)
    }

    sample

  2. Contracts Config

    • File name: Can be arbitrary, but matching the contracts key on brah-weiroll.config.json
    • Location: Can be arbitrary, but matching the contracts key on brah-weiroll.config.json
    • Definition:
    interface ContractsConfig {
      [key: string]: {
        /// name of contract
        address: string; /// contract address
        abi?: string; /// string path to file containing contract abi (not required if useForge: true)
      };
    }
    • NOTE: This must contain address and abi to a 'Helper.sol' contract

    sample

Usage

  1. Instantiate VM object using

    import {BrahVM} from "brah-weiroll-sdk";
    const vm = new BrahVM();
  2. Import contracts and add functions to planner as required. Refer to sample implementation

  3. Compile VM using

    vm.compile(true);

    if the plan's bytecode is to be printed to STDOUT.

    otherwise,

    vm.compile();

License

MIT