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

cse-cli

v0.4.3

Published

⌨ The CLI for all things Commercial Software Engineering

Downloads

6

Readme

The CSE CLI

codecov npm version Build, Test and Coverage

A command-line interface for all things Commercial Software Engineering.

Getting Started

Running CLI from src

In the root of the repo, run npm link to create a symbolic link in your local npm configuration. If you'd like to use the CSE cli in a separate directory, navigate to that directory and run npm link cse-cli.

You will then be able to execute commands with the cse executable inside that directory.

Running Tests

In order to run tests (both unit and integration), set the environment variables specified in the .env.sample file.

The tests have already been configured to read variables from the .env file.

Installation

Run npm i at root.

Configuration

Configuration is located at src/config.

Build

At root, run npm run build.

Test

At root, run npm run test.

Run

Run cse to see the subcommands available.