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

c3addon

v1.1.2

Published

Node and CLI tool to automate publishing your Addons to Construct Addons page

Readme

c3addon

This is a simple script to publish your .c3addon to the Construct Addon registry.

See how to configure GitHub Actions to publish your addon automatically.

CLI Usage

Publishing a .c3addon file

If you provide a .c3addon file, the script will publish it directly. You may also provide a directory, in which case the script will pack the directory into a .c3addon file before publishing.

npx c3addon publish <c3addon-file-or-directory> \
	--username <username> \
	--password <password> \
	--addon-url <addon-url> \
	--release-notes <release-notes>

Publishing looks at the releases already on the addon page before adding one. If that version is already published there is nothing to do; if it is there but unpublished, that release is finished off rather than a second one being made. So re-running after a failed publish picks up where it left off.

Listing releases

npx c3addon releases \
	--username <username> \
	--password <password> \
	--addon-url <addon-url> \
	[--latest] [--json]

--latest prints just the highest published version, which is a way to tell whether publishing is needed at all.

API Usage

import { publish } from "c3addon";

publish({
  addonUrl: "https://www.construct.net/en/make-games/addons/1057/testing-auto-release/",
  filename: "path/to/addon.c3addon",
  username: "your c3 username",
  password: "your c3 password",
  releaseNotes: "This is a release note",
});

Reading the releases

import { getReleases, getLatestRelease } from "c3addon";

const credentials = {
  addonUrl: "https://www.construct.net/en/make-games/addons/1057/testing-auto-release/",
  username: "your c3 username",
  password: "your c3 password",
};

// everything on the addon page
const releases = await getReleases(credentials);

// the highest published version, or null if there is not one yet
const latest = await getLatestRelease(credentials);

Both return the rows of the addon's release table, as they read on the page:

interface Release {
  id: string;           // the id in the edit URL, e.g. "2071"
  version: string;      // "1.2.0.0", or empty until a file is uploaded
  stability: string;    // "Stable" or "Beta", as the column reads it
  isBeta: boolean;
  filename: string;     // "my-addon-1-2-0-0.c3addon", empty with no file
  size: string;         // "43.58 KB", empty with no file
  publishDate: string;  // "26 Aug, 2026 at 22:35", empty when unpublished
  isPublished: boolean;
  isDeleted: boolean;   // removed releases stay in the table, struck through
  url: string;          // the release's edit page
}

A release exists from the moment it is created, before anything is uploaded to it, so version, filename and size are all empty until then. Construct reads the version out of the package rather than being told it.

getLatestRelease skips releases that are deleted, unpublished, or have no version yet, and compares versions as numbers, so 1.1.10.0 beats 1.1.9.0.

License

MIT