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

freemius-deployer

v2.0.0

Published

Deploy a WordPress plugin zip to Freemius.

Downloads

73

Readme

freemius-deployer

Deploy a WordPress plugin zip to Freemius.

Requirements

  • Node.js >= 22

Install

npm install --save-dev freemius-deployer

Example

Configure via a freemius-deployer.json file in your project root. These are the defaults, used for any key you omit:

{
  "zipPath": "dist/",
  "zipName": "project-slug.zip"
}

Then add a script in package.json:

"scripts": {
  "deploy": "freemius-deployer"
}

Configure .env with following keys. (Important: add .env to .gitignore — it contains your API token.)

FREEMIUS_PRODUCT_ID=12345
FREEMIUS_API_TOKEN="YOUR_API_BEARER_TOKEN"

Get the API token from the Freemius Developer Dashboard: open your product's Settings page, then the API & Keys tab.

CLI flags

  • -d, --dry-run — validate without uploading
  • -c, --config <path> — use a different config file
  • -e, --env-file <path> — use a different env file
  • -q, --quiet — suppress non-error output
  • -r, --release-mode <pending|beta|released> — release status to set on the uploaded version (default: pending)
  • -h, --help — show usage and exit
  • -v, --version — show version number and exit

By default, an uploaded version stays pending — not visible to customers — until you release it. Pass --release-mode released to make it live immediately, or --release-mode beta to make it visible only to beta testers.

License

MIT © 2026 Nilambar Sharma