The GritQL plugin is the mechanism that lets a project add its own lint rules without waiting for the Biome team to add them. The plugin is a .grit file that declares a structural pattern, and the pattern matches against the syntax tree, not the raw text. The Biome documentation states the model plainly: the…
A monorepo is a repository that holds multiple packages, and each package can have its own conventions, its own rules, and its own formatting preferences. Biome’s monorepo support is built on the nested configuration model: the tool looks for the nearest biome.json from the current working directory, and if it does not find one, it…
The overrides array is the mechanism that applies a different configuration to a subset of the files without splitting the project into the multiple biome.json files. The array is the list of the objects, and each object has the includes globs and the configuration that applies to the matched files. The configuration in the override…
The biome-ignore comment is the mechanism that disables a lint rule, an assist action, or a syntax check for the specific code without the configuration change. It is the escape hatch for the one-off case—the generated file, the intentional violation, the third-party pattern—that the project does not want to disable globally. The Biome documentation states…
The –staged flag is the mechanism that limits a Biome check to the files in the Git index, and it is the core of a pre-commit hook that does not waste time on the untouched files. The flag is a check command option, not a ci command option, because the staged files are a local…
The Server Actions are the React 19 and Next.js mechanism for the mutations that run on the server, and the React Hook Form is the client-side state manager. The two are not the same layer, and the integration is the question of where the validation and the form state live. The Next.js documentation offers two…
File uploads are the one field type where React Hook Form’s uncontrolled model meets a browser API that refuses to be controlled. The <input type=”file”> element does not accept a value prop that can be set programmatically—the browser throws a DOMException if you try—and its value is a FileList object, not a string . The…
The multi-step form is not a different form API. It is the single useForm instance whose fields are spread across the multiple screens, and the state preservation is the mechanism that keeps the instance alive while the screens mount and unmount. The React Hook Form documentation states the rule plainly: “Fields from earlier steps unmount…
The synchronous validation runs the client-side rules and returns the result immediately. The asynchronous validation sends the value to the server or the external service and waits for the response. The React Hook Form supports both, and the difference is not the API surface—the validate rule accepts the async function the same way it accepts…
The @hookform/resolvers package is the single bridge between React Hook Form and the validation libraries, and the Zod chapter covered one of its adapters. The package ships the adapters for the several libraries—Yup, Joi, Superstruct, Valibot, AJV, ArkType, TypeBox, and the others—and each adapter follows the same contract: it receives the schema, validates the form…