An ini encoder/decoder for node
Parse EditorConfig-INI file contents into AST
TypeScript definitions for ini
No description provided.
Read and parse an ini file
Reads, Writes, Manages INI/Property files
Compact YAML, TOML, JSONC, JSON5 and INI parser and serializer
A simple, fast and configurable INI parser.
A clean class-based API for parsing, editing, and creating INI files.
Simple INI-parser
parsing and serialize ini files
prettier plugin for INI files
A better .ini files parser
Load config default values from ini config files and environmental variable
Stringify and write ini to a file atomically
a simple .ini parser
Node.js module for reading and writing INI and *NIX config files
require('require-ini') lets you load INI files using require syntax. For example: var config = require('./config.ini');
A simple .ini config parser that supports sections, comments, arrays, and objects.
An ini encoder/decoder for node
An ini-file parser which supports multi line, multiple levels and arrays to get a maximum of compatibility with Zend config files.
An ini encoder/decoder for node
INI file parser for INPA configuration files
JavaScript Configuration file(.ini) content parser, similar to python ConfigParser without I/O operations. Only one JavaScript file without any other dependencies. Compatible with NodeJS, TypeScript and Browsers.
A simple macro built on top of configparser to load and parse ini files. You can use this to write Rust programs which can be customized by end users easily.
Import Morrowind.ini settings into OpenMW configuration files
Implements a pretty bare-bones streaming INI parser.
Read and write INI files with funcions. Also allows direct access to INI data
A simple configuration parsing utility with no dependencies that allows you to parse INI and ini-style syntax. You can use this to write Rust programs which can be customized by end users easily.
This tool was developed as a part of the Rust course at National University of "Kyiv-Mohyla Academy".
A lossless, format-preserving INI parser built on rowan — parse, inspect, and edit INI files without losing comments, whitespace, or ordering
Format-preserving INI parser — read, modify and write back INI files without losing comments, ordering or formatting
A serde-based INI file parser for Rust
An Ini configuration file parsing library in Rust
An Ini configuration file parsing library in Rust
Light library to read/write ini files
Ah yes, INI files. We love them. We hate them. We cannot escape them. Originally made popular by Windows, INI files are everywhere including in Samba and Trac. This gem has one goal: make INI file, structure, and stream manipulation as fast, safe, and simple as possible. We take a modal approach with a pluggable parser class.
Parse and generate INI configuration files with sections, inline comments, multiline values, escape sequences, quoted values, and automatic type coercion for booleans and numbers.
The INI file format is an informal standard for configuration files for some platforms or software. INI files are simple text files with a basic structure composed of 'sections' and 'properties'.' - Wikipedia
.ini file DSL and generator
Read, write, modify ini fils seamlessly.
Although made popular by Windows, INI files can be used on any system thanks to their flexibility. They allow a program to store configuration data, which can then be easily parsed and changed. Two notable systems that use the INI format are Samba and Trac. More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file). ### Properties The basic element contained in an INI file is the property. Every property has a name and a value, delimited by an equals sign *=*. The name appears to the left of the equals sign and the value to the right. name=value ### Sections Section declarations start with *[* and end with *]* as in `[section1]` and `[section2]` shown in the example below. The section declaration marks the beginning of a section. All properties after the section declaration will be associated with that section. ### Comments All lines beginning with a semicolon *;* or a number sign *#* are considered to be comments. Comment lines are ignored when parsing INI files. ### Example File Format A typical INI file might look like this: [section1] ; some comment on section1 var1 = foo var2 = doodle var3 = multiline values \ are also possible [section2] # another comment var1 = baz var2 = shoodle
A pure Ruby library for parsing INI documents. Preserves the structure of the original document, including whitespace and comments
Parses ansible ini files
Simple ruby ini reader
Although made popular by Windows, INI files can be used on any system thanks to their flexibility. They allow a program to store configuration data, which can then be easily parsed and changed. Two notable systems that use the INI format are Samba and Trac. More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file). ### Properties The basic element contained in an INI file is the property. Every property has a name and a value, delimited by an equals sign *=*. The name appears to the left of the equals sign and the value to the right. name=value ### Sections Section declarations start with *[* and end with *]* as in `[section1]` and `[section2]` shown in the example below. The section declaration marks the beginning of a section. All properties after the section declaration will be associated with that section. ### Comments All lines beginning with a semicolon *;* or a number sign *#* are considered to be comments. Comment lines are ignored when parsing INI files. ### Example File Format A typical INI file might look like this: [section1] ; some comment on section1 var1 = foo var2 = doodle var3 = multiline values \ are also possible [section2] # another comment var1 = baz var2 = shoodle
Fini is an ini-parser optimized for performance.
Parser / writer for INI files
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.