Instruments a Node program and updates its comments with computed expression values
PostCSS plugin to replace overflow-wrap with word-wrap or optionally retain both declarations.
PostCSS plugin for CSS Modules to pass arbitrary values between your module files
PostCSS plugin postcss-page-break to fallback `break-` properties with `page-break-` alias
Support for representing 64-bit integers in JavaScript
Generic JSDoc-like comment parser
Are these two JavaScript values equal?
Like lodash isEqualWith but for shallow equal.
CSS box-shadow parser and stringifier
a set of utilities to work with JSON / JSON5 documents
A very simple and stupid parser, based on a statemachine and regular expressions.
A topologically ordered map of key/value pairs with a simple API for adding constraints.
A list of all CSS color keywords.
Returns true if a number or string value is a finite number. Useful for regex matches, parsing, user input, etc.
This is a simple parser for tagged comments.
Search CSS(-like) strings
A minimalistic code generation utility.
A thing that is a lot like ES6 `Map`, but without iterators, for use in environments where `for..of` syntax and `Map` are not available.
Light ECMAScript (JavaScript) Value Notation - human written, concise, typed, flexible
PostCSS plugin for fallback image-set
Polyfill for the proposed React context API
mdast utility to parse a comment marker
Reads and interpolates Java .properties files
An ini encoder/decoder for node
csv11 - read / parse comma-separated values (csv); supports csv 1.1 incl. comments, named values, multi-line records, and more
Parse and generate INI configuration files with sections, inline comments, multiline values, escape sequences, quoted values, and automatic type coercion for booleans and numbers.
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
In ruby we use `# =>` as a comment marker that mean the immediately adjacent expression's expected value. There are gems like xmpfilter / seening_is_believing, which are to generate such comments. They are very useful. But so far we lack feature that does vice-versa; to check if the comment is actually the output of the expression. This is the library that does it.
Krakken is able to parse files into a hash, and write a hash to a file. It supports comments started with '#' when parsing, and outputs in the format of '[key]=[value]'
Krakken is able to parse files into a hash, and write a hash to a file. It supports comments started with '#' when parsing, and outputs in the format of '[key]=[value]'
This module provides utilities for working with various kinds of structured text. It includes comment handling and comma-separated-value (CSV) parsing with support for quoted strings.
Addon for IRB to log command run and their returns to a file. Return values are comments so the diary is valid Ruby. Just cut and paste into another session.
Parse Excel spreadsheets with a simple API. Read cell values, formulas, styles, comments, data validations, named ranges, and merged cells from xlsx and xlsm files. Supports streaming from strings and IO objects with lazy row loading for large files.
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
BibTeX-Ruby is the Rubyist's swiss-army-knife for all things BibTeX. It includes a parser for all common BibTeX objects (@string, @preamble, @comment and regular entries) and a sophisticated name parser that tokenizes correctly formatted names; BibTeX-Ruby recognizes BibTeX string replacements, joins values containing multiple strings or variables, supports cross-references, and decodes common LaTeX formatting instructions to unicode; if you are in a hurry, it also allows for easy export/conversion to formats such as YAML, JSON, CSL, and XML (BibTeXML).
Create and manage configuration files in Ruby for Ruby. Jeckyl can be used to create a parameters hash from a simple config file written in Ruby, having run whatever checks you want on the file to ensure the values passed in are valid. All you need to do is define a class inheriting from Jeckyl, methods for each parameter, its default, whatever checking rules are appropriate and even a comment for generating templates etc. This is then used to parse a Ruby config file and create the parameters hash. Jeckyl comes complete with a utility to check a config file against a given class and to generate a default file for you to tailor. Type 'jeckyl readme' for more information.
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.