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

@intentius/chant-lexicon-k3s

v0.45.0

Published

k3s lexicon for chant — the k3s distro's host configuration as declarable data

Downloads

1,661

Readme

@intentius/chant-lexicon-k3s

k3s lexicon for chant — the k3s distro's host configuration as declarable data.

Declares the files k3s itself consumes: config.yaml for k3s server / k3s agent (every CLI flag as a YAML key, typed from the pinned release's own flag definitions), and registries.yaml for the embedded containerd. The emitted files are exactly what the native tool accepts.

The join token is deliberately not declarable: the surface carries only the reference forms (token-file, agent-token-file), and K3S001/K3S101 fail a literal that arrives anyway.

Getting started

# Generate types from the pinned k3s release (v1.36.3+k3s1)
npm run generate

# Validate generated artifacts
npm run validate

# Tests (the Docker-gated acceptance test boots rancher/k3s on the emitted config)
npx vitest run lexicons/k3s

Project structure

  • src/plugin.ts — LexiconPlugin with all lifecycle methods
  • src/serializer.ts — config.yaml / registries.yaml emitter
  • src/spec/fetch.ts — pinned upstream sources (the CLI flag definitions)
  • src/codegen/parse.ts — Go flag-definition parser
  • src/lint/ — K3S001 pre-synth rule, K3S101–K3S105 post-synth checks
  • src/lsp/ — completions and hover from the generated registry
  • src/generated/ — generated artifacts (do not edit)