Detect/remove browser hacks from CSS files.
Stylelint plugin for stylehacks linting.
Fault-tolerant CSS parser for PostCSS
Engine for Shiki using Oniguruma RegExp engine in WebAssembly
styled() API wrapper package for emotion.
This package is intended for Prisma's internal use
Engine for Shiki using JavaScript's native RegExp
A standalone speech rule engine for XML structures, based on the original engine from ChromeVox.
An engine which produces an intermediary structure from HTML to create a React Native render tree.
Tooltip and Popover Positioning Engine
The realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
unified engine to process multiple files, lettings users configure from the file system
Easily create highly customizable particle, confetti and fireworks animations and use them as animated backgrounds for your website. Ready to use components available also for React, Vue.js (2.x and 3.x), Angular, Svelte, jQuery, Preact, Riot.js, Inferno.
3D Engine Components for luma.gl
Rules Engine expressed in simple json
This package is intended for Prisma's internal use
Media query calculator
A tool for processing JSON-RPC messages
styled() API wrapper package for styled-components.
Wrap your standards in a tortilla and cover it in special sauce.
Generates and consumes source maps
Create an Ethereum provider using a JSON-RPC engine or middleware
The editing engine of CKEditor 5 – the best browser-based rich text editor.
RE2JS is the JavaScript port of RE2, a regular expression engine that provides linear time matching
A SubSpawn subproject to provide c/java extensions to modify non-ruby-modifiable classes necessary to implementing SubSpawn, or any other spawn/popen API in pure Ruby
Rails 3 engine which provides a hack to avoid RI_ConstraintTrigger Error bug
ActiveTranslateSelf is a Rails engine that hacks the Ruby string class and lets them translate \ themselves. Supports English, Finnish, Japanese, and others!
(This is Alex's version of Showoff, so I can share my presentations \ without waiting for pull requests and updates from busy Scott. It installs a binary called "showoff" which overwrites the official one, so if you install this hack, be careful about updates.) ShowOff is a Sinatra web app that reads simple configuration files for a presentation. It is sort of like a Keynote web app engine. I am using it to do all my talks in 2010, because I have a deep hatred in my heart for Keynote and yet it is by far the best in the field. \ The idea is that you setup your slide files in section subdirectories and then startup the showoff server in that directory. It will read in your showoff.json file for which sections go in which order and then will give you a URL to present from.
A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.