Trigger a generator, again and again. Output as async generator.
Trigger useEffect on demand
A generational pseudo-LRU cache with strict maximum size limits.
No-dependencies, low-level, high-performance JIT code generation package for JavaScript
[](https://www.npmjs.com/package/@google/genai) [](https://www.npmjs.com/package/@google/genai)
Next generation testing framework powered by Vite
DPoP (RFC9449) for JavaScript Runtimes
Packaging library for the Salesforce packaging platform
Next-Generation full-text search library for Browser and Node.js
A swagger client generator for typescript
No description provided.
No description provided.
No description provided.
Fastest random ID and random string generation for Node.js
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
WIP stable interfaces for interacting with Malloy.
PM2/Keymetrics advanced API
This module provides native bindings to ecdsa secp256k1 functions
Statistical routines and probability distributions.
Enlightened library to convert HTML and CSS to SVG.
allows you to declare database triggers in ruby in your models, and then generate appropriate migrations as they change
A botbase module for matching a speech keyword which then triggers a general RSC job or publishes an SPS message etc.
A completely transparent audit logging component for your application using a stored procedure and triggers. Comes with specs for your project and a rake task to generate the reverse SQL to undo changes logged.
Hayfork generates triggers to maintain a Haystack of all searchable fields that Postgres can index easily and efficiently
== Description Use +on+ and +trigger+ to send generic events from the layout to the controller. Sounds simple, but this enables a powerful method of keeping your UI logic contained in your Layout files.
Relation-aware synchronous full text search index for PostgreSQL using PL/pgSQL triggers described in and generated via ORM-agnostic Ruby.
Apexgen allows you to generate object XML, create scaffolding for triggers, classes and class methods, as well as initialize a project. Currently, only object XML generation is supported, however the other features described above are in active development.
ActiveRecord aware workflow (state machine) module that will also work with any plain old ruby object.
Rails Plugin to augment frontend development with a gulp/webpack based workflow. - Installs Javascript infrastructure in your Rails project to manage frontend assets - Provides view helpers to Rails that allow you to easily reference gulp generated assets from Rails views - Puts Livereload into the Rails middleware stack. This injects the Livereload client into Rails-renderd pages, updates are triggered from gulp.
CustomId generates unique, human-readable, prefixed string IDs (e.g. "usr_7xKmN2pQ…") for ActiveRecord models. Inspired by Stripe-style identifiers. Supports embedding shared characters from related model IDs, custom target columns, configurable random-part length, and an optional PostgreSQL trigger-based alternative.
The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.
This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.