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

@rikology/pupitre-settings

v1.0.0

Published

Typed grouped settings pages for Pupitre

Readme

@rikology/pupitre-settings

Typed grouped settings for Pupitre, with custom pages, JSON values and atomic saves.

import { defineSettings, settings, settingsFor, saveSettings } from '@rikology/pupitre-settings'
import { definePanel, t } from '@rikology/pupitre'

const general = defineSettings('general')
  .label(t('General'))
  .form((s) => [s.text('siteName').required(), s.toggle('maintenanceMode')])
  .defaults({ siteName: 'Pupitre', maintenanceMode: false })
  .scope('global')

export default definePanel('admin').plugins([
  settings({ groups: [general], authorize: (ctx) => Boolean(ctx.auth.user?.isAdmin) }),
])
const values = await settingsFor(general)
await saveSettings(general, { maintenanceMode: true })

Run node ace add @rikology/pupitre-settings and node ace migration:run before using the plugin. Authorization fails closed unless a callback permits access or host SettingsPolicy.viewAny(user) and SettingsPolicy.manage(user, group) both permit it. Trusted server APIs do not enforce HTTP authorization. Tenant groups require the resolved active tenant in HTTP, or { tenant: { id } } in commands/jobs. Reads merge defaults; unknown stored keys are ignored and unknown patch keys rejected. Form validation and all changed-key writes run in one transaction.

Values are JSON envelopes with Lucid-managed timestamps. Request-only caching avoids stale cross-process reads. clearSettingsCache(ctx?) clears the active request cache. The audit adapter is read-only, so this package does not emit audit events. See the settings guide for policy, Shield, tenancy, storage and migration details.

Development: npm run build, npm run quick:test, npm run typecheck. Tests use isolated SQLite by default; DB=pg DATABASE_URL=postgres://.../pupitre_settings_test npm run quick:test requires a disposable database with test in its name.