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

@chix/iobox

v2.9.14

Published

Input/Output iobox

Downloads

92

Readme

IO Box

Provides a simple semi protected IO sandbox.

It can also be use to serve as function generator for vm sandbox.

It wraps a function with the specified input arguments and returns the specified output, where output must be one of the input arguments.

The idea here is that you save the definition of the function along with the generated function.

So you always know what is the input & the output.

The semi-protection is accomplished by pushing global variables names at end of the input array.

e.g. function(input, output) is what you really use, but you also push global vars there:

function(input, output, window, document, whatever, console, unused)

Those will then end up being undefined.

It's meant to enforce a certain kind of api within the function body.

Example

var IOBox = require('iobox');

var ins  = ['input','output']; // input specification
var outs = ['output'];         // output specification, must be one of the inputs.

var io = new IOBox('my-func', ins, outs);

Compile the function to return output as an Array:


io.compile('output.out = input.in');

console.log('Output as array:', io.toString());

Output as array:

function (input,output) {

  var r = function() {
    output.out = input.in; // function body handling input & output
  }();
  return [output, r];       // Output as Array
}

Compile the function to return output as an Object:


io.compile('output.out = input.in', true);

console.log('Output as object:', io.toString());

Output as object:

function (input,output) {

  var r = function() {
    output.out = input.in; // function body handling input & output
  };

  return {
    output: output  // Output as Object
    return: r       // original return
  };
}

Run with output as Array:

console.log(io.run());

['Hi', undefined]

Run with output as Object:

console.log(io.run());

{ output: { out: 'Hi' }, return: undefined }

io.toString() can be used to save the function for later use.