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

companion-module-hello

v0.3.3

Published

A minimal out-of-tree Companion module: one permission, one route, one table, one page.

Readme

companion-module-hello

A minimal out-of-tree module for Companion. It declares one permission (hello:greet), runs one migration (the hello_greetings table), serves one authenticated route (POST /api/hello/greetings) and renders one page at #/hello. It exists to be read, copied, and installed into a running daemon as a working reference for the external module guide.

Layout

src/module.ts        the manifest: pure data, imported eagerly at boot
src/contract/       the registry augmentation and shared DTOs
src/api/            acl, migrations, store, routes: the server slice
src/client/         nav, routes, page: the browser slice
build.mjs           esbuild, with the ABI marked external

The module depends on exactly two packages, both as devDependencies plus peerDependencies and never as runtime dependencies: @moxxy/companion-sdk (the authoring surface) and @moxxy/companion-contracts (the one specifier registry augmentation must target). The build marks both external, so at load time every import resolves to the host's single copy.

Build and check

npm install
npm run build            # emits dist/module.js, dist/api.js, dist/client.js
companion module verify .    # static ABI check, no daemon needed

Install into a Companion instance

companion module add companion-module-hello   # or: companion module add .
# restart Companion so it rescans the modules directory
companion module install hello

The page appears in the tool catalog for any signed-in role, and the route answers under the hello:greet permission.

Start your own module from this one

companion module scaffold my-module

copies this package with the name, module id and title substituted.