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

clevergy-sdk

v0.4.16

Published

Clevergy SDK

Readme

Clevergy SDK

Token authentication

Technically, this SDK can be used with a backend in Node or frontend in Typescript. To use the SDK properly, you can build it with a token already like so:

    const {clevergySdk} =  buildClevergyApiSdk(YOUR_TOKEN_HERE);

or set it at a later time:

    const {clevergySdk, setToken} =  buildClevergyApiSdk();
    ...
    setToken(YOUR_TOKEN_HERE);

Note: If you decide to set the token at a later time, any calls made before the token is set up will not work.

also, you can set as second argument a function to provide a way of get a refreshed token on each api call to avoid expired token requests.

    async function refreshTokenHandler() {
        ...
        return token;
    }

    const {clevergySdk} =  buildClevergyApiSdk(undefined, refreshTokenHandler);

To publish to NPM:

  1. In your .bashrc file (or wherever you set your ENV variables), set the CLEVERGY_NPM_TOKEN to the NPM TOKEN found in the secrets manager of GCP with the name of CLEVERGY_NPM_TOKEN

    Never commit this token to the repo. If you do, you'll have to change the token immediately.

  2. Make changes to the SDK

  3. Run npm run build

  4. Commit and push changes

  5. Run npm version patch --> upgrade version, commit and push

  6. Run npm publish if your .bashrc contains the NPM's token or run CLEVERGY_NPM_TOKEN={npm_token} npm publish

  7. Update the package where it's needed.

Keep in mind of breaking changes made in the sdk/api.