React hook wrapping the remote-storage library.
Firebase JavaScript library for web and Node.js
Get the git remote origin URL from your local git repository. Remember! A remote origin must exist first!
Send samples to prometheus via remote_write from NodeJS
A wrapper of the `@mdx-js/mdx` for the `nextjs` applications in order to load MDX content. It is a fork of `next-mdx-remote`.
An RPC library with strong support for simulating the transfer of functions via postMessage
A collection of DOM-based utilities for synchronizing elements between JavaScript environments
safely create multiple ReadStream or WriteStream objects from the same file descriptor
Appium proxy for Remote Debugger protocol
SSH remote port forward
This library provides a custom React renderer that gives you the full power of React for your remote application, and provides an optional host layer that makes it easy for existing React apps to integrate a remote root. For a full overview of how `@remot
Sets up Turborepo Remote Caching to work with GitHub Actions built-in cache
Get the remote origin URL of a Git repository
This library provides the core model for maintaining a tree of UI components, and for communicating operations on that tree to another context through tiny messages. For a full overview of how `@remote-ui/core` fits in to the different pieces of remote-ui
The Remote Config package of the Firebase JS SDK
[](https://github.com/electron/remote/actions/workflows/test.yml) [](https://npmjs.org/package/@electron/remote
The compatibility package of Remote Config
PostCSS plugin to import CSS files
A polyfill for the browser APIs used by Remote DOM
Launch latest Chrome with the Devtools Protocol port open
Yjs encoding protocols
Remote proxy for Model Context Protocol, allowing local-only clients to connect to remote servers using oAuth
Launch latest Edge with the Devtools Protocol port open
Cross origin web worker
Retrieves remote directory via SFTP and stores it in local Git repository.
A tool for deploying complete HTML Apps to S3-compatible object storage. Cache-Control max-age headers are set based on file type. Closync uses the fog gem to interact with both local and remote storage.
Backup is a RubyGem (for UNIX-like operating systems: Linux, Mac OSX) that allows you to configure and perform backups in a simple manner using an elegant Ruby DSL. It supports various databases (MySQL, PostgreSQL, MongoDB and Redis), it supports various storage locations (Amazon S3, Rackspace Cloud Files, Dropbox, any remote server through FTP, SFTP, SCP and RSync), it provide Syncers (RSync, S3) for efficient backups, it can archive files and directories, it can cycle backups, it can do incremental backups, it can compress backups, it can encrypt backups (OpenSSL or GPG), it can notify you about successful and/or failed backups (Email or Twitter). It is very extensible and easy to add new functionality to. It's easy to use.
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace
No description provided.
No description provided.
No description provided.