Simple pub/sub messaging for the web
React is a JavaScript library for building user interfaces.
Validate that your components can safely be updated with Fast Refresh
An **EXPERIMENTAL** Webpack plugin to enable "Fast Refresh" (also previously known as _Hot Reloading_) for React components.
A message bus client in Javascript
generate random IDs and avoid collisions
React refresh plugin for Rspack
LiveReload JS client - auto reload browser on changes
TypeScript definitions for hat
Convert form parameters to an object using the same logic as Rack
Universal HMR for SolidJS
Runtime OIDC helpers intended for use with Vercel Functions
An experimental package providing utilities for React Refresh.
Axios plugin which makes it very easy to automatically refresh the authorization tokens of your clients
The default Vite plugin for React projects
React Refresh transformer for TypeScript
TypeScript definitions for react-refresh
A passport.js add-on to provide automatic OAuth 2.0 token refreshing.
An **EXPERIMENTAL** Webpack plugin to enable "Fast Refresh" (also previously known as _Hot Reloading_) for React components.
OpenID Connect (OIDC) & OAuth2 client library
A babel-plugin to enable fast-refresh for Preact components.
Parse an HTML meta refresh value.
An implementation of React Native's RefreshControl for web, since react-native-web currently does not provide one
A Simple Pull To Refresh Component for React Application
Rack Middleware for adding Refresh field to response headers
Refresh ActiveRecord connection on each rack request.
Refresh the content of your page with a given interval
A gem to make oauth testing easier
Runs sass on heroku using rack middleware. This takes advantage of heroku's varnish to refresh the stylsehet.'
Drop-in theme that refreshes the MissionControl::Jobs UI with refined typography, a malachite color palette, light/dark mode, and JSON syntax highlighting. Zero configuration — works via Rack middleware without overriding views.
resque-alive adds a Kubernetes Liveness probe to a Resque instance. How? resque-alive provides a small rack application which exposes HTTP endpoint to return the "Aliveness" of the Resque instance. Aliveness is determined by the presence of an auto-expiring key. resque-alive schedules a "heartbeat" job to periodically refresh the expiring key - in the event the Resque instance can"t process the job, the key expires and the instance is marked as unhealthy.
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.