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

@xcwds/plugin-changelog

v0.5.0

Published

What's new for @xcwds apps: release notes on the settings page, a New badge on the ones not seen yet, and a toast after an update.

Downloads

459

Readme

@xcwds/plugin-changelog

What's new for an @xcwds app on @xcwds/sveltekit: release notes on the settings page, a New badge on the ones the user hasn't seen yet, and a toast after an update that links to them.

// src/lib/changelog.ts: one entry per change people will notice, newest first
import type { ChangelogEntry } from '@xcwds/plugin-changelog';

export const changelog: ChangelogEntry[] = [
	{ id: 2, date: '2026-10-09', items: ['Timers keep ringing on every page.'] },
	{ id: 1, date: '2026-10-08', items: ['The first version.'] }
];
// xcwds.config.ts
import { defineConfig } from '@xcwds/core';
import changelog from '@xcwds/plugin-changelog';
import settings from '@xcwds/plugin-settings';
import shell from '@xcwds/plugin-shell';
import update from '@xcwds/plugin-update';
import { changelog as entries } from './src/lib/changelog.js';

export default defineConfig({
	brand,
	plugins: [shell({ sections }), settings(), update(), changelog({ entries })]
});
/* src/app.css, after Tailwind and the shell's styles */
@import '@xcwds/plugin-changelog/styles.css';

Options

  • entries: { id, date, items } newest first, with whole-number ids that grow (checked when the config loads). Keep them in their own module, as above: the config is plain data, so it takes the entries rather than a path to them.
  • show: how many entries What's new lists. Defaults to 10.
  • storageKey: where the newest entry seen is saved. Defaults to app:changelog:seen; set it to keep a key an app already uses.

What it does

  • A fresh install (or cleared data) badges nothing and saves nothing: until What's new is opened, the newest entry counts as seen. After an update, entries newer than the ones the old version had are badged until What's new shows them. The old version carries its newest id across with @xcwds/plugin-update's handover; when it carried none (it predates this plugin), only the newest entry counts as new.
  • After an update, app.toast (from @xcwds/plugin-shell) says "App updated." with a link to What's new when there is something new, and "App updated to the latest version." otherwise.
  • With @xcwds/plugin-settings, What's new is a section of the settings page (after About), at #whats-new. Without it, place <WhatsNew /> from @xcwds/plugin-changelog/WhatsNew.svelte inside <App> yourself.
  • app.changelog has entries, latest, seen(), markSeen() and subscribe(listener).