A readable file stream for files that are growing.
Read a growing file continuously as a Stream.
graph data structure
Configuration control for production node deployments
React components for managing files and images
The modern, community-first TypeScript toolkit with all of the fast, readable, and minimal utility functions you need. Type-safe, dependency-free, tree-shakeable, fully tested.
Like an array, but rounder.
wait-on is a cross platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become available
OpenTelemetry Node SDK provides automatic telemetry (tracing, metrics, etc) for Node.js applications
useful add-ons for react-three-fiber
AWS SDK for JavaScript Efs Client for Node.js, Browser and React Native
XMLHttpRequest emulation for node.js
A/B Smartly - React SDK
Use an `<sp-asset>` element to visually represent a file, folder or image in your application. File and folder representations will center themselves horizontally and vertically in the space provided to the element. Images will be contained to the element
OpenTelemetry Web Tracer
Generate valid JSON data from JSON Schema definitions
A fast fifo implementation similar to the one powering nextTick in Node.js core
A syslog transport for winston
Library to help write libraries that accept both promises and callbacks.
A growing collection of utilities to make working with Promises easier and cleaner.
Stencil Component Starter
Spritesheet generator
Internationalization (i18n) support for vue-formulate
Functional CSS for humans
Currently the only way to access Tropo logs is to download a text file from the Tropo FTP site. This requires constant redownloads of files that can grow to very large sizes. Tropo tail allows you to live tail your logs with log rollovers when Tropo creates a new log file, for a better development experience.
Chomsky generates parsing expression grammars with a nice pure-Ruby DSL, eliminating the need for secondary grammar definition files or out-of-band compilation, and allowing a grammar's rules to grow dynamically or be manipulated as easy-to-understand Ruby objects.
When i use rspec to do a lot of test, each time database is inserted data and truncate table, when tables grows the speed grow down too much. At first i convert the db engine from innodb to memory in db/seed.rb file. After that i write this gem to do the job for more app. Notice: Tables those contain text col can not convert to memory engine, so i convert those colums to string first. So if there are test case use too long string to insert, there would be trouble.
This plugin enables the use of a custom Liquid tag {% aspectratio filepath %}, to find the aspect ratio of an image or video file. This can be used for e.g. specifying the flex-grow value of an item to display items of different aspect ratios on one line at the same height, or to separate out horizontal or vertical videos (aspect ratio > or < than 1).
Belletrist is a collection of Ruby DSLs for generation of different data file types. Currently, HTML and JSON are supported but that will grow as my needs do, or if other people want or contribute any other DSLs. It is important to note that Belletrist has a focus on performance, not correctness. Belletrist ascribes to the rule of "what goes in, must come out", and as such Belletrist DSLs must output well-formed documents so long as the developer provides Belletrist valid input. If that contract is broken the result is undefined.
Twitterize is a quick and dirty hack I did in a few hours to play with the Twitter API (seriously, there are no tests and I'm sure there is code crude enough in there to make you recant any friendship we might have). It allows you to take any number of RSS feeds and post them to one or more Twitter accounts. An example of this is how various RSS feeds from the New York Times are sent to twitter accounts nytimes, nyt_arts, nyt_biz, etc. This is accomplished via a command-line script that requires a separate configuration file (see below). Since Twitter is a rapidly growing (read somewhat flaky) service, twitterize also uses a database to store twitters to be posted and recover later if twitter is down. This also allows the app to retain feed GUIDs and avoid duplicate posts.
# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request