Flareforge Lexicon
Flareforge is a rapid development framework designed to generate production-ready web applications on Cloudflare’s serverless infrastructure from a single, declarative JSON configuration. It aims to accelerate development by automating boilerplate.
Configuration
Section titled “Configuration”This is the central JSON file that defines your application’s structure, features, pricing plans, authentication providers, and custom task definitions. It serves as the single source of truth for Flareforge’s code generation engine.
Code Generation
Section titled “Code Generation”Code generation is the automated process by which Flareforge transforms your flareforge.jsonc
configuration and internal templates into functional React, TypeScript, and Cloudflare Worker code. This generated code forms the foundation of your application.
To manually trigger code generation:
npx flareforge codegen
yarn flareforge codegen
pnpm flareforge codegen
Unforge
Section titled “Unforge”Unforge
is a flareforge command that allows you to “eject” or copy internal UI component/block templates or localization files directly into your project’s codebase. This gives you full, direct control to customize them without losing the benefits of code generation for other parts of the framework. Once unforged, a file is managed by you and will not be overwritten by future framework updates.
To unforge a UI block:
npx flareforge unforge block marketing/cta
yarn flareforge unforge block marketing/cta
pnpm flareforge unforge block marketing/cta
In Flareforge, a Block is a larger, reusable UI section or layout that often combines multiple Components to form a distinct part of a page (e.g., a login form, a pricing section, an asset list). Blocks are found in flareforge/ui/blocks
and are designed to be easily interchangeable and composable.
When you “unforge” a UI element, you are often working with a block.
Cloudflare Workers
Section titled “Cloudflare Workers”Cloudflare’s serverless platform for deploying and running your application code at the edge.
Cloudflare D1
Section titled “Cloudflare D1”Cloudflare’s SQL database built on SQLite. D1 provides a fast, persistent data layer for Flareforge applications, with data accessible directly from Workers at the edge.
Cloudflare R2
Section titled “Cloudflare R2”R2 is used in Flareforge for storing static assets like user-uploaded images, videos, and other files, offering high availability and low cost without egress fees.
Cloudflare Queues
Section titled “Cloudflare Queues”Queues are essential for Flareforge to handle long-running, asynchronous tasks (e.g., AI transformations, complex data processing) by decoupling them from the main request flow, improving responsiveness and reliability.
Task / Task Group
Section titled “Task / Task Group”Defined within flareforge.jsonc
, a Task Group allows you to structure collections of fields (data inputs) for specific functionalities in your application (e.g., “Scraping Request”, “Image Generation Request”).
A Task is an instance of data submitted based on a Task Group’s definition. Task Groups can be static (one instance per task) or dynamic (multiple instances, e.g., a list of characters).