Pointfree forking `Futures`
This fork adds synchronous APIs and session extensions needed for LiveStore's real-time collaborative database features. **This fork is intended for LiveStore use only** - external users should use [upstream wa-sqlite](https://github.com/rhashimoto/wa-sql
Runs typescript type checker and linter on separate process.
Shiki's fork of `vscode-textmate`
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
rawStream.pipe(JSONStream.parse()).pipe(streamOfObjects)
A Node.js BLE (Bluetooth Low Energy) central library.
Validate JSON
A PDF generation library for Node.js
Client-side Bitcoin-like JavaScript library
An advanced font engine for Node and the browser
The official JavaScript client for the Phoenix web framework.
No description provided.
Thin wrapper around zen-observable and @types/zen-observable, to support ESM exports as well as CommonJS exports
A hook that can combine two refs(mutable or callbackRefs) into a single callbackRef
Declaratively encode and decode binary data
An implementation of the Unicode Line Breaking Algorithm (UAX #14)
Bun is a fast all-in-one JavaScript runtime.
Check whether a browser event matches a hotkey.
Maybe the best beautiful HTML5 responsive player component for react
fork of fast-memoize and support esm
msgpack encoder and decoder in pure javascript based on creationix/msgpack-js updated to match the new v5 specification with string support.
A Spelling Checker for Code!
Fork of pretty-format with support for ESM
Represents forks (child processes) as objects and makes interaction with forks easy. It provides a simple interface to create forked futures, get the return value of the fork, get an exception raised in the fork, and to send objects between parent and forked process.
An experimental fork of Authlogic that aims to work with Rails 3 and MongoMapper (and other DBS in the future I hope).
Forking from bhuga/promising-future on github, so Version is started from 0.3.1
Forked from meh/ruby-thread. Fixes thread limit exception. Includes a thread pool, message passing capabilities, a recursive mutex, promise, future and delay.
SimpleFuture is class that simplifies coarse-grained concurrency using processes instead of threads. Each instance represents the future result of a block that is passed to it. The block is evaluated in a forked child process and its result is returned to the SimpleFuture object. This only works on Ruby implementations that provide Process.fork().
SlimGems is a drop-in replacement for RubyGems, a package management framework for Ruby. This project was forked at 1.3.7, which was a great stable release. SlimGems focuses on maintaining a sane and stable API. We believe that the project has been put through enough stress testing by the community to lock into the current API functionality for the forseeable future. We will also continue to improve the runtime performance over time; we can do this without changing the API.
What is send? ============= It’s a tiny wee ruby gem that is a fork of [Object#try](http://ozmm.org/posts/try.html) and [Object#try from Rails](http://api.rubyonrails.org/classes/Object.html#M000027). It will *never* throw a NoMethodError (no matter the receiver), and returns nil if called on a nil-class or if the method in the receiver does not exist. Note on Patches/Pull Requests ----------------------------- 1. [Fork me!](http://github.com/Burgestrand/send-/fork) 2. Write tests for your new feature or bug fix (important, I don’t want to break your stuff in a future update by accident!) 3. Hack away on the code; make your tests pass. 4. Commit! Don’t touch Rakefile, version or git history in any of the commits you want me to pick. 5. ??? 6. Send me a pull request!
The start_project gem is a simple way of downloading the latest version of your favourite framework. It's very easy to use: simply install the gem as normal with gem install start_project and then run the command line tool ProjectStart --type {framework} --name {name of project} and it will pull the latest version of the framework and extract it to your machine with the name you provided. Currently, there are 5 frameworks: html 5 boilerplate, bootstrap, 960 grid, 320 and up, and mass gs960 andup320 mass, but I'll be adding more in the future. You can fork the source on github here: https://github.com/aonghusflynn/ProjectStart You can find my blog here: http://www.aonghusflynn.com
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
= Ungulate According to Wikipedia, this can mean "hoofed animal". Camels have hooves. This is a gem for uploading and processing images using an Amazon Web Services stack. It comes with a few goodies: * ungulate_server.rb - simple queue runner that expects a YAML-encoded job description for RMagick * Ungulate::FileUpload - a model for e.g. Rails that does some cryptography stuff - example to follow * A view helper for Rails: "ungulate_upload_form_for" == Installation gem install ungulate == Documentation http://wiki.github.com/camelpunch/ungulate/ == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2011 Camel Punch Limited. See LICENSE for details.
= wahlrecht_de Provides summary analysis of current poll results from wahlrecht.de == Contributing to wahlrecht_de * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet. * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it. * Fork the project. * Start a feature/bugfix branch. * Commit and push until you are happy with your contribution. * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it. == Copyright Copyright (c) 2013 Tobi Fankhänel. See LICENSE.txt for further details.
= rails_vcstatus_logger It adds current state of version control to the log when you start the server. * Currently only supports git Adds current version hash and result of `git diff` The idea is that you can be sure about what source was running when you look in the log. I recently had a situation where i wasn't sure when a change was put up on the live server. Please add support for your vc system and send me a pull request! Just add this to enivorment.rb config.gem 'bjornblomqvist-rails_vcstatus_logger', :lib => 'rails_vcstatus_logger', :source => 'http://gems.github.com' == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2009 Bjorn Blomqvist. See LICENSE for details.
No description provided.
No description provided.
No description provided.