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

@emdzej/ncsx-patches

v0.8.0

Published

Shareable coding patches for ncsx — YAML files that describe FSW/PSW changes across one or more modules, with metadata for discoverability and runtime compatibility checks against the current FunctionList.

Readme

@emdzej/ncsx-patches

YAML patch format + reader/writer for shareable NCS coding changes (.ncsxpatch.yaml).

A patch is the rich-format cousin of FSW_PSW.MAN: same FSW/PSW edits, wrapped in metadata (title, description, author, keywords, chassis, optional CI pin, optional require_current assertions) and capable of carrying multiple module blocks in a single file.

Schema reference, compatibility model, and UI flow are documented in docs/patches.md.

Usage

import {
  buildPatchFromCurrent,  // (in apps/web only — pulls in FunctionList)
  parsePatch,
  serializePatch,
  resolveModulePatch,
  modulesForCurrent,
  type PatchFile,
} from '@emdzej/ncsx-patches';

// Read a patch file
const patch: PatchFile = parsePatch(readFileSync('feature.ncsxpatch.yaml', 'utf-8'));

// Resolve against a loaded FunctionList
const { resolved, warnings } = resolveModulePatch(patch.modules[0], functionList);
// `resolved.targets` is a Record<fsw_id, psw_id> ready to merge into the
// FunctionTree's staged-edits state.

// Round-trip
writeFileSync('out.ncsxpatch.yaml', serializePatch(patch));

Exports

| Export | Purpose | |---|---| | parsePatch(text) | YAML → PatchFile with zod validation. Throws PatchSchemaError on invalid input. | | serializePatch(patch) | PatchFile → YAML. Block-literal description, flow-style keywords/coding_indexes. | | resolveModulePatch(modulePatch, list, currentCi?) | Translate keyword edits → numeric targets. Returns warnings for unresolved entries + soft CI mismatch. | | checkRequireCurrent(modulePatch, list, netto, decodeCurrentPsw) | Evaluate require_current against a netto buffer. | | modulesForCurrent(patch, moduleName) | Pick the patch entries that apply to a given SG (case-insensitive). | | targetsToEdits(list, targets) | Inverse of resolveModulePatch — Record<fsw_id, psw_id> → Record<FSW_KW, PSW_KW>. | | mergeModulePatch(patch, next, mode) | Splice or replace a module block in an existing patch. |

License

PolyForm Noncommercial 1.0.0 — free for personal, research, and hobby use.