Search Results for "cpu-g"

hotkeys-js is a tiny, framework-agnostic library for binding keyboard shortcuts in the browser, from simple key presses to complex combos and sequences. It provides a declarative API to register handlers like ctrl+k, shift+alt+p, or g g, and it normalizes key behavior across major browsers. The library includes scoping, so the same shortcut can trigger different actions depending on page context, and it offers filters to ignore inputs when the user is typing in form fields. You can enable or disable groups of shortcuts dynamically, making it well suited for SPAs and dashboard apps. ...

workerpool is a JavaScript library that simplifies the creation and management of worker threads and process pools for parallel task execution in Node.js and browser environments. The project provides an abstraction layer that allows developers to offload CPU-intensive operations to background workers without manually handling thread communication or lifecycle management. It supports task queuing, dynamic worker scaling, timeouts, transferable objects, and proxy-based APIs for interacting with worker functions as if they were local calls. workerpool is designed to improve application responsiveness and throughput in workloads involving heavy computation, data processing, or asynchronous execution. ...

CAF (Cancelable Async Flows) is a small utility that brings cooperative cancellation to JavaScript async workflows. It wraps async generators or promise-returning functions so they can respond to a cancel signal and halt work early, preventing wasted CPU and stray side effects. The library encourages a disciplined pattern: pass a token into your task, periodically check it, and unwind gracefully when cancellation is requested. This approach avoids brittle timeouts and “fire-and-forget” leaks by making cancellation a first-class concern. CAF is framework-agnostic and pairs well with fetch, timers, or custom async primitives, giving you a consistent contract for stopping in-flight operations. ...

...This is fine for things like language features but can be a frustrating overhead for libraries that allow for compile-time code transformation as an optimization. babel-plugin-macros defines a standard interface for libraries that want to use compile-time code transformation without requiring the user to add a babel plugin to their build system (other than babel-plugin-macros, which is ideally already in place). There is cpu usage/time overhead; the client needs to run the code to generate these classes every time the page loads. There is code bundle size overhead; the client needs to receive a CSS parser in order to generate these class names, and shipping this makes the amount of js the client needs to parse larger. Eval-ing out code at compile time that will be baked into the runtime code, for instance, to get a list of directories in the filesystem.