Search Results for "Dependency"

Zippy is a pure Nim implementation of DEFLATE, ZLIB, GZIP, and ZIP data compression formats, aiming to be small, performant, and dependency-free.

...Some interesting data will be summarized for you, such as the percentage of time spent in a service, and whether or not operations failed. The Zipkin UI also presents a Dependency diagram showing how many traced requests went through each application. This can be helpful for identifying aggregate behavior including error paths or calls to deprecated services. Applications need to be “instrumented” to report trace data to Zipkin.

...The specification of the Brotli Compressed Data Format is defined in RFC 7932. Brotli is open-sourced under the MIT License. You can download and install brotli using the vcpkg dependency manager.

File-Type is a Node.js library that detects the file type of a Buffer or Uint8Array by examining its binary signature, supporting a wide range of file formats.

...No special tools are required, the reactivity system will detect all your changes and propagate them out to where they are being used. All changes to and uses of your data are tracked at runtime, building a dependency tree that captures all relations between state and output. This guarantees that computations depending on your state, like React components, run only when strictly needed. There is no need to manually optimize components with error-prone and sub-optimal techniques like memoization and selectors.

Convert to it! is a lightweight utility project designed to provide simple and fast file or data conversion workflows through a developer-friendly interface. The repository focuses on practical transformations between formats, making it useful in scripting pipelines, automation tasks, and small backend utilities where reliability matters more than heavy frameworks. Its structure emphasizes clarity and minimal dependencies so developers can quickly understand and extend the codebase. The tool...

...When building several big cloud applications we found a lack of great solutions (that's not to say there aren't solutions out there) for many key pieces to building scalable distributed applications while keeping the development experience simple. Wanted to build against abstract interfaces so that we could easily change implementations. Wanted the blocks to be dependency injection friendly. We were initially using an open-source Redis cache client but then it turned into a commercial product with high licensing costs. Not only that but there weren't any in-memory implementations so every developer was required to set up and configure Redis. We initially looked at NServiceBus (a great product) but it had high licensing costs (they have to eat too) and was not OSS friendly.

...For the average consumer, Time Machine is an excellent choice, especially considering many Mac owners may only have Time Machine as a backup strategy. Asimov aims to solve problems, scanning your filesystem for known dependency directories (e.g. node_modules/ living adjacent to a package.json file) and excluding them from Time Machine backups. At its essence, Asimov is a simple wrapper around Apple's tmutil program, which provides more granular control over Time Machine.

Created as a more sensible alternative to MacPorts, Fink, and Homebrew, Pacmac was inspired by Archlinux's pacman, but is not a port. All files except packages are plain text, and all executables are scripts. No compilers are necessary to create packages, just request the package by name and Pacmac will resolve the dependencies for you.