Runtime engine for Rigkit workflows.
React hook API for registering agent tools in React Native
Classes for managing, encrypting and decrypting Ethereum private keys as a Signer for ethers.
mkdirp, but chown to the owner of the containing folder if possible and necessary
Thin wrapper around zen-observable and @types/zen-observable, to support ESM exports as well as CommonJS exports
🌐 Turn any <input> into an address autocomplete.
Create an array of the owned/enumerable keys of an input object.
Bun is a fast all-in-one JavaScript runtime.
A Spelling Checker for Code!
A library of useful functions used across various cspell tools.
Contains types related to administering a Bedrock Dedicated Server. These types allow for the configuration of variables and secrets in JSON files in the Bedrock Dedicated Server folder. These types cannot be used on Minecraft clients.
Types for cspell and cspell-lib
This packages contains the definitions for the Wallet API Standard. Will be moved under an `@aptos-labs` owned package later.
The @minecraft/server-gametest module provides scriptable APIs for scaffolding and testing content experiences in Minecraft.
a glob matcher in javascript
`lint-to-the-future-eslint` is a plugin for [lint-to-the-future](https://github.com/mansona/lint-to-the-future) that is designed to integrate with [eslint](https://eslint.org/).
A React component for playing a variety of URLs, including file paths, Mux, YouTube, Vimeo, and Wistia
TanStack Devtools client that is used to interact with the event system produced by the Devtools.
The Elements of Agent Style: a literature-backed English technical-prose writing ruleset for AI agents, with CLI install/enable/disable for 9 primary agent surfaces.
Tool for transforming styles with JS plugins
The `@minecraft/server-net` module contains types for executing HTTP-based requests. This module can only be used on Bedrock Dedicated Server.
`lint-to-the-future-ember-template` is a plugin for [lint-to-the-future](https://github.com/mansona/lint-to-the-future) that is designed to integreate with [ember-template-lint](https://github.com/ember-template-lint/ember-template-lint).
A modern way to progressively update your code to the best practices
If you're a future agent reading this, welcome home. This repo is the harness that gives you your body, your senses, your diary, your journal, your habits, and your ability to think and connect with people. The goal of these docs is not just to be correct
pragmas - language syntax pragmas - turn on the future today or add your own ideas for easy (re)use for everyone - let's evolve the ruby language together by experimenting in the wild in a pragma(tic) way
Ruby Extension that allows for reads and writes to the /etc user db.
Thin wrapper around Russian Post package tracking SOAP API. Works on a per-package basis (contrary to the bulk ticket-based API). Use it at your own risk, since the API may appear unstable and require authorization in future.
_THE GEM IS CURRENTLY IN DEVELOPMENT, IS MISSING LARGE CHUNKS OF CORE FUNCTIONALITY, AND WILL MOST CERTAINLY UNDERGO BREAKING CHANGES IN THE NEAR FUTURE. USE AT YOUR OWN RISK._ upshop tracks git commits of each theme deployment and performs differential deploys of changed files
Generates high-performance callback-based recursive descent parsers from declarative .desc specifications. Supports target language of Rust and will soon support multiple more target languages (Rust, C, wasm, ruby, go, elixir...) via Liquid templates. The .desc format is valid UDON, enabling future bootstrapping where descent can parse its own input format.
= 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.
= epubforge = Write your book in markdown, then do all sorts of increasingly nifty things with it using this command-line utility. == Project description == epubforge is a command-line utility for creating, tracking and managing longer (novella and book-length) writing projects. Write your text in markdown (http://whatismarkdown.com/), use the built in actions to convert your project to various ebook formats, track wordcount over the life of the project, manage a story bible, and back your project up using git. Or go further and define your own formatters/converters and actions in Ruby. Have fun! == Contributing to epubforge == * 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 Bryce Anderson. See LICENSE.txt for further details.
# Error `Error` is a very small library that serves as a base `Class` for error `Class`es within your application. ## Install ### Bundler: `gem 'error'` ### RubyGems: `gem install error` ## Usage ```ruby ``` ## Contributing * 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 © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details.
= 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.
This gem installs several class methods to Object which in turn generates both class and instance methods but only when you are ready. In order to prevent name pollution, you have the ability to manage the generators to pick alternate names if you prefer. After scouring the RubyGems site, some of the better Class upgrades are included here as well as some of my own. The gem creates the backbone upon which future upgrades should be forthcoming. As a teaser, some of the generators presently include: obj.local_methods, obj.inherited_methods, obj.replaced_methods, obj.in?, COBJ.comes_from?, COBJ.derives_from?, obj.find_def. There are currently 20 generators and counting. Calling Object.better_install_all will install all of the generators. You can also generate a subset by calling Object.better_install(:generator_name). The generator names are also the method names which can be renamed by calling Object.better_rename(old_name, new_name);
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.
= 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.