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

@doist/integrations-common

v2.2.2

Published

Common utilities for integrations written with Typescript.

Downloads

2,139

Readme

integrations-common

Common utilities for integrations written with Typescript.

Installation

npm install @doist/integrations-common

Development + Testing

Instead of having an example app in the repository to assist development and testing, we have included ts-node as a dev dependency. This allows us to have a scratch file locally that can import and utilize the modules in the project while developing or reviewing pull requests without having to manage a separate app project.

  • Add a file named scratch.ts in the src folder.
  • Configure your IDE to run the scratch file with ts-node (instructions for VSCode, WebStorm), or you can optionally run ts-node in a terminal using instructions here.
  • Import and call the relevant modules and run the scratch file.

Example scratch.ts file:

import { pickRandomString } from './utils/stringUtils'

const randomChoice = pickRandomString(['Option A', 'Option B', 'Option C'])
console.log(randomChoice)

Publishing

This project uses semantic versioning. A new version will be published to GitHub Package Registry when a new tag is pushed. This is done via semantic-release so please check your PR commit messages for the correct format.

npm version <major|minor|patch>
git push --follow-tags