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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@withjoy/sdk-js

v0.2.0

Published

Joy Javascript SDK

Downloads

178

Readme

Joy Javascript SDK

Installing or Upgrading Packages

Please follow the Best Practices for Care & Feeding of 'npm-shrinkwrap.json'.

Presently, the 'npm-shrinkwrap.json' can be successfully re-generated using Node 6 + npm@3. There is no need to switch to Node 10 + npm@6, as the Wiki above suggests.

If the above fails:

Switch to node 16

nvm use 16

Run yarn instead of npm

yarn install --frozen-lockfile

Switch back to node 6.9

nvm use

Test to verify an working bulid

npm test

Publishing

To publish a new version of this module,

  • do not up-version on your development branch
  • merge your fixes into main
  • from the main branch,
npm version patch  # or whatever is suitable

See npm's examples of the different levels of versions (major, minor, patch, etc.)

As a verification step (via 'preversion'),

  • a fresh (local) build is produced
  • the Test Suite must pass

As a follow-up,

  • package.json is up-versioned
  • a semver-ish tag is pushed to Git
  • CircleCI will perform the npm publish operation when it detects the tag
  • it's ready once the 'versions' in npm info @withjoy/sdk-js have been updated

CircleCI

Its Project uses the following Environment Variables:

  • ARTIFACTORY_TOKEN
  • NPM_TOKEN