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

@logarys/pipeline-validator

v0.2.0

Published

Validation helpers for Logarys pipeline runtime JSON configuration.

Downloads

316

Readme

@logarys/pipeline-validator

Validation helpers for Logarys pipeline runtime JSON configuration.

This package centralizes pipeline checks shared by Logarys applications:

  • JSON syntax check
  • required object checks
  • required field checks
  • parser type validation aligned with the ingestor (raw, json, regex, loki)
  • regex syntax check
  • ingestor pipeline field compatibility checks
  • normalization of parser.regex to parser.pattern

Install

npm install @logarys/pipeline-validator

Usage

import {
  parsePipelineJson,
  validatePipelineConfig,
  normalizePipelineConfig,
} from "@logarys/pipeline-validator";

const result = parsePipelineJson(`{
  "parser": {
    "type": "loki"
  },
  "defaults": {
    "source": "locafire-docker"
  },
  "publish": {
    "subject": "logs.locafire-docker.normalized"
  },
  "security": {
    "mode": "none"
  }
}`);

if (!result.valid) {
  console.error(result.errors);
} else {
  console.log(result.value);
}

Runtime config schema

A runtime config block must contain these required objects:

{
  "parser": {},
  "publish": {}
}

Required fields:

parser.type
publish.subject

Supported parser types:

raw
json
regex
loki

For regex pipelines:

parser.pattern

parser.regex is accepted for legacy configs and normalized to parser.pattern.

Optional objects:

mapping
mapping.timestamp
mapping.level
mapping.message
mapping.source
mapping.host
mapping.service
mapping.env

defaults
defaults.source
defaults.host
defaults.service
defaults.env

security
security.mode
security.token

Supported security modes:

none
header
query

Full pipeline document validation

const result = validatePipelineConfig(pipeline, {
  document: true,
  requireDocumentFields: true,
});

This also allows and checks:

id
source
enabled

Ingestor compatibility

The validator follows the ingestor pipeline conventions:

  • mapping is a top-level object, singular, not mappings
  • defaults is optional and contains only source, host, service, env
  • security is optional and contains mode and optional token
  • parser.type must be one of raw, json, regex, loki
  • the legacy misspelling lokki is not accepted

The validator rejects fields that are not part of this schema, for example:

name
mappings
parser.mappings
mapping.environment
defaults.environment
defaults.job
defaults.level

API

parsePipelineJson(json, options?)

Parses JSON and validates the resulting object.

validatePipelineConfig(value, options?)

Validates an already parsed object.

normalizePipelineConfig(config)

Normalizes legacy accepted fields, currently:

parser.regex -> parser.pattern

isValidPipelineConfig(value, options?)

Boolean shortcut.

Validation result

type ValidationResult<T = unknown> = {
  valid: boolean;
  errors: ValidationIssue[];
  warnings: ValidationIssue[];
  value?: T;
};