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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@rainbow-o23/n4

v1.0.56

Published

o23 pipeline parser

Downloads

966

Readme

Static Badge

Module Formats

o23/n4

o23/n4 provides the ability to read pipeline and pipeline step configurations, currently supporting the YAML format. While reading the configuration, o23/n4 simplifies the notation of certain properties and also adds some related validation and script parsing supplements, as follows:

  • For single-line snippet, a prefix return will be automatically added to ensure that data can be returned,
  • Automatic conversion between camel case and kebab case property names,
  • If a property value starts with env:, it will be automatically replaced with the corresponding environment variable value,
  • The prefix env: supports multiple environment variables, separated by commas, with the first one having a value taking precedence.

When writing YAML configurations, the following syntax rules should also be noted:

  • null string value will be recognized as a null value. If you need to return a null value, you can write it as "null" or return null,

  • Property values that conform to JSON syntax will be automatically parsed. Therefore, if a value needs to be treated as a snippet, it should be enclosed in double quotation marks (""). For example, {name: $factor.name} can be written as "{name: $factor.name}",

  • Sometimes, we don't want the return prefix to be automatically added before a single-line snippet. In this case, we can use the vertical line | syntax to avoid this problem. For example, consider this:

    snippet: $factor.enabled = true

    If it is written in this way, the return value is true. We can instead write it as following:

    snippet: |
      $factor.enabled = true

You can find all relevant YAML configuration examples in the server/02-api-test folder of o23/n99. Since the property names are self-explanatory, we will not explain the purpose of each property in the following section. You can refer to the documentation of o23/n3 for this part.