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

@janiscommerce/sdk

v0.1.3

Published

An SDK to interact with Janis easily

Readme

sdk

Build Status Coverage Status npm version

An SDK to interact with Janis easily

Installation

npm install @janiscommerce/sdk

API

Auth

This SDK implements the OAuth Authorization Code flow + PKCE, which is the recommended flow for Web and Native APPs.

You can see this module API in the following examples:

Authorization Request

const { Auth } = require('@janiscommerce/sdk');

const options = {
	client_id: 'YOUR_APP_CLIENT_ID', // Required
	client_secret: 'YOUR_APP_CLIENT_SECRET', // Not required yet
	redirect_uri: 'YOUR_APP_REDIRECT_URI', // Required
	scope: 'scope to authorize', // Recommended
	state: 'optional app state'
};

const authClient = new Auth(options);

const {
	codeVerifier,
	codeChallenge,
	codeChallengeMethod
} = await authClient.generatePKCEChallenge();

// Store safely to fetch the tokens later
storeSafely(pkceChallenge.codeVerifier);

const authorizeUrl = authClient.getAuthorizeUrl({
	code_challenge: codeChallenge,
	code_challenge_method: codeChallengeMethod
});

window.location.href = authorizeUrl;

Tokens Fetching and Refreshing

const { Auth } = require('@janiscommerce/sdk');

const options = {
	client_id: 'YOUR_APP_CLIENT_ID', // Required
	client_secret: 'YOUR_APP_CLIENT_SECRET', // Required for fetching and refreshing tokens
	redirect_uri: 'YOUR_APP_REDIRECT_URI' // Required
};

const authClient = new Auth(options);

// Retrieve the verifier from your storage
const codeVerifier = fetchCodeVerifierFromSafeStorage();

const [, authorizationCode] = window.location.search.match(/[?&]code=([^?&]+)/) || [];

const {
	tokenType,
	expiresIn,
	scope,
	accessToken,
	idToken, // This is only returned if openid scope is authorized
	refreshToken // This is only returned if offline_access scope is authorized
} = await authClient.getTokens({
	code: authorizationCode
	codeVerifier: codeVerifier
});

const userData = await authClient.decodeIdToken(id_token);

console.log(`Hello ${userData.name}!`);

// refreshTokens() response has the same structure than getTokens()
const newTokens = await authClient.refreshTokens(refresh_tokens);

The Auth by default uses Janis Production endpoints. But if you need to test against the QA environment, or even if you want to use it against a custom Authorization server (for example, Google's), you can pass an extra argument to each method:

  • getAuthorizeUrl(appInfo, 'https://accounts.google.com/o/oauth2/v2/auth')
  • getTokens(authorizationData, 'https://oauth2.googleapis.com/token')
  • decodeIdToken(idToken, 'https://www.googleapis.com/oauth2/v3/certs')
  • refreshTokens(refreshTokens, 'https://oauth2.googleapis.com/token')