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 🙏

© 2026 – Pkg Stats / Ryan Hefner

toberemoved

v0.1.0-SNAPSHOT

Published

FIXME: write this!

Downloads

5

Readme

gh-cli

FIXME: Write a one-line description of your library/project.

Overview

FIXME: Write a paragraph about the library/project and highlight its goals.

cljs-node-app Template Docs

Overview

The following code structure has been created:

.
├── LICENSE
├── README.md
├── project.clj
├── src
│   └── gh_cli/core.cljs
└── test
    ├── gh_cli/core_test.cljs
    └── gh_cli/core_runner.cljs

Editing

Edit src/gh_cli/core.cljs and create other files in src as your node application. Make sure to (set! *main-cli-fn* some-fn) for the main build export. Note that its best to just access (.-argv cljs.nodejs/process) to get command line arguments.

Usage

You should lein npm install before doing anything to ensure you get the source-map-support library.

To build the clojurescript into a node script, use lein build (aliased to lein cljsbuild once main). To then run the node app use node build/main.js.

You can add clojure and clojurescript dependencies in the normal :dependency spot. You can also add npm dependencies in the :npm {:dependency []} spot.

Testing

To test once, use lein test (which is aliased to lein doo node test-node once). To watch code for changes and re-test, use lein test-auto.

Distribution

You can distribute your app via npm by doing the following:

  • Uncomment the line ["npm" "publish"] in the :release-tasks section of project.clj
  • Edit :npm {:package {...}} in project.clj as you would your package.json file. See npm docs for details. (If you want to distribute a public library, use :private false.

To create a build for release, simply call lein release. This calls lein do clean, build, tags the commit, and deploys a build to either/both a maven repo and/or npm.

License

Copyright © 2015 FIXME

Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.