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

nonstop-cli

v0.2.3

Published

nonstop CLI for building, packaging and uploading locally

Downloads

3

Readme

nonstop cli

This project provides a command line interface for building, packaging and uploading your project(s) locally from the shell. This allows you to make changes to the build file and know exactly how the build will run on a build agent after you've pushed your code. It also allows you to explore any number of interesting use cases outside of the usual CI server/build agent interaction pattern.

Things to keep in mind

Version is always determined by a file. For node projects, package.json should provide the version. *.app.src is how you should specify version in Erlang. The convention for .Net/Mono projects is to put a version attribute for the assembly in AssemblyInfo.cs. In the event nonstop cannot determine where to get the version, it will ask you which file it should read the version from.

Build count is determined by the number of commits that exist for a version. If you want to produce a package with a new build number, you'll need to create a commit first. nonstop will not overwrite an existing package unless you use a force flag ( -f or --force) to prevent accidentally changing the contents of a package based on code that belongs in a new commit.

Use cases

This CLI exists to support four primary use cases:

Build and pack

By default, nonstop will build and package the result (in the event of a successful build). Packages will be created in './packages' (add this path to your .gitignore and .npmignore).

As mentioned above, if a package has already been created for the last commit in your repository, nonstop will not replace the package without a force flag.

Builds all projects

ns

Build a specific project

ns --project [projectName]

Build only

If you only want to see the result of the build and not create a package, you can use this command to test the status of your build.

Builds all projects without creating packages

ns nopack

Build a specific project without creating a package

ns nopack --project [projectName]

Build file creation

If you don't have a build file and run nonstop, you'll be asked if you'd like help creating a build file. This interactive console mode will walk you through a series of steps and attempt to help you create a build file.

Uploading

This command can upload one or more packages generated from a build.

Upload one or more packages selected from a list

ns upload

Upload a specific package

ns upload ./packages/[specificPackageFile].tar.gz

Upload latest package without prompts

ns upload --latest --index [index address] --port [index port] --token [auth token]

Upload latest package over HTTPS, without prompts and custom api url

ns upload --latest --secure --index [index address] --url /prefixed/api --port [index port] --token [auth token]

Dependencies

This project depends on several core nonstop modules:

It also was made possible by several great Node modules:

  • machina
  • when
  • commander
  • inquirer
  • lodash