Load and parse a file that might be JS, JSON, YAML, or CSON
Load whatever u wanna loader with webpack.
Insert code to load a module corresponding to JSX pragma.
Adds animated effect to the content, so the app can load whatever is needed.
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
Minimal module to check if a file is executable.
Autoload Config for PostCSS
Build Content Security Policy directives.
Read and parse a JSON file
Utility module to print pretty messages on SIGINFO/SIGUSR1
Load tsconfig.json
Load shared commitlint configuration
Utility to dynamically load ESM modules in TypeScript CommonJS projects
Utility function to load nyc configuration
Reverse an SVG path (or subpath)
The router for easy microfrontends
Datadog CI plugin for `junit` commands
Easily measure performance metrics in JavaScript
A library for arbitrary-precision decimal and non-decimal arithmetic
Lodash modular utilities.
Intercept imports in Node.js
The Pug loader is responsible for loading the depenendencies of a given Pug file.
Dynamic script loading for browser
AWS SDK for JavaScript Elastic Load Balancing V2 Client for Node.js, Browser and React Native
Sedative helps you keep track of all your settings. They can be Constants, Switches, or whatever. They're kept in a pseudo-object for convenience. Your settings are read from a yaml file and can be individually loaded for each environment.
This gem provides an API for parallel processing like the parallel gem but distributed and scalable over different machines. All this with minimum configuration and minimum dependencies to specific technologies and using the rails ecosystem. Dipa provides a rails engine which depends on ActiveJob and ActiveStorage. You can use whatever backend you like for any of this components and configure them for your specific usecase. The purpose of this gem is to distribute load heavy and long running processing of large datasets over multiple processes or machines using ActiveJob.
== E9Tags An extension to ActsAsTaggableOn[http://github.com/mbleigh/acts-as-taggable-on] which "improves" on custom tagging, or at least makes it more dynamic. Additionally it provides some autocomplete rack apps and the corresponding javascript. == Installation 1. E9Tags requires jquery and jquery-ui for the autocompletion and tag-adding form, be sure they're loaded in your pages where the tags form will be rendered. 2. E9Tags extends ActsAsTaggableOn and requires it. Run it's generator if you have not. 3. Run the E9Tags install script to copy over the required JS rails g e9_tags:install 4. Then make sure it is loaded, how you do that doesn't matter, e.g. <%= javascript_include_tag 'e9_tags' %> 5. Create an initializer for that sets up the taggable models and their controllers. This gives the models the tag associations and methods and prepares their controller to handle the otherwise unexpected tag params. require 'e9_tags' require 'contacts_controller' require 'contact' E9Tags.controllers << ContactsController E9Tags.models << Contact OR You can just include the modules in your classes yourself. The first way really exists for the case where the classes you wish to extend are part of another plugin/gem. # in contact.rb include E9Tags:Model # in contacts_controller.rb include E9Tags::Controller 6. Render the tags form partial in whatever model forms require it. = render 'e9_tags/form', :f => f If you pass a context, it will be locked and no longer possible to change/add the contexts on the form (and as a side effect, the tags autocompletion will be restricted to that context). = render 'e9_tags/form', :f => f, :context => :users Finally if you pass a 2nd arg to :context you can set a tag context to be "private" (default is false). In this case the tag context will be locked as private (typically suffixed with *), meaning that the tags will not be publicly searchable/visible. This is useful for organizational tags tags, say if you wanted to arbitrarily group records, or create a custom search based on a tag context. = render 'e9_tags/form', :f => f, :context => [:users, true] NOTE: The form and javascript are intended to work out of the box, but the certainly aren't going to look pretty. If you do intend to use the forms, you'll no doubt need to style them.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.