/** * The export's only chrome: a floating theme toggle, since the header is gone by design. * * The two glyphs ride as inline SVG with the site's own show/hide classes, so whichever * runtime flips `dark` also flips the icon for free. Shared as a string because both * export paths inline it verbatim — the browser export at run time, the CLI export at * build time — and the two files must ship the same button. */ export const THEME_TOGGLE = ``; /** * The exported file's theme, decided when the reader opens it rather than when the export * ran. * * The live site resolves `system` through next-themes and leaves a literal `dark`/`light` * class on ``; serialising that would hand every reader the exporter's OS setting * forever. So the export strips the resolved class and ships this instead: the reader's own * `prefers-color-scheme` on load, their toggle choice if they have made one, and a listener * that keeps following the OS until they do. * * Inlined in `` by both export paths so it runs before first paint — a class set from * the body would flash the wrong theme first. `localStorage` throws outright on some * `file://` origins, which is why every access is guarded; an unreadable store just means * the file follows the OS, which is the sane default anyway. */ export const THEME_INIT = ``;