What problem does it solve? Writing a correct netlify.toml file from memory is error-prone, with subtle syntax rules for redirects, headers, deploy contexts, and function configuration that are easy to get wrong. ## Core Features & Use Cases - Build & Dev Configuration: Set base directory, build command, publish directory, and Netlify Dev server options. - Redirects & Rewrites: Define SPA catch-alls, splats, path parameters, forced redirects, proxy rules, and country/language conditions with correct rule ordering. - Headers & Deploy Contexts: Apply per-path HTTP headers and override settings for production, deploy-preview, branch-deploy, and dev contexts. - Functions & Plugins: Configure serverless function directories, scheduled functions, edge functions, Deno import maps, plugins, and the Image CDN. - Use Case: You are deploying a React SPA to Netlify and need a catch-all rewrite to index.html, long-lived cache headers for static assets, and a separate build command for deploy previews. ## Quick Start Write a netlify.toml for my React app with an SPA catch-all redirect, immutable cache headers for /assets, and a staging branch context.
