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

@camoto/gamecomp-cli

v1.0.0

Published

CLI for gamecomp.js, for use with `npm install -g`

Downloads

7

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

malvineousmalvineous

Keywords

Readme

This is just a dummy class to install only the devDependencies needed to run the command-line interface.

It is intended to be installed globally with npm install -g (or via a Linux distribution's package manager) to make the library's command-line interface available anywhere on the system.

It avoids two problems:

  1. The dependencies only used by the CLI can be put in as devDependencies, so they don't have to be installed when the library is used by other projects, where the CLI isn't used anyway.

  2. All the other devDependencies (like the test framework and linting tools) don't get installed like they would if the library itself was installed in dev mode.

  3. The CLI can still be distributed with the core library so it can be easily used during development for testing new features.