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

nscale-planner

v0.1.1

Published

Plan your deployements, easily

Downloads

5

Readme

nfd-planner

Plan your deployments, easily! This module is not though of being used alone, but rather it is a internal dependency of nscale.


var  amiDefinition = {
        "name": "Virtual Machine"
      , "type": "aws-ami"
      , "id": uuid.v1()
    }

  , origin = {
        "name": "white sheet"
      , "namespace": "white sheet"
      , "id": uuid.v1()
      , "containerDefinitions": []
      , "topology": {
            "containers": {}
        }
    }

  , machine = {
        "id": uuid.v1()
      , "containerDefinitionId": amiDefinition.id
      , "specific": {
            "ipaddress": "10.74.143.152"
        }
    }

  , dest = {
        "name": "single instance"
      , "namespace": "single instance"
      , "id": uuid.v1()
      , "containerdefinitions": [ amidefinition ]
      , "topology": {
            "containers": {}
        }
    }

machine.containedBy = machine.id

dest.topology.containers[machine.id] = machine

console.log(planner(origin, dest))
//prints
//[{
//   cmd: "add"
// , id: machine.id
// , parent: machine1.id
//}, {
//   cmd: "start"
// , id: machine.id
// , parent: machine1.id
//}, {
//   cmd: "link"
// , id: machine.id
// , parent: machine1.id
//}]

See examples/whitesheet.js for an example with an ELB, an AMI and 2 docker instances.

See examples/dirty.js for an example that spin up an AMI with a new docker instance within an ELB. docker instances.

For the sake of simplicity, each commands includes the parent id. This is where the command will be executed most of the time.

Safe deployment

The default mode of planning is 'quick', which means that the parent is not unlinked before operating. This is quicker than 'safe' mode that unlink the parent before operating, i.e. it removes an AMI instance from the ELB. Usage:

planner(origin, dest, { mode: 'safe' })

License

Artistic License 2.0.