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

@lime.it/blip

v1.0.2

Published

Project facilitator for people with little time and little desire to work

Downloads

5

Readme

@lime.it/blip

Project facilitator for people with little time and little desire to work

Version CircleCI Downloads/week License

Usage

$ npm install -g @lime.it/blip
$ blip COMMAND
...

Commands

blip destroy

Destroys a blip environment deleteing its machines.

USAGE
  $ blip destroy

OPTIONS
  -h, --help  show CLI help
  -y, --yes   If set make yes the default answer to adavance prompts.

See code: src/commands/destroy.ts

blip docker

Wraps docker command to trigger blip decorators.

USAGE
  $ blip docker

OPTIONS
  -h, --help  show CLI help

See code: src/commands/docker.ts

blip docker-compose

describe the command here

USAGE
  $ blip docker-compose

OPTIONS
  -h, --help  show CLI help

See code: src/commands/docker-compose.ts

blip docker-machine

Wraps docker-machine command to trigger blip decorators.

USAGE
  $ blip docker-machine

OPTIONS
  -h, --help  show CLI help

See code: src/commands/docker-machine.ts

blip down

Bring down a blip workspace, stopping its machines.

USAGE
  $ blip down

OPTIONS
  -h, --help  show CLI help

See code: src/commands/down.ts

blip env [MACHINE]

Prints the docker-machine env for the workspace given machine.

USAGE
  $ blip env [MACHINE]

ARGUMENTS
  MACHINE  Name of the workspace machine. If not specified the first will be used.

OPTIONS
  -h, --help     show CLI help
  --shell=shell  [default: bash] Command output destination shell type.

See code: src/commands/env.ts

blip git

Wraps git command to trigger blip decorators.

USAGE
  $ blip git

OPTIONS
  -h, --help  show CLI help

See code: src/commands/git.ts

blip help [COMMAND]

display help for blip

USAGE
  $ blip help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

blip init [PROJECTNAME]

Initialize a blip workspace in the current directory.

USAGE
  $ blip init [PROJECTNAME]

ARGUMENTS
  PROJECTNAME  Name of the project to be created. If missing it will be set to the name of the current directory.

OPTIONS
  -h, --help                             show CLI help
  --machine-cpu-count=machine-cpu-count  [default: 1] Docker machine cpu count
  --machine-disk-size=machine-disk-size  [default: 20480] Docker machine disk size MB
  --machine-driver=machine-driver        [default: virtualbox] Docker machine driver
  --machine-name=machine-name            Docker machine name for the project
  --machine-ram-size=machine-ram-size    [default: 2048] Docker machine ram size MB
  --skip-git                             When true, does not initialize a git repository.
  --skip-setup                           When true, does not creates workspace machines.

See code: src/commands/init.ts

blip inspect [MACHINE]

describe the command here

USAGE
  $ blip inspect [MACHINE]

ARGUMENTS
  MACHINE  Name of the workspace machine. If not specified the first will be used.

OPTIONS
  -h, --help  show CLI help

See code: src/commands/inspect.ts

blip ls

List the available blip machines

USAGE
  $ blip ls

OPTIONS
  -h, --help  show CLI help

See code: src/commands/ls.ts

blip plugins

list installed plugins

USAGE
  $ blip plugins

OPTIONS
  --core  show core plugins

EXAMPLE
  $ blip plugins

See code: @oclif/plugin-plugins

blip plugins:install PLUGIN...

installs a plugin into the CLI

USAGE
  $ blip plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  plugin to install

OPTIONS
  -f, --force    yarn install with force flag
  -h, --help     show CLI help
  -v, --verbose

DESCRIPTION
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command 
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in 
  the CLI without the need to patch and update the whole CLI.

ALIASES
  $ blip plugins:add

EXAMPLES
  $ blip plugins:install myplugin 
  $ blip plugins:install https://github.com/someuser/someplugin
  $ blip plugins:install someuser/someplugin

See code: @oclif/plugin-plugins

blip plugins:link PLUGIN

links a plugin into the CLI for development

USAGE
  $ blip plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

DESCRIPTION
  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello' 
  command will override the user-installed or core plugin implementation. This is useful for development work.

EXAMPLE
  $ blip plugins:link myplugin

See code: @oclif/plugin-plugins

blip plugins:uninstall PLUGIN...

removes a plugin from the CLI

USAGE
  $ blip plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

ALIASES
  $ blip plugins:unlink
  $ blip plugins:remove

See code: @oclif/plugin-plugins

blip plugins:update

update installed plugins

USAGE
  $ blip plugins:update

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

See code: @oclif/plugin-plugins

blip tpl [COMMAND]

Execute available template commands

USAGE
  $ blip tpl [COMMAND]

OPTIONS
  -h, --help  show CLI help

See code: src/commands/tpl/index.ts

blip tpl:help COMMAND

Shows help of an available tempalte command

USAGE
  $ blip tpl:help COMMAND

OPTIONS
  -h, --help  show CLI help

See code: src/commands/tpl/help.ts

blip tpl:ls

List the available workspace templates

USAGE
  $ blip tpl:ls

OPTIONS
  -h, --help  show CLI help

See code: src/commands/tpl/ls.ts

blip tpl:use [TEMPLATENAME]

Use a specified template

USAGE
  $ blip tpl:use [TEMPLATENAME]

ARGUMENTS
  TEMPLATENAME  Name of the template to use. If absent it will be asked.

OPTIONS
  -h, --help  show CLI help
  -y, --yes   If set make yes the default answer to adavance prompts.
  --none      If set no template will be used. If one is currently in use its teardown procedure will be invoked.

See code: src/commands/tpl/use.ts

blip up

Bring up a blip workspace, starting machines and enforcing configuration.

USAGE
  $ blip up

OPTIONS
  -h, --help  show CLI help

See code: src/commands/up.ts