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

occam-open-cli

v6.0.135

Published

Occam's command line package management tool.

Downloads

579

Readme

Occam Open-CLI

Occam's command line package management tool.

This readme file is mostly for developers. For instructions tailored to end users, see the following:

https://openmathematics.org/how-to-contribute

Contents

Installation

If you would like to contribute or would simply like to have a look at the code, you can clone the repository with Git...

git clone https://github.com/djalbat/occam-open-cli.git

...and then install the dependencies with npm from within the project's root directory:

npm install

Usage

These are the commands and options:

  open [<command>] [<argument>]

Commands:

  help                                           Show this help
  
  version                                        Show the version

  [install] <package_name>                       Install a package

  initialise                                     Create a configuration file

  set-options                                    Set options 

  clone <package_name>                           Clone a package with Git

  publish <package_name>                         Publish a package

  withdraw <package_name>                        Withdraw a package

  create-account [<email_address>]               Create an account
   
  sign-in [<email_address_or_username>]          Sign in 

  sign-out                                       Sign out 

  reset-password [<email_address>]               Reset password 

  set-shell-commands                             Set shell commands 

Options:

  --help|-h                                      Show this help

  --version|-v                                   Show the version

  --quietly|-q                                   Run with almost no console logging

  --log-level|-l                                 Set the log level when publishing
  
  --yes|-y                                       Initially answer yes to prompts

  --tail|-t                                      Sets the size of the tail of the log messages when publishing. The default is ten. 

  --follow|-f                                    Show all of the log messages when publishing. The default is false.

This is slightly different from npm in that open is usually executed from the parent directory of a project rather than from within the project sub-directory itself.

Building

Automation is thanks to npm scripts, have a look at the package.json file. The pertinent commands are:

npm run build-debug
npm run watch-debug

Contact