INI parser and serializer for JavaScript.
AWS credential provider that sources credentials from ~/.aws/credentials and ~/.aws/config
An ini encoder/decoder for node
Parse EditorConfig-INI file contents into AST
Compact YAML, TOML, JSONC, JSON5 and INI parser and serializer
Read and parse an ini file
Small, efficient encoding of SVG data URIs for CSS, HTML, etc.
TypeScript definitions for ini
A clean class-based API for parsing, editing, and creating INI files.
Configuration management for the npm cli
Get the set npm registry URL
prettier plugin for INI 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.
parsing and serialize ini files
Stringify and write ini to a file atomically
A simple, fast and configurable INI parser.
Simple INI-parser
An ini-file parser which supports multi line, multiple levels and arrays to get a maximum of compatibility with Zend config files.
a simple .ini parser
Expand environment variables using dotenv
Properties file reader for Node.js
Loads environment variables from .env file
Reads, Writes, Manages INI/Property files
Read/Write config couldn't be easier!
iniparser - read / parse INI configuration, settings and data files into a hash (incl. named subsections)
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
Simplistic parsing of INI style files. Data within sections can be handled as raw lines or as an array split on spaces.
Gem ini berfungsi untuk automatisasi dalam mengambil informasi saldo dan mutasi rekening Bank BCA anda secara mudah, cepat, dan efisien. Dengan menggunakan command line anda dapat dengan mudah melakukan automatisasi untuk pengambilan data berupa informasi saldo, mutasi transaksi harian, mutasi transaksi bulanan. Data kemudia dapat ditampilkan maupun disimpan ke dalam bentuk CSV maupun Excel. Gem ini tidak mengambil data anda sama sekali, karena gem ini pada dasarnya bekerja dengan melakukan automatisasi pada browser anda untuk melakukan hal-hal yang biasa anda lakukan dengan mengklik pada browser untuk melakukan transaksi. Dibutuhkan browser Firefox terinstall pada sistem anda untuk menggunakan gem ini.
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
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.