parses Markdown syntax and converts it into HTML
JSON.parse with context information on error
Transforms jsdoc data into something more suitable for use as template input
Parser for Github, GitLab and Bitbucket issues actions, references and mentions
Parse and stringify URL query strings
micromark utility to decode markdown strings
Parse HTML character references
This package contains helpers and nodes for wrapping content in marks for Lexical.
Small footprint URL parser that works seamlessly across Node.js and browser environments
<mark> tag for markdown-it markdown parser.
JSON.parse with context information on error
utility library for parsing asn1 files for use with browserify-sign.
Node.js path.parse() ponyfill
JavaScript parser and stringifier for YAML
Parse HTTP Content-Type header according to RFC 7231
mdast extension to parse and serialize highlight mark
hast utility to create an element from a simple CSS selector
JSON.parse and stringify with better errors that respects formatting
CSV parsing implementing the Node.js `stream.Transform` API
quote and parse shell commands
Parse the Forwarded header (RFC 7239) into an array of objects
Parse JSON with more helpful errors
micromark extension to support highlight mark
An Esprima-compatible JavaScript parser built on Acorn
Core parsing engine for the FineMark markup language
Namumark
A Netspace bookmark parser for Rust
Executable tools pakcaged as a ruby gem that will parse RSPEC results files in XML and mark results in TestRails.
Parse a front matter from syntactically correct strings or files
A markup extension for the PDF::Reader library
qutebrowser_url_mark is a library for parsing and serializing qutebrowser's URL marks (quickmarks or bookmarks).
This gem parses the `.loi` file format and allows to check if a given National Insurance Number card serial number is marked as 'in opposition', or to extract all the serial numbers in opposition.
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
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.