An issues generation tool for GitHub pull requests
This module provides native bindings to ecdsa secp256k1 functions
Unicode to ASCII transliteration / slugify module for node.js, browser, Web Worker, ReactNative and CLI.
A package to seed your database using Drizzle ORM
A generational pseudo-LRU cache with strict maximum size limits.
Next generation ANTLR Tool
React integration for Kubb's fabric - JSX runtime and component-based code generation with React reconciler for building type-safe generators
Library that generates Typescript clients based on the OpenAPI specification.
[](https://www.npmjs.com/package/@google/genai) [](https://www.npmjs.com/package/@google/genai)
A Prisma generator that creates Zod schemas for all of your models
sdk for interacting with glacier-api
No-dependencies, low-level, high-performance JIT code generation package for JavaScript
Next generation testing framework powered by Vite
Automatic create index.ts file
Automatic create index.ts file
CLI tool for Genspark Tool API - search, crawl, analyze images, generate media
DPoP (RFC9449) for JavaScript Runtimes
Modular Prisma Studio components
A JavaScript parser
A plugin for Vite (v4 and higher) to generate useful modules at bundle-time.
Packaging library for the Salesforce packaging platform
A swagger client generator for typescript
Babel compiler core.
Babel Types is a Lodash-esque utility library for AST nodes
Changelog generation has never been so easy. Fully automate changelog generation - this gem generate changelog file based on tags, issues and merged pull requests from GitHub.
Generate GitHub Issue template from Issuetempl
When rails throws excpetion, this gem will create issue and if project available, it will create project, assign developer and set tags if availabe
From a YAML specification, create a batch of Jira issues allowing for variable substitutions.
It generates a release note based on the issues keys and descriptions found in the commits
A new check for puppet-lint that validates generic whitespace issues in manifests.
Changelog generation has never been so easy. Fully automate changelog generation - this gem generate change log file based on tags, issues and merged pull requests from Github issue tracker.
Changelog generation has never been so easy. Fully automate changelog generation - this gem generate changelog file based on tags, issues and merged pull requests from GitHub.
Rails 4, much to everyone's annoyance, provides no option to generate both digest and non-digest assets. Installing this gem automatically creates both digest and non-digest assets which are useful for many reasons. See this issue for more details: https://github.com/rails/sprockets-rails/issues/49
Enables the creation of scenarios that involve creating a rails project, starting and stoppping of servers, generating projects, editing files, issuing http requests, running of commands, etc. Output is captured as a single HTML file that can be viewed locally or uploaded. Additionally, there is support for verification, in the form of defining assertions based on selections (typically CSS) against the generated HTML.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Rails 4, much to everyone's annoyance, provides no option to generate both digest and non-digest assets. Installing this gem automatically creates both digest and non-digest assets which are useful for many reasons. See this issue for more details: https://github.com/rails/sprockets-rails/issues/49
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.