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

@commversion/libs

v0.16.10

Published

A set of Commversion's public facing scripts and utilities.

Readme

Commversion public facing libraries

A set of Commversion's public facing scripts and utilities.

Installation & Configuration

The library is distributed as a public facing npm package.

The recommended way to install this on a website is through JsDelivr.com.

<script src="https://cdn.jsdelivr.net/npm/@commversion/libs@version/dist/schedule-event.js"></script>

Configuration

Configuration takes place by global window.commversion object, make sure to not overwrite it if it already exists!

<script>
  window.commversion = window.commversion || {};
  window.commversion.someProperty = true;
</script>

Available scripts

All scripts are available under the scripts/ directory.

  • schedule-event
  • lc-open-on-button-click
  • lc-cookie-banner-update-position
  • lc-show-by-selector
  • lc-exit-intent-debounced
  • lc-pause-on-url
  • lc-kill-chat-persist
  • lc-gclid
  • lc-powered-by
  • lc-ga-initialize-event
  • lc-exit-intent
  • lc-ga-tags
  • lc-input-errors
  • lc-show-hide
  • lc-kill-chat
  • lc-form-abandonment
  • lc-form-submission
  • lc-experiment
  • lc-gtm
  • lc-device
  • lc-geoblocking
  • lc-utm-params

Release new versions

Important This project uses the npm.js public registry. Before trying to do any release, make sure you are logged with npm as Commversion. The quickest way to do that, is to create a .npmrc file in the project directly and insert the following:

//registry.npmjs.org/:_authToken=base64_encoded_npm_token

You can test if the above works by running:

$ npm whoami
commversion       # this is the authenticated npm user

The project follows the semantic versioning convention.

Patch releases for bug fixes. Minor releases for new features. Major releases for breaking changes.

The release is fully automated by executing npm run release. No need to run build scripts beforehand, this is done automatically.

Guideline for contributing

To create a new script, run the following command in a shell.

$ npx hygen scripts new script-name

The command above will create e new script containing the absolute minimum files. It will also amend root README.md and package.json to include required entries.

Start working on a specific script by running npm run package:dev.

Finally, you can run tests by running:

$ npm test