Parse code comments from JavaScript or any language that uses the same format.
Parse and stringify JSON with comments. It will retain comments even after saved!
Fast and easy parser of statements in source code in any language ✂️
Strip comments from JSON. Lets you use comments in your JSON files!
Jest runner for API documentation generation from code comments, supports TypeScript. Very stable and reliable, based on `parse-comments` package
JavaScript parser and stringifier for YAML
Parses and serializes `.po` file content.
CSV parsing implementing the Node.js `stream.Transform` API
Fast and easy parser for declarations of import and export in ECMAScript/TypeScript
Parse incomplete json text in best-effort manner
JSDoc parser
TOML parser for Node.js (TOML v1.1.0 compliant)
Scanner and parser for JSON with comments.
Generic JSDoc-like comment parser
parse comments in an AGS Script Header file and turn into docs
JavaScript parser written in OCaml. Produces ESTree AST
Remark plugin to support comments
No description provided.
Parses well-formed HTML (meaning all tags closed) into an AST and back. quickly.
Require .json files with comments
Open Source Composition library for Apollo Federation
Official Node.js client library for the Postmark HTTP API - https://www.postmarkapp.com
Find and parse the tsconfig.json file from a directory path
Discard comments in your CSS files with PostCSS.
A tool to help import variables from .env files into Bitwarden Secrets Manager.
An async gcode parser for no_std targets.
Parse HTML conditional comments
A pure Ruby library for parsing INI documents. Preserves the structure of the original document, including whitespace and comments
Parse a front matter from syntactically correct strings or files
A Treetop parser for alias files
Brings comment-aware YAML parsing to Psych
EmailReplyParser is a small library to parse plain text email content. This is what GitHub uses to display comments that were created from email replies.
TomParse provides no other functionality than to take a code comment and parse it in to a convenient object-oriented structure in accordance with TomDoc standard.
Receive, parse and manage GitHub webhook events for issues, PRs and issue's comments
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
Parses DSS comments from css files
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]'
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.