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

@busy-web/cli

v1.0.1

Published

Command line tools to enhance web dev tasks

Downloads

79

Readme

cli

Command line to for node and emberjs shorcut commands

Install

npm i -g @busy-web/cli

Docs

Usage:

busyweb ‹command› [options]

OPTIONS:

--boring Hide title and version information and remove empty new lines
--debug Turn debug mode on

Example:

busyweb help => print usage information

Commands:

deploy ‹branch›
deploy build to server.
Alias: d
dev:clean
remove packages, and build files
Alias: dev:c
dev:install
clean project install fresh packages
Alias: dev:i
Options:
  --rebuild removes the lockfile and generates a new lockfile based on current package.json only on <install>
dev:update
install missing packages
Alias: dev:up
dev:upgrade
update packages and regenerate yarn.lock file
Alias: dev:u
docker ‹config› ‹EMBER_CONFIG.PATH:DOCKER_ENV...›
DEPRECATED: Please use `env:config` inplace of `docker config`
injects docker config into built ember app
ember:init
installs new files from the current installed version of ember-cli. (ember:update should be ran first)
Alias: em:i
Options:
  --diff use git difftool to merge files after init
ember:update [version]
update ember-cli locally or globally
Alias: em:up
Options:
  --global update global ember install
  --dry performs a dry run where no update will be performed
env:config ‹EMBER_CONFIG.PATH:ENV_VAR...›
injects ENV variables into and ember app config/environment
Alias: env:c
Options:
  --path <path> path/to/folder where file config changes are. ( default: Current Working Directory )
  --file <name> filename to replace config settings for. ( default: index.html )
  --require throw error if config or ENV settings do not exist. ( default: false )
  --allow-null allow null values to be set from ENV to APP config
release ‹type›
tag a new version to be released with a git tag. ARGS type: [ patch | docker | canary | alpha | beta | prod ]
Alias: r
Options:
  --no-commit prevent version from committing and creating a new tag
  --tag [name] tag the version and push to remote [name], default: origin
  --push [name] push changes to remote [name], default: origin
  --branch [name] override the current branch, default: current branch
release:prune ‹version› [type]
Prune a release type by version
Alias: r:p
Options:
  --dry shows the tags that would be deleted but doesnt do anything
  --all delete all tags matching the version and type
  --mod <number> mod number to prune the tags with, default: 5
  --remote [name] flag to prune remote tags for [name], default: origin
  --prod production tags can only be deleted with --prod option applied.
template ‹type› ‹name›
creates a new template file. (not supported yet)
Alias: t
Options:
  --delete deletes a template file

Contribute

Contributions are welcome.

  1. Fork the repo and make the desired changes.
  2. yarn run docs to regenerate readme file.
  3. Then submit a PR request for review.