[{"data":1,"prerenderedAt":350},["ShallowReactive",2],{"fougere:post.list:{}":3,"reference:\u002Freference\u002Fpackages\u002Fhttp":6,"reference-pages":128},{"items":4,"hasMore":5},[],false,{"id":7,"title":8,"body":9,"description":19,"extension":120,"file":121,"meta":122,"navigation":123,"path":124,"seo":125,"stem":126,"__hash__":127},"reference\u002Freference\u002Fpackages\u002Fhttp.md","@fougere\u002Fhttp",{"type":10,"value":11,"toc":114},"minimark",[12,16,20,26,31,59,63,70],[13,14,8],"h1",{"id":15},"fougerehttp",[17,18,19],"p",{},"The words every HTTP door speaks — a method, an answer, the headers a state travels in.",[17,21,22,23],{},"Entries: ",[24,25,8],"code",{},[27,28,30],"h2",{"id":29},"what-you-import","What you import",[32,33,34,46],"table",{},[35,36,37],"thead",{},[38,39,40,44],"tr",{},[41,42,43],"th",{},"name",[41,45],{},[47,48,49],"tbody",{},[38,50,51,57],{},[52,53,54],"td",{},[24,55,56],{},"HTTP_METHODS",[52,58],{},[27,60,62],{"id":61},"types","Types",[17,64,65,66,69],{},"TypeScript types only — they do not run. Import them with ",[24,67,68],{},"import type"," to type your own code: a variable, a parameter, an option object.",[32,71,72,80],{},[35,73,74],{},[38,75,76,78],{},[41,77,43],{},[41,79],{},[47,81,82,91,100],{},[38,83,84,89],{},[52,85,86],{},[24,87,88],{},"HttpMethod",[52,90],{},[38,92,93,98],{},[52,94,95],{},[24,96,97],{},"ResponseResult",[52,99],{},[38,101,102,107],{},[52,103,104],{},[24,105,106],{},"HttpCarrier",[52,108,109,110,113],{},"What an HTTP door carries a caller's state in for one request: the headers it arrived with, and those it leaves with. The agreement between the doors and a keeper ",[24,111,112],{},"over: 'http'"," — a cookie.",{"title":115,"searchDepth":116,"depth":116,"links":117},"",2,[118,119],{"id":29,"depth":116,"text":30},{"id":61,"depth":116,"text":62},"md",null,{},true,"\u002Freference\u002Fpackages\u002Fhttp",{"title":8,"description":19},"reference\u002Fpackages\u002Fhttp","TB7Qen73W2R4fHYwgK2F2Fve9M4Uk-wGNv_vj-PteiY",[129,134,139,144,149,154,159,164,169,174,179,184,189,194,199,204,209,214,219,224,229,234,239,244,249,254,259,264,269,274,275,280,285,290,295,300,305,310,315,320,325,330,335,340,345],{"path":130,"title":131,"description":132,"stem":133},"\u002Freference\u002Fcli","CLI","fougere new, serve, call, sync, graph — composing a workspace, hosting one frond, invoking an operation from a shell.","reference\u002F01.cli",{"path":135,"title":136,"description":137,"stem":138},"\u002Freference\u002Ferrors","Error codes","Every code an operation can refuse with, and its HTTP status.","reference\u002F02.errors",{"path":140,"title":141,"description":142,"stem":143},"\u002Freference\u002Fconfig","fougere.config.ts","Every key the app config admits, and which package answers each one.","reference\u002F03.config",{"path":145,"title":146,"description":147,"stem":148},"\u002Freference\u002Ffrond-config","frond.config.ts","Every key a frond's own config admits.","reference\u002F04.frond-config",{"path":150,"title":151,"description":152,"stem":153},"\u002Freference\u002Fsources","Source types","Every type an entry of sources: may name, and the keys it admits.","reference\u002F05.sources",{"path":155,"title":156,"description":157,"stem":158},"\u002Freference\u002Fprotocols","Protocols","What protocols: may serve, and what each admits.","reference\u002F06.protocols",{"path":160,"title":161,"description":162,"stem":163},"\u002Freference\u002Fstates","State keepers","How state: may keep a caller's values.","reference\u002F07.states",{"path":165,"title":166,"description":167,"stem":168},"\u002Freference\u002Fforms","Forms","The types a frond is written with — each one read by the scan.","reference\u002F08.forms",{"path":170,"title":171,"description":172,"stem":173},"\u002Freference\u002Fports","Ports Fougere opens","The classes you stand in front of, or extend, to change what the framework does.","reference\u002F09.ports",{"path":175,"title":176,"description":177,"stem":178},"\u002Freference\u002Finterfaces","Interfaces to extend","The empty interfaces a package augments with declare module, and who augments each.","reference\u002F10.interfaces",{"path":180,"title":181,"description":182,"stem":183},"\u002Freference\u002Fdiagnostics","Boot and check diagnostics","Every code a boot, the scan or fougere check can raise, and what it says.","reference\u002F11.diagnostics",{"path":185,"title":186,"description":187,"stem":188},"\u002Freference\u002Fpackages\u002Fadapter-duckdb","@fougere\u002Fadapter-duckdb","Read across an app's sources — one SQL query over what DuckDB can attach.","reference\u002Fpackages\u002Fadapter-duckdb",{"path":190,"title":191,"description":192,"stem":193},"\u002Freference\u002Fpackages\u002Fadapter-env","@fougere\u002Fadapter-env","The process environment as a source — MEILI_URL read as Meili's url, judged at boot.","reference\u002Fpackages\u002Fadapter-env",{"path":195,"title":196,"description":197,"stem":198},"\u002Freference\u002Fpackages\u002Fadapter-file","@fougere\u002Fadapter-file","Rows as files — one JSON or YAML file per row, in a directory per entity.","reference\u002Fpackages\u002Fadapter-file",{"path":200,"title":201,"description":202,"stem":203},"\u002Freference\u002Fpackages\u002Fadapter-graphql","@fougere\u002Fadapter-graphql","Entity → GraphQL types, inputs and CRUD, through Pothos.","reference\u002Fpackages\u002Fadapter-graphql",{"path":205,"title":206,"description":207,"stem":208},"\u002Freference\u002Fpackages\u002Fadapter-memory","@fougere\u002Fadapter-memory","Rows in a Map — the source a first run meets, and the one that ships no driver.","reference\u002Fpackages\u002Fadapter-memory",{"path":210,"title":211,"description":212,"stem":213},"\u002Freference\u002Fpackages\u002Fadapter-rest","@fougere\u002Fadapter-rest","Entity → REST routes.","reference\u002Fpackages\u002Fadapter-rest",{"path":215,"title":216,"description":217,"stem":218},"\u002Freference\u002Fpackages\u002Fadapter-sql","@fougere\u002Fadapter-sql","Entity → SQL tables through Kysely (SQLite, PostgreSQL, MySQL, SQL Server).","reference\u002Fpackages\u002Fadapter-sql",{"path":220,"title":221,"description":222,"stem":223},"\u002Freference\u002Fpackages\u002Fadmin","@fougere\u002Fadmin","A back-office derived from what the app already says it hosts — a react-admin DataProvider over the Fougere wire.","reference\u002Fpackages\u002Fadmin",{"path":225,"title":226,"description":227,"stem":228},"\u002Freference\u002Fpackages\u002Fapp","@fougere\u002Fapp","The host-independent half of a Fougere app: boot, call envelope, REST table, form contract.","reference\u002Fpackages\u002Fapp",{"path":230,"title":231,"description":232,"stem":233},"\u002Freference\u002Fpackages\u002Fauth-better","@fougere\u002Fauth-better","Fougere's auth — a translation layer onto better-auth.","reference\u002Fpackages\u002Fauth-better",{"path":235,"title":236,"description":237,"stem":238},"\u002Freference\u002Fpackages\u002Fcalls","@fougere\u002Fcalls","Optional call log for Fougere: a bounded ring of every dispatch, served as an rpc operation. Read it with `fougere devtools`.","reference\u002Fpackages\u002Fcalls",{"path":240,"title":241,"description":242,"stem":243},"\u002Freference\u002Fpackages\u002Fcli","@fougere\u002Fcli","The Fougere CLI — compose a workspace, serve a frond, call an operation.","reference\u002Fpackages\u002Fcli",{"path":245,"title":246,"description":247,"stem":248},"\u002Freference\u002Fpackages\u002Fcompiler","@fougere\u002Fcompiler","The scan: Fougere reading a project's source to produce the descriptors core boots from. Needs a filesystem and a TypeScript program.","reference\u002Fpackages\u002Fcompiler",{"path":250,"title":251,"description":252,"stem":253},"\u002Freference\u002Fpackages\u002Fcontainer","@fougere\u002Fcontainer","Fougere's DI container: resolution by type, wired from the AST scan. Zero dependencies.","reference\u002Fpackages\u002Fcontainer",{"path":255,"title":256,"description":257,"stem":258},"\u002Freference\u002Fpackages\u002Fcore","@fougere\u002Fcore","The core — scan, call contract, façades, remote stand-ins.","reference\u002Fpackages\u002Fcore",{"path":260,"title":261,"description":262,"stem":263},"\u002Freference\u002Fpackages\u002Fdecorators","@fougere\u002Fdecorators","Configuration sugar (@config) — declarative, never hidden runtime.","reference\u002Fpackages\u002Fdecorators",{"path":265,"title":266,"description":267,"stem":268},"\u002Freference\u002Fpackages\u002Fdefaults","@fougere\u002Fdefaults","The conventional boot of a Fougere app — the one place storage is wired.","reference\u002Fpackages\u002Fdefaults",{"path":270,"title":271,"description":272,"stem":273},"\u002Freference\u002Fpackages\u002Fgraph","@fougere\u002Fgraph","Fougere's graph: a labelled directed multigraph, and the four questions asked of it — order, cycles, components, reach. Zero dependencies.","reference\u002Fpackages\u002Fgraph",{"path":124,"title":8,"description":19,"stem":126},{"path":276,"title":277,"description":278,"stem":279},"\u002Freference\u002Fpackages\u002Flog","@fougere\u002Flog","Logging for Fougere: two lines for every call, in every process, and a file destination for the lines.","reference\u002Fpackages\u002Flog",{"path":281,"title":282,"description":283,"stem":284},"\u002Freference\u002Fpackages\u002Fnext","@fougere\u002Fnext","The Next.js adapter: mounting, and the one import that is genuinely Next.","reference\u002Fpackages\u002Fnext",{"path":286,"title":287,"description":288,"stem":289},"\u002Freference\u002Fpackages\u002Fnuxt","@fougere\u002Fnuxt","The Nuxt module: Fougere's client primitives and server surface.","reference\u002Fpackages\u002Fnuxt",{"path":291,"title":292,"description":293,"stem":294},"\u002Freference\u002Fpackages\u002Fobservability","@fougere\u002Fobservability","Optional observability for Fougere: one span per operation, W3C Trace Context across any transport.","reference\u002Fpackages\u002Fobservability",{"path":296,"title":297,"description":298,"stem":299},"\u002Freference\u002Fpackages\u002Foclif","@fougere\u002Foclif","A frond's operations, as a terminal: topics, flags and help derived from what it declares.","reference\u002Fpackages\u002Foclif",{"path":301,"title":302,"description":303,"stem":304},"\u002Freference\u002Fpackages\u002Freact","@fougere\u002Freact","Fougere's four primitives as React hooks — host-independent.","reference\u002Fpackages\u002Freact",{"path":306,"title":307,"description":308,"stem":309},"\u002Freference\u002Fpackages\u002Fregistry","@fougere\u002Fregistry","Fougere's registry: one answer per name, refused when a second one arrives, and a reload that says it replaces. Zero dependencies.","reference\u002Fpackages\u002Fregistry",{"path":311,"title":312,"description":313,"stem":314},"\u002Freference\u002Fpackages\u002Fschema","@fougere\u002Fschema","The entity and its 4 axes — shape, role, lifecycle, boundary. Subject-owned judgments, edge-safe.","reference\u002Fpackages\u002Fschema",{"path":316,"title":317,"description":318,"stem":319},"\u002Freference\u002Fpackages\u002Fstate-cookie","@fougere\u002Fstate-cookie","A caller's state kept in a cookie — what `state: { cart: { cookie: {} } }` names, signed by core, carried by every HTTP door.","reference\u002Fpackages\u002Fstate-cookie",{"path":321,"title":322,"description":323,"stem":324},"\u002Freference\u002Fpackages\u002Fstate-session","@fougere\u002Fstate-session","A caller's state kept in a session — what `state: { cart: { session: {} } }` names: one cookie holds a reference, the values a row in a source.","reference\u002Fpackages\u002Fstate-session",{"path":326,"title":327,"description":328,"stem":329},"\u002Freference\u002Fpackages\u002Fsvelte","@fougere\u002Fsvelte","Fougere's four primitives as Svelte stores — host-independent.","reference\u002Fpackages\u002Fsvelte",{"path":331,"title":332,"description":333,"stem":334},"\u002Freference\u002Fpackages\u002Ftesting","@fougere\u002Ftesting","Tests derived from the declaration — cases, stubs and a gradient of realities.","reference\u002Fpackages\u002Ftesting",{"path":336,"title":337,"description":338,"stem":339},"\u002Freference\u002Fpackages\u002Ftransport-http","@fougere\u002Ftransport-http","The call contract on the wire, in JSON-RPC 2.0 (server + client).","reference\u002Fpackages\u002Ftransport-http",{"path":341,"title":342,"description":343,"stem":344},"\u002Freference\u002Fpackages\u002Fvite","@fougere\u002Fvite","The Vite plugin: what any Vite-built host must know to run a Fougere app.","reference\u002Fpackages\u002Fvite",{"path":346,"title":347,"description":348,"stem":349},"\u002Freference\u002Fpackages\u002Fworkflow","@fougere\u002Fworkflow","A release that goes to the end: the journal is three entities, the sweep is an operation, and a shared journal is one line of remotes:.","reference\u002Fpackages\u002Fworkflow",1794396612980]