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

codexjs

v1.0.0

Published

Human friendly configuration file format

Downloads

2

Readme

codex

Human friendly configuration file format for Node

Example

location (key)
A113 (and value are separated by a newline)

profile.username (you can add comments between parentheses)
hirschfeldnina (all values are strings or numbers)

profile.luckynumber (two or more newlines separate key-value pairs)
42 (numbers are automatically detected)



profile.org
funsociety

profile.id 
'4815162342' (but, you can explicitly make number-like stuff a string)

profile.codename
"007"

websites (multiple values make an array)
218.108.149.373
192.251.68.239
192.251.68.254
i239.bxjyb2jvda.net
conficturaindustries.com

profile.twitter (the order doesn't matter; the profile values did't have to be grouped)
https://twitter.com/1231507051321

(There are no nested representations beyond the ones above [arrays and flat objects].
Instead, we encourage the use of separate files 
[instead of using arrays of objects or objects of objects, etc].)

The above example when parsed, would generate the following object:

{ 
  location: 'A113',
  profile:{ 
    username: 'hirschfeldnina',
    luckynumber: 42,
    org: 'funsociety',
    id: '4815162342',
    codename: '007',
    twitter: 'https://twitter.com/1231507051321'
  },
  websites: [ 
    '218.108.149.373',
   '192.251.68.239',
   '192.251.68.254',
   'i239.bxjyb2jvda.net',
   'conficturaindustries.com'
  ] 
}

Installation

  • Run npm install -g codexjs to install it globally
  • Or run npm install --save codexjs to install it locally and add it to your project's package.json dev dependencies

Usage

Just require it and send the path of the codex file:

var codex = require('codexjs');

var configFromFile = codex.read('example.codex');

Or you can directly sent a string to parse:

var codex = require('codexjs');

var configString = fs.readFileSync('example.codex', {
  encoding: 'utf-8'
});

var configFromString = codex.parse(configString);