gt定制脚手架
A deep deletion module for node (like `rm -rf`)
Node.js native addon build tool
Skillflag producer CLI reference implementation.
> A simple utility to get the packages from a monorepo, whether they're using Yarn, npm, Lerna, pnpm, Bun or Rush
Android Studio Vector Drawable tool
CLI tool to update caniuse-lite to refresh target browsers from Browserslist config
JavaScript build tool, similar to Make or Rake
The CLI tool to run `eslint --fix` for each rule
Checksum utility for node
A wrapper around Sauce Labs REST API
CLI tool for Angular
Paragraph Tool for Editor.js
app-builder precompiled binaries
No description provided.
Stylish console.log for node
command-line-tool
A package for detecting all duplicated property keys of a JSON string.
Convert Workspaces to TypeScript's Project References
InlineCode Tool for Editor.js
A JavaScript Regular Expression library, extending the standard RegExp class with missing functionality
Pa11y CI is a CI-centric accessibility test runner, built using Pa11y
Marker Tool for Editor.js
An NPX command to install and list Model Context Protocols from Smithery
CLI tools for interacting with the Gitea API. Mainly for attaching files to releases.
A barebones GTF toolkit with fast nom-based IO
Part of the zng project.
Process monitoring tool. Inspired from Bluepill and God. Requires Ruby(MRI) >= 1.9.3-p194. Uses Celluloid and Celluloid::IO.
## Why I have to develop this tool One of my ruby project is using bundler to manage gem dependencies. But the `Gemfile` is very complicate. It requires external `Gemfile` by using ruby `eval`. Because I have lots of similar projects that will use same piece of gems. So I decide to abstract these gems into a standalone `Gemfile`. And let those projects’ `Gemfile` loads it. The problem I met is when I building my docker image. I hope that image can pre-install all the ruby gems in that `Gemfile.lock`. Unluckily, `bundle install` require you must have the `Gemfile`. So I have to find out a way to revert `Gemfile.lock` to a usable `Gemfile`. So here we are!
rwdwords is a Dictonary lookup tool using rwdtinker and RubyWebDialogs. Requires rwdtinker >1.56
FORK FOR TESTING. Process monitoring tool. Inspired from Bluepill and God. Requires Ruby(MRI) >= 1.9.3-p194. Uses Celluloid and Celluloid::IO.
Graphviz wrapper for Ruby. This can be used as a common library, a rails plugin and a command line tool. == FEATURES/PROBLEMS: GraphvizR is graphviz adapter for Ruby, and it can: * generate a graphviz dot file, * generate an image file by means of utilizing graphviz, * interprete rdot file and generate an image file, * and, generate a graph image file in rails application as a rails plugin. == SYNOPSYS: === Command Line: bin/graphviz_r sample/record.rdot === In Your Code: This ruby code: gvr = GraphvizR.new 'sample' gvr.graph [:label => 'example', :size => '1.5, 2.5'] gvr.beta [:shape => :box] gvr.alpha >> gvr.beta (gvr.beta >> gvr.delta) [:label => 'label1'] gvr.delta >> gvr.gamma gvr.to_dot replies the dot code: digraph sample { graph [label = "example", size = "1.5, 2.5"]; beta [shape = box]; alpha -> beta; beta -> delta [label = "label1"]; delta -> gamma; } To know more detail, please see test/test_graphviz_r.rb === On Rails : <b>use _render :rdot_ in controller</b> def show_graph render :rdot do graph [:size => '1.5, 2.5'] node [:shape => :record] node1 [:label => "<p_left> left|<p_center>center|<p_right> right"] node2 [:label => "left|center|right"] node1 >> node2 node1(:p_left) >> node2 node2 >> node1(:p_center) (node2 >> node1(:p_right)) [:label => 'record'] end end <b>use rdot view template</b> class RdotGenController < ApplicationController def index @label1 = "<p_left> left|<p_center>center|<p_right> right" @label2 = "left|center|right" end end # view/rdot_gen/index.rdot graph [:size => '1.5, 2.5'] node [:shape => :record] node1 [:label => @label1] node2 [:label => @label2] node1 >> node2 node1(:p_left) >> node2 node2 >> node1(:p_center) (node2 >> node1(:p_right)) [:label => 'record'] == DEPENDENCIES: * Graphviz (http://www.graphviz.org) == TODO: == INSTALL: * sudo gem install graphviz_r * if you want to use this in ruby on rails * script/plugin install http://technohippy.net/svn/repos/graphviz_r/trunk/vendor/plugins/rdot == LICENSE: (The MIT License)
Tool(s) to help synchronize Git -> Chef server
cartage-bundler is a plug-in for {cartage}[https://github.com/KineticCafe/cartage] that uses Ruby {Bundler}[http://bundler.io] to install application dependencies into the <tt>vendor/bundle</tt> path to allow for clean deployments in environments with strict access control rules and without requiring development tools on production servers. Cartage provides a repeatable means to create a package for a server-side application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt.
== DBT (Dependencies and deBugging Tool) DBT is a tool that helps declare dependencies (+app.files_dependencies+) and assists with debugging in a RubyMotion project. It looks for 'break', 'requires', and 'provides' commands (it does a *teensy* bit of code analyzing to provide some defaults) to make your RubyMotion +Rakefile+ and +debugger_cmds+ files short and consistent. To use, include this gem, and add +DBT.analyze(app)+ to your +Rakefile+ in the <tt>Motion::Project::App.setup</tt> block. In your source code you can add DBT commands and those will be translated into directives for +app.files_dependencies+ and +debugger_cmds+. Run +rake+ or <tt>rake debug=1</tt>, and off you go!
Pluggable classes are automatically registered from classes that subclass from <classname>::Plugin, and can use tools for managing, installing and delegating methods therefrom.
Utopia is a website generation framework which provides a robust set of tools to build highly complex dynamic websites. This package includes a useful <google-analytics> tag for easily integrating with Google Analytics.
Tool that allows to build AST tree representation from the swift's AST dump swift-ast-dump-parser <ast-file>
TarPit provides the glue for an unholy union of build tools. TarPit includes general automation for any rubygems project. It originally used and remains heavily influenced by Hoe (e.g. Manifest.txt.) However, it fully supports use of Bundler. The gemspec benefits from sensible automation but remains in a <project>.gemspec per Bundler's requirements.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.