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 🙏

© 2025 – Pkg Stats / Ryan Hefner

devspeed-commandsjs

v1.0.3

Published

create commands easly

Downloads

9

Readme

devSpeed-commandsjs

commandsjs allows You to create commands an execute them any were in your application.

Table of Content

quickstart

const { Command,  CommandLibrary,initializeCommand} = require('devSpeed-commandsjs')
// first step create a command 
const myCommand = new Command({
    trigger: "myCommand",
    execute: function(){
        console.log('myCommand has been called')
    }
})
// second step save your command to the CommandLibrary
const commands = new CommandLibrary([myCommand])
// last initialize your commands 
initializeCommand("myCommand", commands) // results myCommand has been called

Setup Process

there are 4 steps to seting setup

Step 1

  • create a commands folder
  • in the commands folder create sayhello.js file
  • in the sayhello.js write this code
 const {Command} = require('devspeed-commandsjs');

 const sayhello = new Command({
    trigger: "sayhello"
    execute: function(){
        console.log('hello')
    }
 })
 module.exports = sayhello;

The Command class makes it easier to create an command. the trigger field trigger the command the execute field is the function that is being called when the command is being initialize

Step 2

create a commandlibrary to hold all of our command. create a index.js file in your commands folder

const  {CommandLibrary} = require('devspeed-commandsjs');

const sayhello = require('./sayhello.js')

const commands = new CommandLibrary([
    sayhello,
])

module.exports = commands;

The CommandLibrary class also makes it easy to store commands.

last step

back in your main file we will need a command executer to execute our commands. we will import or commands from our commands folder and pass it to the Executer, the Executer will than check if the trigger matches one of the commands and than call the execute method attach.

 const {Executer} = require('devspeed-commandsjs')
 const commands = require('./commands/index')

 const executer = new Executer(commands)

executer.initializeCommand('sayhello') // hello logged to the console 

The Executer class have all the methods to execute a command.

features

passing args

Passing args to the execute function. imagine your working on a project and you need to past an arg to the execute function. this feature allow you to do exactly that.

 const executer = new Executer([testCommand])
 const LastArg = 'arg3';

 executer.initializeCommand('Test', 'arg1', 'arg2', lastArg) 

when we trigger the command we can send args to the execute function

  const testCommand = new Command({
    name: 'Test command',
    trigger: 'Test',
    execute: function(arg){
         console.log(arg) // ['arg1', arg2, arg3]
    }
  })