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

@discourse/update-skeleton

v0.1.0

Published

Update Discourse theme and plugin scaffolding and install its dependencies

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

cvx-plcvx-pldiscourse-npmdiscourse-npmsam.saffronsam.saffronjoffreyjaffeuxjoffreyjaffeuxpmusarajpmusarajdavidtaylorhqdavidtaylorhqkeegangeorgekeegangeorgefalcofantasticfalcofantastic

Keywords

Readme

@discourse/update-skeleton

Update a Discourse theme or plugin's scaffolding and install its dependencies. Requires Node.js 22.13+, pnpm, Ruby, and Bundler.

Run from the theme or plugin root:

pnpx @discourse/update-skeleton@latest

Skeletons also provide pnpm update-skeleton, which runs that command without adding the updater as a dependency. For local development, run node /path/to/update-skeleton/bin/update-skeleton.js.

What it does

  1. Detect a plugin using plugin.rb, otherwise a theme using about.json.
  2. Fetch current files from the matching skeleton's raw.githubusercontent.com /main/ URLs, without using the GitHub API.
  3. Merge package dependencies, scripts, and engine settings. Replace lint configs, TypeScript config, Gemfile, and standard workflows; remove obsolete configs. Append required .gitignore entries. Plugin TypeScript paths use its name header.
  4. Install with pnpm, then run bundle install, bundle update --bundler, and bundle update --all.
  5. Print lint and autofix commands for you to run.

Managed configs are overwritten, including customizations. Unrelated package data and source files are preserved. Updates write directly to disk; failures leave completed changes in place. Fix the error and rerun. No state file or dry run.

pnpm installs stay within this project and include dev dependencies, even with NODE_ENV=production. Ruby gems are updated within the Gemfile's constraints.

Development

pnpm install
pnpm lint:fix
pnpm lint
pnpm test
pnpm pack

The implementation uses execa for running commands and Node built-ins for files and HTTP. Tests use local skeleton fixtures and stub the installers. ESLint and Prettier use @discourse/lint-configs.

Releases

Like lint-configs, CI publishes unpublished versions to npm after checks pass on main. To release, bump version in package.json and merge to main. Already published versions are skipped by pnpm publish -r.

Configure an npm trusted publisher for the package: organization discourse, repository update-skeleton, workflow ci.yml, no environment, with direct publishing allowed. No npm token secret is needed. If the package does not exist yet, publish its first version manually before configuring the trusted publisher.