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

ci-intrepreter

v1.0.3

Published

A simple to use but advanced configuration storage method known as CI.

Downloads

17

Readme

CI Intrepreter

CI, (Standing for Configuration Information) is a new type of variable storage which combines JSON and YML. It easily allows for comments, and mixed variable types whilst retaining ease of use and accessibility. As well as dynamic writing of new configuration options whilst maintaining the integrity of the other options (for plugin-type systems)

How it works

By reading your configuration file it can parse your configuration options into an easy to read Config Object. Once it's parsed, you can retrieve a specific key the loader. Using parsers, you can parse values during the read process into any object you'd like! See the Parsers section for more information.

Notes

CI files must be stored in .ci files.

Examples

    const Loader = require("CI-Intrepreter").Loader;
    Loader.Load("someIdentifier", "./fileName.ci");

    /**
     * You can choose from config files other than the default one using the overload Loader.GetOption(key, config).
     */
    console.log(Loader.GetConfig("someIdentifier").GetValue("someOptionHere"));

    /**
     * You can write new values into the config dynamically using one function call. It'll prevent you from writing duplicate values.
     */
    Load.GetConfig("someIdentifier").AppendValue("someKey","someValue", ["Some", "Comments", "Here"]);

    /**
     * You can also update values present-set values dynamically
     */
    Load.GetConfig("someIdentifier").SetValue("someKey","someOtherValue");
    #--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    # Some arbitrary help information.
    #--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

    # This does things.
    someOptionHere: true

    # This also does things, but in INTEGER FORM!
    someOtherOptionHere: 1

    # And this is just some random string.
    someOtherOtherOptionHere: Yep...

Parsers

This software supports using what's called "Parsers". You can write a parser and use it to immediately parse any read values into anything object you'd like. To create a parser, you must create a class like so;

const Parser = require("CI-Intrepreter").Parser;

class MyParser extends Parser
{
    Parse(value)
    {
        return parseInt(value)+1; // Parse passed values into an int+1.
    }
}

And then you may use said parser when loading a file, using a JSON object passed to the load function, passing the parser to a key named after your desired key.

const MyParser = new (require("../MyParser"));
Loader.Load("someIdentifier", "./fileName.ci", {someOptionHere: MyParser});

After passing your parser, it will automatically parse and will be usable upon fetching a value.

Installation

You can install this software with npm i CI-Intrepreter! Installation into your code is easy as well, you only need a single line of code to be on your way.

    const Loader = require("CI-Intrepeter").Loader;

After inputting this, you can load configuration files with:

    Loader.Load("identifierHere", "filePathHere", {optional: parsers});

If you're not sure if a config is loaded, or would like to make a "modular" system. You can use CheckIfLoaded!

    Loader.CheckIsLoaded("someIdentifier");