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

@nxn/config

v1.0.41

Published

config loader in json or yaml format

Downloads

17

Readme

nxn-config

loads config files in json or yaml format, and search them in a path list. Supports : variables, external file inclusion, and path list search.

Config files are searched using a path list, usually :

  • environment directory : where variables and keys are stores, by environment, within client data directory
  • client data : where configuration files are stored by client (for multi tenant applications), and also data stored on disk,
  • root directory : where the index.js main file is stored.

Configuration files can be organised as structured data, or as key:value pairs.

Config format @nxn/config supports :

  • JSON format,
  • YAML format.

Variables: Variables can be defined in the config file itsef : ex. $variables: var1 :xxx var2: true var3: a: true b: AAA

or loaded from another file $variables: $ref(.env_variables)

and used in the config: ex.

$variables: $ref(.env_variables)

app1: path: ${var1} active: ${var3.c}

Pipe filters : variables can be modified with "filters", to format them: for example : ${name|id} transforms name variable into an id, replacing accents, blanks, etc.

Filters can be piped : ${name|id|base64} : transforms name into an id and then format it in base 64.

supported filters: id : base64 : base 64, decode64 : decode Base 64, md5: md5 hash dateString: transform a date object into a string, timestamp: date to unix time date: transform to date format now: current date url_encode: URL encode trim: remove trailing blanks lower: lower case upper: upper case no_accents : remove accents in strings env: get a env variable argv: get main argv param, if variable is an integer

Includes: another file can be referenced and loaded in the config file. ex.

myServices: $ref(app/services)

nb. a YAML file can include another YAML file or a JSON. Each file is loaded and evaluated before inserting its values in another file. As such, an included file can define its own variables or include other files. An included file can use variables that are replaced by its own variables, completed by its "parent" file variables.