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

@layerzerolabs/devtools-extensible-cli

v0.0.7

Published

This is a CLI for LayerZero Devtools - which is extensible by defining new operations.

Downloads

17

Readme

Devtools-Extensible-CLI README

This is a CLI for LayerZero Devtools - which is extensible by defining new operations.

Operations are of the class Type INewOperation and are defined in the types/index.d.ts file.

When you go to type your new operation, the args will have - instead of _. For example, oapp_config will be --oapp-config on the command line.

import { build as buildMove } from "../../tasks/move/build";
import { INewOperation } from "./NewOperation";

class MoveBuildOperation implements INewOperation {
  // the vm to use
  vm = "move";
  // the name of this operation
  operation = "build";
  // the required arguments for the operation
  reqArgs = ["oapp_config", "named_addresses", "move_deploy_script"];
  // arguments that you want to create in addition to the pre-defined ones
  addArgs = [];

  // the implementation of the operation
  async impl(args: any): Promise<void> {
    await buildMove(args);
  }
}

const NewOperation = new MoveBuildOperation();
export { NewOperation };

You can attach new operations to this via

  1. Paths await sdk.extendOperationFromPath('./operations/move-build') - example: packages/devtools-movement/operations/init.ts
  2. Providing an implementation of the INewOperation interface await sdk.extendOperation(NewOperation) - example: examples/oft-aptos-move/scripts/cli.ts