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

@monstermakes/larry-executioner

v0.0.2

Published

A library to automate the execution of javascript calls.

Downloads

3

Readme

Larry The Executioner

Description

This project aims at creating a nodejs libray that can execute arbitrary functions/methods as a set of instructions for automating or testing purposes.

Example Usage

let p = new Parent();
let instructionSet = {
    commands: [
        {
            id: 'initial',
            classInstance: p,
            method: 'method',
            args: [1,2,3]
        },
        {
            id: 'second',
            classInstance: p,
            method: 'method',
            args: [
                '$cmd:0->request[2]',
                2,
                '$cmd:0->request[0]'
            ]
        },
    ]
};
let execution = new Execution(instructionSet);
return execution.execute()
    .then((executionDetails)=>{
        executionDetails[0].request.should.eql([1,2,3]);
        executionDetails[1].request.should.eql([3,2,1]);
	});

This is an example of using the Execution class directly. It demonstrates setting up 2 commands to run seuentially where the request arguments being passed into the second command are based on the first.

These request arguments can be any javascript value however if they are a string that matches the lookup selector format $command:<cmdId>-><dot selector> they will be replaced with their "looked up" value. The values are looked up against previously executed command. Each command has a unique cmdId if supplied or are identified by their index in the initial instructionSet. When a command is executed an “Execution Details” object is created that has a bunch of properties in it like request,response, failure etc… The dot selector (a lodash style selctor obj.property[1]) is then used against the Execution Details object to pull the appropriate value.

So think of the $cmd: as a token to tell the executioner to lookup a cmd value, followed by a way to uniquely id the command (id or index). Everything to the right of the -> is a dot selector to lookup your value in that commands Execution Details object.

Here are a few more examples of request arguments:

$cmd:0->request[0]',
'$cmd:initial->request[0]',
'$cmd:0->request[2].property',
'$cmd:0->request[3][1]',
'$cmd:0->response.someProp',
'$cmd:0->failure.message'

TODO

  1. Make it work...
  2. Execute Things...
  3. Be Rad