Results for keep-apps-active

keep active to prevent cold starts for your nodejs express apps hosted on free plan for render.com or heroku.com or any other cloud provider

Missing keepalive http.Agent

React Freeze

A simple hook to create infinite scroll components

Minimal async jobs utility library, with streams support

Node client library for the Portkey API

Microsoft Authentication Library for js

Microsoft Authentication Library for Node

Expose config variables to React Native apps

Page Titles for Ember applications

High-performance image processing library for native use and the web

Microsoft Authentication Library for js

Provides a React component that prevents the screen sleeping when rendered. It also exposes static methods to control the behavior imperatively.

Universal library to retrieve GitHub’s identity URL for the OAuth web flow

Attach cloud and local files in Rails applications

Intuitive, type safe and flexible Store for Vue

Plugin for accessing cli info from the command line

The official React Native and Expo components for Stream Chat, a service for building chat applications

JavaScript SDK for Base44 API

Commands to interact with Salesforce orgs

Display intelligible realtime output from concurrent processes

Microsoft Azure Storage SDK for JavaScript - Blob

MCP Apps SDK — Enable MCP servers to display interactive user interfaces in conversational clients.

Automated stream rotation useful for log files

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.