``` npm install --save easy-down ```
Micro-generator framework that makes it easy for an entire team to create files with a level of uniformity
A Quick description of the component
Basic IP rate-limiting middleware for Express that slows down responses rather than blocking the user.
CLI Simple, Stupid. Automatic discovery of parameters names. Provides an easy and minimal setup by passing in only a function reference without the need of declaring all expected options names or create a help section by hand. Support to sync / async. Sup
An easy way to set and cache context changes for Apollo Link
PostgeSQL migration tool
SuperAgent driven library for testing HTTP servers
Essential JS 2 DropDown Components
A small JS+SVG library for drawing railroad syntax diagrams.
The node-pty package, stripped down only for linux-x64.
Slow down your Cypress tests
Collision-resistant ids optimized for horizontal scaling and performance. For node and browsers.
A React component to crop images/videos with easy interactions
Select a one- or two-dimensional region using the mouse or touch.
A super minimal emoji rendering library for React
Simple JS stack with auto run for node and browsers
Easy to use npm NodeJS Monero Miner with C++, uses XMRIG for highspeed hashing.
A library of styleable components built using React Aria
A logging helper for Node.js
Basic IP rate-limiting middleware for Express. Use to limit repeated requests to public APIs and/or endpoints such as password reset.
A TypeScript ESLint ruleset designed for large teams and projects
Stylish, intuitive and user-friendly prompt system. Fast and lightweight enough for small projects, powerful and extensible enough for the most advanced use cases.
Parse a .gitignore or .npmignore file into an array of patterns.
Hunting down random test failures can be very very difficult, sometimes impossible, but minitest-bisect makes it easy. minitest-bisect helps you isolate and debug random test failures. If your tests only fail randomly, you can reproduce the error consistently by using `--seed <num>`, but what then? How do you figure out which combination of tests out of hundreds are responsible for the failure? You know which test is failing, but what others are causing it to fail or were helping it succeed in a different order? That's what minitest-bisect does best.
I had a lot of XML transformation to do and the requirements kept changing, so I sat down and wrote something that was easy to modify.
Sidekiq::Undertaker is a plugin for Sidekiq. It allows exploring, reviving (retrying) or burying (deleting) dead jobs. For easy exploring the dead-jobs queue is broken down into time windows (buckets) of hours, days and weeks.
I had a lot of XML transformation to do and the requirements kept changing, so I sat down and wrote something that was easy to modify.
Thumbsy provides an easy way to add thumbs up/down or like/dislike functionality to your Rails models with comments support
Groonga(Rroonga) for using easily. You can add the data in the column without specifying. You can easy to use and persistence, advanced search query, sort, grouping (drill down), snippets, and pagination. You can make an immediate search engine.
lazy_migrate lets you easily see which migrations have and have not been run, and makes it easy to up/down/migrate/rollback your migrations through a terminal UI. You can even bump migration versions in the event that you've just pulled master and somebody else merged their migration before yours.
Add some convenience macros for your POROs that cut down on boilerplate code. Method definition macros, more powerful attr_accessors, and easy associations between in-memory objects. Mocks the ActiveRecord API to make it feel comfortable and intuitive for Rails developers. The main intent of this project is to explore dynamic programming in Ruby. Maybe someone will find it useful. WIP.
A gem that provides some useful components for dry-system. The goal is to be able to easily add dependencies to your project, in a robust and easy way. The gem will take care of important best practices for you, such as: - Managing the lifecycle of a dependency (starting, shutting down, etc.) - Ensure the resources are safely wrapped (i.e. using a connection pool when neccesary) - Configuring the environment - Adding logging - And more...
Wish you could write your Ruby in XML? Has the fact that Ruby is not "enterprise" got you down? Do you feel like your Ruby code could be made to be more "scalable"? Well look no further my friend. You've found the enterprise gem. Once you install this gem, you too can make Rails scale, Ruby faster, your code more attractive, *and* have more XML in your life. I'm sure you're asking yourself, "how can the enterprise gem promise so much?". Well the answer is easy, through the magic of XML! The enterprise gem allows you to write your Ruby code in XML, therefore making your Ruby and Rails code scale. Benefits of writing your code in XML include: * It's easy to read! * It scales! * Cross platform * TRANSFORM! your code using XSLT! * Search your AST with XPath *or* CSS! The enterprise gem even comes with a handy "enterprise" binary to help you start converting your existing *legacy* Ruby code in to scaleable, easy to read XML files. Let's start getting rid of that nasty Ruby code and replacing it with XML today!
I'm tired of the complications that tools like bundler and rvm inject into my system and my workflow. I don't want 4 billion gems installed globally. I don't want to have `rake` slow down for no good reason. I don't want rvm to regress on undefined variables over and over and over (and I don't want to report it anymore when it does). I want as much simplicity as I can afford and still be able to get my job done. I've found pretty good balance using rbenv (only when needed) and by using this 45 line shell function `ohmygems` (aliased to `omg`, of course). I still have my system-level gems as my previous GEM_HOME gets moved into GEM_PATH so things like minitest and autotest are always available. But now I have private gems that are incredibly easy to switch around and only rely on simple environment variables to manage. To go back to normal, simply run `omg reset`.
#### MultiRails by Relevance, http://thinkrelevance.com Rob Sanheim - MultiRails lead MultiRails lets you test your Rails plugin or app against many versions of Rails in one sweep. #### DESCRIPTION: MultiRails allows easy testing against multiple versions of Rails for your Rails specific gem or plugin. It also has tentative support testing Rails applications against multiple versions of Rails. Use MultiRails to hook in Rails 2.0 testing in your continuous integration. Still working on Rails 2.0 support? Use MultiRails to see where your test suite falls down against the 2.0 preview releases of Rails. MultiRails was initially developed by members of Relevance while developing Streamlined against edge Rails. To see how Streamlined uses MultiRails, go to http://trac.streamlinedframework.org. #### FEATURES: * easily test plugins/extensions using a require from your test_helper.rb and a require in your RakeFile * rake tasks to test against a specified version of Rails, the latest version, or all versions * tentative support for testing plain Rails apps against multiple versions of Rails * Uses rubygems for version management of Rails #### TODOs: * improve docs on how to override what files are required by multi_rails * maybe add ability to load plain Rails versions -- ie checked out copies not in RubyGems #### NOTES: * (__For Rails apps only__) multi_rails will rename your vendor/rails directory to vendor/rails.off if it finds one within your rails app. We have to do this to make Rails fall back to RubyGems rails. Multi_rails will rename back to the correct vendor/rails when done testing, so it will not interrupt your app in normal use. * (__For Rails apps only__) multi_rails needs to add a line to top of your environment.rb to hook into -- see the instructions below for more details
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.