Results for developing_gems

A CLI tool to bootstrap project configuration files

A crate for gems

High level Ruby bindings. Write Ruby extension gems in Rust, or call Ruby code from a Rust binary.

CLDR-sourced timezone name translations for 152 timezones across 36 locales (data crate)

CLDR-sourced country name translations for 257 territory codes across 168 locales (data crate)

Alternative to Pathname

Gemfile support for deps-lsp

A Rust network address parsing and arithmetic library

A fast, intelligent RubyGems proxy/mirror server written in Rust

Rust client for PeasyText — text tools, glossary, and guides API

Markdown code chunk runner and renderer

Fix all vulnerabilities that are fixed.

Include development gems, but only if we're not in production. Provides a method (DevelopingGems.gems) that can be invoked in the Gemfile, and one (DevelopingGems.requires) that can be used in the code to require the gems. The standard list of development gems is: - pry - pry-stack_explorer - pry-doc This may be overridden in two ways: - The DevelopingGems.gems and DevelopingGems.requires methods take an optional argument that is an array of gem names, which it will use. - If a $DEVELOPING_GEMS environment variable exists, it will be used. It is expected to be a list of gem names, separated by spaces.