Read a glob of files, dynamically choosing the reader or requiring the files based on the file extension.
Properties file reader for Node.js
PX4 ULog file reader
Promise File Reader
File-Reader for the Doctrine JSDoc Parser
Gedcom file reader
TypeScript definitions for react-file-reader-input
A gyp file reader / processor
Pull streams implementation of a file reader
W3C File Reader API streaming interfaces
A pure javascript HDF5 file reader, based on pyfive
Asynchronous line-by-line reverse file reader
PX4 ULog file reader
File reader for IPG Automotive .erg result files
ctx-core file-reader
file reader and sender apis
SIE file reader
RGBE(.hdr) file reader/writer.
File reader and writer for IPG Automotive infofiles
Flow Cytometry Standard (FCS) file reader
SIE file reader/writer
Lightweight Node.js BWF and WAV file reader
mdict (*.mdx, *.mdd) file reader
javascript clientside file reader
Sample Project
Console (or text file) input assistant
JavaScript/TypeScript execution runtime for pctx
Library of helper functions and structures for iterating over text files
A simple Rust crate to read config.json from executable directory
functions for reading environment variables from a file
Generic reader for scattering event files
Library for parse perf.data file from Linux perf tool
A rustls certificate chain and private key file reader.
A Rust library for reading and parsing SDR (Software Defined Radio) files into complex samples. Supports various sample formats including u8, i8, i16, u16, f32, and f64.
Implement Read+Seek for web_sys::File
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
furnace-swf allows one to load, modify and write back Flash SWF files. It can be used with furnace-avm2 in order to achieve impressive results.
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.
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.