Tiny string compression module for Node.
Compression module for Nuxt 3
Gzip compression module for NowBackup database backups
AdonisJs middleware provider that wraps compression module
lzf compression module for nodejs
The compression module for CerusJS
Tiny string compression module for Node.
lzf compression module for nodejs
Node.js compression middleware
No description provided.
A production build plugin for the HPS (Hyperse) build system that provides optimized builds using Rspack with configurable compression, module filtering, and build timing for web applications.
ECC JS code based on JSBN
The smallest brotli compression module for the edge
NodeJS GZip Compression Module for Azure IoT Gateway
Prepare compressed versions of assets to serve them with Content-Encoding
Compress images in the browser
A zstd web compression module for AppExpress.
Decompression and compression plugins for loaders.gl
Lossy image compression module for JavaScript applications.
High performance (de)compression in an 8kB package
TypeScript definitions for compression
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Middleware and Plugin for request compression.
Mesh optimization library that makes meshes smaller and faster to render
DeflateRuby provides Ruby bindings for libdeflate, a heavily optimized library for DEFLATE, gzip, and zlib compression and decompression. Significantly faster than Ruby's built-in Zlib module.
sym-crypt is a core encryption module for the symmetric encryption app (and a corresponding gem) "sym", and contains the main base serialization, encryption, encoding, compression routines. sym-crypt uses a symmetric 256-bit key with the AES-256-CBC cipher, which is the same cipher as the one used by the US Government. For encyption with a password sym-crypt uses AES-128-CBC cipher. The resulting data is zlib-compressed and base64-encoded. The keys are also base64 encoded for easy copying/pasting/etc.
Ruby bindings (via Rust/magnus) for the Zstandard compressor with persistent ZSTD_CCtx / ZSTD_DCtx contexts that are reused across calls. Provides Zstd frame compress/decompress at module level and a stateful Dictionary class for dict-bound compression. Designed to be safe to call from multiple Ractors and competitive with rlz4 on small messages, where per-call context allocation in zstd-ruby dominates the cost.
<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>
Sym is a ruby library (gem) that offers both the command line interface (CLI) and a set of rich Ruby APIs, which make it rather trivial to add encryption and decryption of sensitive data to your development or deployment workflow. For additional security the private key itself can be encrypted with a user-generated password. For decryption using the key the password can be input into STDIN, or be defined by an ENV variable, or an OS-X Keychain Entry. Unlike many other existing encryption tools, Sym focuses on getting out of your way by offering a streamlined interface with password caching (if MemCached is installed and running locally) in hopes to make encryption of application secrets nearly completely transparent to the developers. Sym uses symmetric 256-bit key encryption with the AES-256-CBC cipher, same cipher as used by the US Government. For password-protecting the key Sym uses AES-128-CBC cipher. The resulting data is zlib-compressed and base64-encoded. The keys are also base64 encoded for easy copying/pasting/etc. Sym accomplishes encryption transparency by combining several convenient features: 1. Sym can read the private key from multiple source types, such as pathname, an environment variable name, a keychain entry, or CLI argument. You simply pass either of these to the -k flag — one flag that works for all source types. 2. By utilizing OS-X Keychain on a Mac, Sym offers truly secure way of storing the key on a local machine, much more secure then storing it on a file system, 3. By using a local password cache (activated with -c) via an in-memory provider such as memcached, sym invocations take advantage of password cache, and only ask for a password once per a configurable time period, 4. By using SYM_ARGS environment variable, where common flags can be saved. This is activated with sym -A, 5. By reading the key from the default key source file ~/.sym.key which requires no flags at all, 6. By utilizing the --negate option to quickly encrypt a regular file, or decrypt an encrypted file with extension .enc 7. By implementing the -t (edit) mode, that opens an encrypted file in your $EDITOR, and replaces the encrypted version upon save & exit, optionally creating a backup. 8. By offering the Sym::MagicFile ruby API to easily read encrypted files into memory. Please refer the module documentation available here: https://www.rubydoc.info/gems/sym
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.