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

@jonallured/jay

v0.3.0

Published

Various cli tricks and stunts.

Downloads

27

Readme

jay CircleCI

This project is a collection of commands that I find helpful. It's built using the oclif framework.

Installation

This is a published NPM package, so you can install with yarn or whatever:

$ yarn add @jonallured/jay
# or
$ yarn global add @jonallured/jay

I used to just run this locally, like so:

$ c jay
$ npm link
$ asdf reshim

You don't always have to reshim, but if it doesn't link right, then that's probably the issue.

Running checks

This project is setup to comply with the following checks:

  • prettier
  • eslint
  • Typescript
  • jest

See the package.json for individual commands, but to run all of this together, one can do this:

$ ./bin/check-all

And so if that is green locally there's an excellent chance that CI will be green too.

Updating dependencies

There's a script for this so updating to the latest version of dependencies should be as easy as this:

$ ./bin/update

This will run yarn upgrade --latest and then create a PR after running all the checks locally. That PR will need to be manually merged.

Releasing

I've set things up so that CircleCI can release new package versions automatically based on pushing tags, so one can cut a new version like so:

$ ./bin/release

That will:

  • update the required files with new version numbers
  • commit that change and push to master
  • tag that commit
  • push that tag

Which in turn triggers a build that has access to NPM creds and will publish the package without running tests because YOLO.