Tools for the FAIR protocol
A family of specs for interoperable TypeScript
A type checked signal library for TypeScript (and JavaScript)
Module federation runtime package collection. You can just install it instead of installing all the packages separately.
Run commands concurrently
This module is used by a number of the other Workbox modules to share common code.
Password policies presets used by Auth0. Extracted from [password-sheriff](https://github.com/auth0/password-sheriff).
A service worker helper library to manage common request and caching patterns
Queues failed requests and uses the Background Sync API to replay them when the network is available
Simplifies communications with Workbox packages running in the service worker
n8n Workflow Automation Tool
Read/write IEEE754 floating point numbers from/to a Buffer or array-like object
A modern CSS parser and stringifier with TypeScript support
A library that makes it easier to work with Streams in the browser.
A service worker helper library to route request URLs to handlers.
This library takes a Response object and determines whether it's cacheable based on a specific configuration.
This library allows developers to opt-in to using Navigation Preload in their service worker.
A service worker helper library that expires cached responses based on age or maximum number of entries.
This library creates a new Response, given a source Response and a Range header value.
Queues failed requests and uses the Background Sync API to replay them when the network is available
This module makes it easy to get started with the Workbox service worker libraries.
Fork of GraphQL.js' execute function
A service worker helper library that uses the Broadcast Channel API to announce when a cached response has updated
A service worker helper library implementing common caching strategies.
Travail À Faire (taf) is a lightweight command-line tool that helps you manage your todos in a markdown file with support for tags and hierarchical organization.
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