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

betterparse

v0.1.1

Published

A simple YAML parsing tool for Kubernetes manifests.

Downloads

10

Readme

BetterParse

A simple YAML parsing utility for Kubernetes manifests.

Usage

CLI

The basic usage is:

betterparse <PATH_TO_YAML> [--raw] [--out=<PATH_FOR_OUTPUT>] [--environment=<CONFIG_ENVIRONMENT>]

More detailed info can be found by running betterparse --help.

When --raw is specified without --out, the parsed YAML will be concatenated to allow for ingesting into Kubernetes as a single file:

kubectl apply -f <(betterparse ./kubernetes --raw)
Logging

To see logs, prefix the betterparse command with DEBUG=betterparse:*. These logs are sent to stderr and do not conflict with the --raw option.

Templating

config.json

The config.json file should live in the same directory as the YAML to parse.

This file should have top-level keys corresponding to the specific environment. The values inside each environment object are 100% user-defined.

{
  "staging": {
    "kubernetes": {
      "image": "",
      "imagePullPolicy": "Always",
      "replicas": 2,
      "resources": {
        "limits": {
          "cpu": ""
        },
        "requests": {
          "cpu": "",
          "memory": ""
        }
      }
    },
    "variables": {
      "loggingDisplayName": "QaWorker",
      "nodeEnv": "development",
      "rabbitmq": {
        "user": "user",
        "pass": "C4y9ACotwtrtN9Z8"
      },
      "database": {
        "user": "bv",
        "pass": "%44JvaL&EVS##ty5"
      }
    }
  }
}
YAML

Each YAML file inside the input directory will be parsed. The parser looks for the token #@ on each line

For example:

config.json (top-level environment key omitted for brevity)
{
  "path": {
    "to": {
      "replacement": "abcdefg
    }
  }
}
template.yaml
someValue: defaultValue #@ path.to.replacement

When run through the parser, template.yaml will be converted to

someValue: 'abcdefg'

Assuming the path could not be found in the config, the original value will be used:

someValue: defaultValue #@ i.dont.exist

This would produce

someValue: defaultValue