@jedmao/ini-parser



A highly forgiving and configurable INI parser for the informal INI file format.

Introduction

The INI file format is informal. Different parsers behave differently, in that they support different features. This parser aims to be a bit more flexible and configurable to suite your needs, whatever they may be. Also, it assumes INI files out there in the wild could have some pretty crazy things in them. This parser does its best to understand whatever crazy you throw at it.

No dependencies on Node.js here, so you should be able to use it in the browser.

Usage

``ini
; example.ini

a=b

[c]
d:e

[c]
f=g
`

`ts
import { readFileSync } from "fs";
import Parser from "@jedmao/ini-parser";

const { configure, parse } = new Parser(/ config /);

parse(fs.readFileSync("./example.ini"));
`

See Parser#parse API.

$3

`json
[
{
"a": "b"
},
[
[
"c",
{
"d": "e"
}
],
[
"c",
{
"f": "g"
}
]
]
]
`

API

`ts
import Parser from "@jedmao/ini-parser";
`

$3

Class constructor. Accepts ParseOptions for initial configuration.

$3

Sets configuration options, preserving existing configuration and overriding only the new keys you provide.

$3

Resets configuration to default settings as if you created a new Parser().

$3

Parses INI file contents as a string. The result will be an array:

- Index 0 will have any/all root properties.
- Index 1 will have an array of any/all sections that follow.

_Note: repeated sections will also be repeated in the array._

See Usage for an example.

$3

`ts
interface ParseOptions {
/**
* Indicates accepted comment chars. Only works if you specify single-char
* comment values in RegExp form. A setting of false turns off comments
* completely, treating comment chars as normal string values.
* @default {RegExp} /[#;]/
*/
comment?: RegExp | false;
/**
* Accepts comment chars in a property key or value. If a space
* follows the comment char, it is considered an actual comment.
* Example: "#k;=#v; #z" -> { "#k;": "#v;" }
* @default {false} false
*/
isCommentCharInProp?: boolean;
/**
* Indicates accepted delimiter chars. Only works if you specify
* single-char delimiter values in RegExp form.
* @default {RegExp} /[=:]/
*/
delimiter?: RegExp;
/**
* Indicates accepted newline sequences in the form of a RegExp.
* @default {RegExp} /\r?\n/
*/
newline?: RegExp;
/**
* By default, attempts to parse property values with JSON.parse.
* If unsuccessful, returns property value as a string. You may also
* provide your own resolve function here for custom property value
* resolution.
* @default {true} true
*/
resolve?: boolean | ResolveCallback;
}
`

$3

`ts
interface ResolveCallback {
(value: string, key?: string, fallback?: typeof parseValue): any;
}
`

$3

Attempts to parse a string value with JSON.parse. If unsuccessful, returns input string untouched.

Testing

Run the following command:

`
$ npm test
`

This will build scripts, run tests and generate a code coverage report. Anything less than 100% coverage will throw an error.

$3

For much faster development cycles, run the following commands in 2 separate processes:

`
npm run build:watch
`

Compiles TypeScript source into the ./dist folder and watches for changes.

`
$ npm run watch
`

Runs the tests in the ./dist` folder and watches for changes.