A Lightweight Data Interchange Language for Encoding String Trees
A function to parse floating point hexadecimal strings as defined by the WebAssembly specification
CSS Object Model implementation and CSS parser
Error-tolerant ECMAScript parser
Validates XML name productions — Name, NCName, QName, NMToken, NMTokens — for XML 1.0 and 1.1
CSS Object Model implementation and CSS parser
HTML to React parser.
CSS Object Model implementation and CSS parser
A tool set for CSS: fast detailed parser (CSS → AST), walker (AST traversal), generator (AST → CSS) and lexer (validation and matching) based on specs and browser implementations
A JavaScript parser
Dependency-free RFC 3986 URI toolbox
A utility package to parse strings
the mighty option parser used by yargs
[](https://travis-ci.org/mulesoft-labs/yaml-ast-parser)
Node.js body parsing middleware
Parse binary files with a schema into nicely readable objects
Option parsing for Node, supporting types, shorthands, etc. Used by npm.
Low footprint ECMAScript source code parser
Support for `import <defer|source>` phase syntax in Acorn
An ESLint custom parser which leverages TypeScript ESTree
> Selector parser with built in methods for working with selector strings.
Range header field string parser
An RFC 3986/3987 compliant, scheme extendable URI/IRI parsing/validating/resolving library for JavaScript.
No description provided.
multipart-parser is a simple parser for multipart MIME messages, written in Ruby, based on felixge/node-formidable's parser. Some things to note: - Pure Ruby - Event-driven API - Only supports one level of multipart parsing. Invoke another parser if you need to handle nested messages. - Does not perform I/O. - Does not depend on any other library.
Optimist is a commandline option parser for Ruby that just gets out of your way. One line of code per option is all you need to write. For that, you get a nice automatically-generated help page, robust option parsing, command subcompletion, and sensible defaults for everything you don't specify.
Meta parser that allows you to define new parser with ruby DSL to match access log file format you are willing to parse or use one of the predefined parsers like Apache common, IIS and more
Mulparse is a multilingual parser for multiple coding languages this parser is easily extensible so one may define his own language and easily parse it.
A slim command-line parser that does one thing well: turn an array of arguments into a hash of recognized options and their arguments.
Your Dynamic Parser may be a composite of both `Stateless` and `Stateful` parsers. To build a composite/dynamic paser, first you need one or more `MicroParsers`. Check https://github.com/ContaBoa/dynamic_parser for more details.
You've seen Getopt::Long, OptionParser, Thor? What the world needs now is one more command-line parser. This serves as a backend command line parser that passes the option-parsing portion of it off to OptionParser, Trollop, or any other option-parser that has an adapter[^adapter]. But the parts it *does* do are really exciting: It features arbitrarily deeply nested subcommands, optionally colorized help screens with smart formatting, automatically generated usage syntaxes, manpage generation[^maybe2], lazy-loading of subcommands, and (get this:) you can turn your command line app into a web app. (is processing a form then displaying a record really that different from CLI that does the same?)[^maybe3]
This library provides a DSL which you can use to easily generate parsers in Ruby. At it's core, it's a parser combinator library, but you don't need to worry about that. You build more complex expression based on simple ones, and match any formal language you want. Originally by Federico Ramirez (https://github.com/gosukiwi)
The LL(k) Interpreted Parser (llip) is an automated tool to easily create an LL(k) parser and the related scanner without the need of generating anything. Everything is done on the fly through a simple DSL. == A Little comparrison against other tools Tools like JavaCC, ANTLR, Coco/R and others use an external description file which they compile into the destination code. This file it's usually written using a complex product related language. Using Ruby metaprogramming, a parser generator can go one step further. In fact, the llip gem gives you the possibility to write a parser writing only Ruby code.
This gem removes common margin from indented strings, such as the ones produced by indented heredocs. In other words, it strips out leading whitespace chars at the beggining of each line, but only as much as the line with the smallest margin. It is acknowledged that many strings defined by heredocs are just code and fact is that most parsers are insensitive to indentation. If, however, the strings are to be used otherwise, be it for printing or testing, the extra indentation will probably be an issue and hence this gem.
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.
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.