This Angular Module allows you to read and parse CSV and JSON file(s)
Collection of utilities which helps to process different kind of test results as Allure Results
Properties file reader for Node.js
Read binary packets...
Incremental parser
A epub-reader for React powered by ePubJS
A React Component for reading QR codes from the webcam
Various helper utilities for working with buffers and binary data
A generic toolkit to help with accessibility
Allure Reader API
Read an exact number of bytes from a binary (async) iterable
Maxmind DB (MMDB) Library
MSG Reader
React component that handles csv file input.
Node.js bindings for C2PA
TypeScript version of the gluestick ETL library for hotglue IPaaS platform
Dynamsoft Barcode Reader JS is a recognition SDK which enables you to embed barcode reading functionality in your web, desktop, and mobile applications. With a few lines of JavaScript code, you can develop a robust application to scan a linear barcode, QR
a strongly specified, highly compatible variant of Markdown
TypeScript definitions for properties-reader
A small EXIF image metadata reader
[](https://www.npmjs.com/package/@aws-sdk/chunked-stream-reader-node) [](http
A set of Vue.js components for detecting and decoding QR codes.
XML import/export for documents described with moddle
Asynchronous, buffered, line-by-line file/stream reader
GzipReader for reading multiple 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
Pure Ruby MaxMind DB (GeoIP2) binary file reader.
In the realm of the text file, few files have been as hard to read as MANIFEST.MF. Frankly, they suck, and we'd better be off without them. That's where we come in.
Provides a class for reading .80 files as delivered by 80legs.
Read and interpret Spektrum TLM log files.
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.
Read and interpret Jeti telemetry log files.
Read and interpret iCharger log files.
Read and interpret Eagle Tree telemetry log files.
Controlled file access using nginx's local redirects. Requires reader extension.
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.