@ogygia/core

AllMajorMinorPatch Hide pre-releases
0.14.0 minor

@ogygia/core

Minor Changes

  • #1680 9fb9b44 Thanks @PuruVJ! - import.meta.og.asRegion is gone from the import.meta.og types too, so editors flag a leftover call before the build does: mark the import itself instead (import { Header as H } from '@design/system' with { wake: 'load' }).
  • #1357 55e05d4 Thanks @PuruVJ! - import.meta.og.bake moves to its own package: install @ogygia/bake, list bake() beside ogygia(), and reference @ogygia/bake/types; without the plugin a bake call fails the build with macro_needs_plugin.
  • #508 eae1add Thanks @PuruVJ! - Breaking: the barrel rewrite is a plugin now, barrels() from @ogygia/barrels, listed beside ogygia() (plugins: [ogygia(), barrels(), sveltekit()]) with the same options. Use it in place of ogygia({ barrels }), which is a build error (barrels_option_removed) that names it; debarrel(), DebarrelOptions and DebarrelMatcher are gone from ogygia/vite.
  • #532 b011a71 Thanks @PuruVJ! - - @ogygia/core, ogygia: breaking (internal paths only): ogygia/internal/region-core is gone, and ogygia/internal/compiler no longer exports set_parser or takes a pathModule option; they existed only to run the compiler in a browser. Import region and isRegion from ogygia. Build output is unchanged.
  • #533 49ff074 Thanks @PuruVJ! - - @ogygia/compiler: new package, ogygia's compiler and its Vite plugin: @ogygia/compiler (the compiler), @ogygia/compiler/vite (ogygia(), definePlugin) and @ogygia/compiler/ids. It uses core only through @ogygia/core/contract; core never depends on it. - @ogygia/core: breaking: the @ogygia/core/vite, @ogygia/core/internal/compiler and @ogygia/core/internal/compiler-ids import paths are gone. Import from ogygia/vite (or @ogygia/compiler/vite), @ogygia/compiler and @ogygia/compiler/ids instead; the names are the same. - @ogygia/core: the types of the ogygia:* virtual modules and the build's switches are named in core (@ogygia/core/contract), so core's own types no longer reach into the compiler. - ogygia: ogygia/vite, ogygia/internal/compiler and ogygia/internal/compiler-ids re-export @ogygia/compiler; apps change nothing. - @ogygia/barrels, @ogygia/cli, @ogygia/content, @ogygia/devtools, @ogygia/federation, @ogygia/flags, @ogygia/postrender, @ogygia/router: they take definePlugin and the compiler from @ogygia/compiler, a new peer dependency (ogygia brings it).
  • #1684 22e276e Thanks @PuruVJ! - createContext's old callable form is removed: no theme('dark') <Provide> entry, no theme.get(), no theme.key and no default argument. Destructure const [getTheme, setTheme, hasTheme] = createContext<Theme>('theme'), call the setter above, and ask hasTheme() where you used a default.
  • #1541 1a475de Thanks @PuruVJ! - createContext<T>(name) from ogygia now returns Svelte's [get, set, has] shape, keyed by Symbol.for(name) so the value reaches every region in the browser (const [getRuntime, setRuntime] = createContext<AppRuntime>('app-runtime')).
  • #1878 6ebfbd9 Thanks @PuruVJ! - A bare snippet now freezes through a tiny component ({@render snippet()}) rendered by Svelte's public render(), instead of a hand-written copy of Svelte's private server component shape. Frozen snippet HTML gains one empty marker (<!---->) at its end, so frozen snippets' ids, island fingerprints, freeze keys and ETags change once on upgrade.
  • #1870 97bec00 Thanks @PuruVJ! - In an app without Svelte's async mode, a <Region of={promise}> whose promise rejects now sends the error to the nearest <svelte:boundary>, as async mode does. Before, the error was an unhandled rejection no boundary could catch. With no boundary, the page still gets the promise's own error as an unhandled rejection; a region that left the page before its promise failed reports nothing.
  • #527 a4f938a Thanks @PuruVJ! - - @ogygia/insights: new package, the analysis engine the devtools dock, the profiler's report and @ogygia/testing share (what the browser measured, turned into findings). - @ogygia/core: breaking: the @ogygia/core/insights import path is gone. Install @ogygia/insights and import from it instead; the names are the same.
  • #762 99ceeb4 Thanks @PuruVJ! - core: the import.meta.og.* macros, bake above all, work only in the app's own source and in files a package lists in ogygia.files; an installed file outside that list that uses one fails the build with macro_outside_app, and its bake function never runs
  • #1354 53e96f0 Thanks @PuruVJ! - A named import takes the region mark, in .svelte, .ts and .js, and replaces import.meta.og.asRegion, which is now a build error (as_region_removed) that prints the import to write. Before: import { Search } from '@ogygia/content'; const SearchBox = import.meta.og.asRegion(Search, { wake: 'idle' }); After: import { Search as SearchBox } from '@ogygia/content' with { wake: 'idle' };. One with covers every name in its import; a marked name used as anything but a component, and a mark on a namespace, type-only or bare import, fail the build with a code.
  • #1838 9c6692d Thanks @PuruVJ! - During an upgrade from 0.12.x, an old page's deferred regions are now refused by the new server, so they keep their fallback until the visitor reloads the page. Before, the new server answered them and they hydrated wrong (the old runtime loaded the new build's island and it failed). The refusal is x-ogygia-deny: shape for any region URL minted before capability v3: a single request, a renewal and a batch alike.
  • #693 b0a4f0e Thanks @PuruVJ! - region(C, props, { version }) in @ogygia/core: when two answers for the same held region reach the browser (two commands that both return it), the one with the newer data version stays on screen, whichever arrived last.
  • #1908 f725fef Thanks @PuruVJ! - A new client hook, reloadNeeded({ url, error, regions }), fires once per page when a chunk can load only after a reload, at the same moment the page says chunk_reload_needed. This happens when a download it needs failed (a dropped connection mid-load) and the browser keeps that failure for the page's life. regions are the regions whose own file the chunk is, so an app can offer the reload. A page with no subscriber carries none of its code.
  • #711 41f5eec Thanks @PuruVJ! - breaking: a remote function's argument sent from the browser must be plain data. The server now refuses an argument that holds an ogygia value (a region, a snippet, a function, a wired class instance, a store or a derived store) with a 400 and remote_arg_not_data, and runs nothing. Values the server sends to the browser are unchanged.
  • #528 9201d45 Thanks @PuruVJ! - - @ogygia/core, ogygia: breaking: the internal internal/compiler-browser and internal/compiler-browser-full import paths are gone. The compiler runs in Node only; use @ogygia/core/internal/compiler there. - @ogygia/cli: breaking: the ogygia mcp server no longer has the ogygia_observatory tool; the Observatory it linked to is gone. - @ogygia/content: its macros and markdown pipeline read the compiler through @ogygia/core/internal/compiler and Node's own fs, path and crypto.
  • #1707 b20ae04 Thanks @PuruVJ! - - breaking: an app's own pass over the HTML ogygia sends is the new @ogygia/rewrite package. ogygia.handle({ transform }) now throws handle_transform_moved; list rewrite() (from @ogygia/rewrite/vite, no options) beside ogygia(), and put a rewrite() handle before ogygia.handle() in sequence(). ogygia/markup is removed, and scanRegions / liftRegions / restoreRegions leave ogygia/server. - @ogygia/rewrite: rewrite({ match, render }) renders only the outermost custom elements match picks (a tag prefix, a list of tags, or a test), in one render(elements, ctx) call per chunk of the page and per region answer, so a streamed page keeps streaming and its later chunks are rendered too. - @ogygia/rewrite: each element render gets has ogygia's marks numbered from 0, so a cache can key on its bytes; equal elements in one call are rendered once. - @ogygia/rewrite: ctx carries kind, csr, url, event and signal, an AbortSignal that fires when the request is cancelled. - @ogygia/rewrite: a render's sheets go out once per key per response, into the head while it is open and inline before the first element that needs them after. - @ogygia/rewrite: a failed batch is retried one element at a time; an element that still fails, drops ogygia's marks, or returns HTML that does not close what it opens goes out as ogygia rendered it, with a warning in every build (rewrite_element_failed, rewrite_marks_lost), never thrown. - @ogygia/rewrite: an element split across streamed chunks goes out unrendered, said in dev (rewrite_element_split). - @ogygia/rewrite: several rewrites in sequence() run in order on one marking of the HTML; one listed after ogygia.handle() throws rewrite_after_ogygia, and a rewrite without the plugin throws rewrite_plugin_missing. - @ogygia/rewrite: rewrite({ page }) rewrites the whole document (held until its last chunk) or region answer, says rewrite_page_failed when it throws (thrown in dev), and has .html(str) for a plain string. - @ogygia/rewrite: .check(html, { kind, csr }) runs the whole round trip on one piece of markup for a test, listing failures and, with a DOM, every restored element that differs from Svelte's. - @ogygia/rewrite: a page where nothing was restored ships no restorer, and each streamed chunk that restored something ends with one short restore call. - @ogygia/devtools: the profiler reads a page's regions itself and no longer depends on @ogygia/rewrite.
  • #516 368b1da Thanks @PuruVJ! - - @ogygia/core, ogygia: breaking: SharedState is no longer exported from ogygia or @ogygia/core. Import it from @ogygia/federation/shared instead; it works the same. - @ogygia/federation: SharedState (state shared across separate builds on one page) is exported from @ogygia/federation/shared.
  • #1688 0602ba2 Thanks @PuruVJ! - The build no longer appends a registration call after each exported createContext(...), and the no-op __tag_context it called is gone from ogygia and ogygia/internal: a module that exports only contexts is left exactly as written. Rebuild any package that shipped already-transformed output.
  • #1842 b6b930e Thanks @PuruVJ! - These methods are now typed as function properties, so passing one on by itself (const { handle } = router) type-checks under unbound-method; none of them used this. A method type was bivariant in its parameters and a function property is checked strictly, so code that assigned a narrower function to one of them may now need its parameter types widened. The changed types: ogygiaTransport.Region.encode / .decode and the ref entry's encode / decode (@ogygia/core), CapabilitySigner.sign / .verify (@ogygia/core), Router.handle (@ogygia/router), Signer.sign / .verify and Staging.discard (@ogygia/machine).

Patch Changes

  • #1848 558b9a9 Thanks @PuruVJ! - On SvelteKit 3, a value of a custom transport type now ships in the page seed, the remote seed and a remote call's page facts; before, each dropped it, because ogygia read the transport from Kit's private request state, which Kit 3 no longer keeps it on.
  • #1387 d16b921 Thanks @PuruVJ! - An island whose hydration changed only attributes is read as the browser reads its tags: a > inside a quoted value no longer cuts the tag, values in any quoting with spaces around = and names in any case are compared, and the first of two same-name attributes is the one kept.
  • #1121 d61549f Thanks @PuruVJ! - @ogygia/core: Tag and attribute names read from server HTML are lower-cased the way a browser does it, ASCII letters only, so data-Äsrc and data-äsrc count as two attributes. @ogygia/federation: A peer tag with two attributes whose names differ only past ASCII (data-Äsrc, data-äsrc) now has each value pinned in its own attribute. Before, the first value was written into the second.
  • #1845 c61a561 Thanks @PuruVJ! - A wake: 'load' island whose background start throws is reported (machine_queue_start_failed, then the error to the page's error handler), and the starts queued behind it still run in the same background task instead of waiting for another.
  • #1841 6e90f0c Thanks @PuruVJ! - A held region the server baked with its stylesheet keeps its styles when it repaints with the same sheet (an island that reads the region's query again once it hydrates): the answer's sheet is now linked in the head whenever the head has none, not skipped because the old copy inside the region was still there.
  • #509 936654e Thanks @PuruVJ! - - @ogygia/core: the dock's island-barrel finding says why barrels() left the barrel (it runs code of its own, it is a package the plugin does not list, an import of it marks a region, and so on) with the fix for that reason, and names barrels() from @ogygia/barrels when the app does not list it. - @ogygia/devtools: the profiler's island-barrel warning quotes the same reason, recorded by the build, and its fix names barrels() instead of the removed ogygia({ barrels }).
  • #1161 8644a71 Thanks @PuruVJ! - A hole batch called off while its body is still arriving (two quick link clicks), or whose body breaks off, now ends quietly: no more "Uncaught (in promise) AbortError" for error monitors to report. Its holes still fetch on their own.
  • #1216 0b97707 Thanks @PuruVJ! - Holes fetched in one batch (a client-side navigation) mint their slot ids with their own region id, as a hole fetched on its own does. They shared one unprefixed sequence, so a slotted island in a batched hole could take the page's own slot id and adopt the wrong children.
  • #1695 3faef3d Thanks @PuruVJ! - In dev and rules builds, a batch of holes where one hole skips its page's data and another asks for it no longer breaks rule_hole_page_read_unpredicted when the page's data could not be looked up.
  • #679 79f67f7 Thanks @PuruVJ! - A batch's answer for a hole that lands after a newer refresh of it no longer paints its older HTML over the refresh.
  • #918 b9af6be Thanks @PuruVJ! - Holes that start together are batched only with region calls of their own endpoint path; a plugin's hole (a deferred peer widget) goes on its own instead of being posted to the wrong endpoint and refused.
  • #717 bf92b58 Thanks @PuruVJ! - A batch of holes is charged to the visitor's render budget once per hole it renders, after that hole's capability verifies, the same as each hole's own request; one call asked twice in a batch renders once. A hole over budget is left out of the batch and fetches on its own.
  • #1451 032d21f Thanks @PuruVJ! - A request body that breaks off mid-upload is a 400 on the profiler's login and on the federation routes (the exposed table, a thaw notice), not a thrown error and a 500.
  • #442 95ed95c Thanks @PuruVJ! - say() in @ogygia/machine says a thing once per key until it recovers, remembering at most 1024 keys; a machine's warn-once and a plugin's warn use it, so a long-lived server no longer keeps every distinct warning text.
  • #1114 36de4b8 Thanks @PuruVJ! - A region capability's exp and ttl are accepted only as ogygia mints them (plain digits, no leading zero) and refused as shape before the signature check otherwise (before, any spelling of the same expiry, such as +n, 0n, n.0 or 0x…, verified, so one capability had many URLs).
  • #926 9caa92e Thanks @PuruVJ! - A server island's address is a path from the app's root (/__ogygia__?…, under paths.base when set), never relative to the page, so it still works in HTML that moves to another page or app under Kit's default paths.relative.
  • #1095 b3f4d94 Thanks @PuruVJ! - The region batch endpoint and federation's routes stop reading a request body once it passes their size cap, also when it is sent without a content-length (before, such a body was read whole, then refused).
  • #1176 25db3c9 Thanks @PuruVJ! - A plugin whose browser boot throws no longer stops the runtime's boot: it is reported once (client_hook_failed, hook boot), the other plugins still boot, and the page's regions still wake.
  • #730 f7ffd0e Thanks @PuruVJ! - A build now fails with secret_in_client_chunk when a client chunk or asset holds a signing secret (OGYGIA_SECRET, or the build's own key) or a server module that signs region addresses.
  • #1368 574999e Thanks @PuruVJ! - A runtime script the page emits loses every code-origins attribute it carried, however it is written (single quotes, no quotes, spaces around =, twice), so the origins the render learned are the ones the browser reads.
  • #986 d460c55 Thanks @PuruVJ! - @ogygia/core: in dev, a region's style module is imported only from the page's code origins, and a dropped download is asked for again only there, the same check an island's own code load uses (#981).
  • #985 9459fff Thanks @PuruVJ! - A stylesheet an island's code put in the head as it loaded (the bundler adds the CSS the island's chunks need, as on a mounted peer page) leaves with the page after a router navigation, as a fresh load of the next page has none, and comes back with a page whose island runs that code again.
  • #1403 891228b Thanks @PuruVJ! - A hydration mismatch report drops a comment where the browser ends it (--!>, <!-->), and keeps a <!-- inside a script or a quoted value.
  • #1278 925cf79 Thanks @PuruVJ! - componentCssHead no longer links every sheet again when a request asks for the same components a third time.
  • #1541 1a475de Thanks @PuruVJ! - A context that cannot cross into regions is now said, not dropped silently: a one-off Symbol() key (context_key_one_off) or a function value (context_value_function) set with setContext from ogygia or in a <Provide> warns in dev, naming the key and what to use instead; the build warns on a one-off Symbol() key it can see (region_context_key_one_off), and its "island code reads a context nothing bridges" warning now covers Symbol.for(name) keys.
  • #1541 1a475de Thanks @PuruVJ! - A Symbol.for(name) context key, set with setContext from ogygia or in a <Provide>'s values, now reaches regions in the browser: it crosses by its name. Before, the drop-in setContext left it out and a <Provide> holding one failed to render.
  • #474 e891f09 Thanks @PuruVJ! - Render deadlines, the region endpoint's rate-limit windows, a lake's maxAge and the page-asset budget are now measured on the monotonic clock, so a wall-clock step (an NTP correction, a VM resume) no longer shortens or stretches them.
  • #1887 2fdd64b Thanks @PuruVJ! - Region's generated .svelte.d.ts no longer names RegionValue, Snippet and Component without importing them, so it type-checks with skipLibCheck off; its props are unchanged.
  • #1483 25c95f5 Thanks @PuruVJ! - A hole answer redirected to another origin is refused like a same-origin redirect: no retries, and dev says region_answer_redirected with the URL that answered.
  • #852 a3ca2ad Thanks @PuruVJ! - A client navigation to a page with more copies of an island than the current page shows live now gets the extra copies rendered by the server, instead of empty placeholders the browser had to fill.
  • #1618 80f4d91 Thanks @PuruVJ! - With serverDelta on, a page the router kept (a soft refresh's, a prefetch's) is reused only by a document that still shows the regions its fetch left out: going back to a page after a soft refresh on it no longer brings its regions in empty and fails to hydrate them.
  • #1460 3ddf36b Thanks @PuruVJ! - In dev, a route group whose name holds a quote mark or an ampersand gets its edited stylesheets live again: the dev-scope meta now escapes the name instead of dropping its quotes.
  • #1966 c22268b Thanks @PuruVJ! - A build that ships devtools events on every page (a plugin's events() without lazy) now marks each page cache-control: private, no-store, so a shared cache can't keep one visitor's server events and serve them to another.
  • #882 724b0f3 Thanks @PuruVJ! - Devtools builds: the devtools stream takes server events only from the response's own side channel, not from one the page's markup carries.
  • #880 5373f25 Thanks @PuruVJ! - On a devtools build, only well-formed server events from the page's devtools side channel enter the event stream, and ingest() (a saved trace, another realm) takes only well-formed events of either realm; anything else is left out.
  • #1555 65733b6 Thanks @PuruVJ! - The check for edits to a sleeping island now watches only the islands still asleep, not the whole document, so DOM changes elsewhere on a large page (a framework hydrating it, web components rendering) no longer run the runtime's code.
  • #594 0a40057 Thanks @PuruVJ! - @ogygia/core: a click made while an island is starting goes to the island alone; the page's own click listeners hear it once, as the replay when the island is live (late, and with isTrusted false), not at the press and then again at the replay.
  • #505 abc4a42 Thanks @PuruVJ! - In dev, a file added next to a barrel that already re-exported it is now picked up by the barrels pass and the CSS walk, without restarting the dev server.
  • #1190 1bc6577 Thanks @PuruVJ! - A whole-body swap navigation keeps the objects the next page's seed revived: an island that decodes the same object as page.data gets that object, not a fresh copy.
  • #1348 e0b4429 Thanks @PuruVJ! - An og.$ factory whose code holds </script or <!-- no longer breaks the page in a build: the script that registers the factories keeps it inside its tag.
  • #705 79e5bfa Thanks @PuruVJ! - An import.meta.og.$ function now travels as its build tag and captures only, never its source: a side whose build lacks the tag refuses it with fn_revive_missing instead of rebuilding it from the payload.
  • #2023 00a7bc4 Thanks @PuruVJ! - A peer's live region or kept island, mounted in a shell, is hydrated by the peer's own build, and its next tick or page's props reach it in place (a peer on an older build is hydrated again instead).
  • #1970 f9ebb02 Thanks @PuruVJ! - An island from a mounted peer page now reads the cross-island context its page provides (<Provide>, setContext, createContext), even when the shell provides no context of its own. Before, a production shell left the context bridge out and never handed context to a peer's island, so the island hydrated with its context silently empty. A federated build now also ships the live-region feature a peer's held or kept regions need.
  • #1338 0a4a20e Thanks @PuruVJ! - A form value kept across a navigation goes back into the island it was typed in, found by its component and which copy of it it is, even when the page now has other islands in front of it.
  • #1172 c9e4346 Thanks @PuruVJ! - A router link whose hash is a bad percent escape (#%E0) no longer breaks the navigation after the swap: the router finds the hash target as the browser does (the hash as written first, then decoded, never throwing), so after hooks and og:page-load run and the router goes idle.
  • #916 daa8d5c Thanks @PuruVJ! - A hole's frame address now names the whole call it asks (the endpoint path and every parameter but the capability's own), so two plugin holes alike but for their props, like two deferred peer widgets, no longer share one answer, on one page or across a navigation.
  • #1029 40b91ab Thanks @PuruVJ! - @ogygia/machine: A cache() set of the value its key already holds keeps it (no 'delete' notice, so an onEvict cleanup no longer runs on a value still held), set takes its own keep, and a keyed flights of one field keys by that field's value with no string built. @ogygia/core: A region answer written to the frame store costs about a third fewer steps (one cache write, no lookup before it), and an island warm reads its chunk graph once.
  • #1353 fc49f63 Thanks @PuruVJ! - goto() returns a rejected promise for a URL it refuses (not http, another origin without external, unparsable) instead of throwing, as Kit's goto does: goto(x).catch(...) now sees it. A try { goto(x) } catch without await no longer catches it.
  • #1002 13e08a2 Thanks @PuruVJ! - @ogygia/core: an island's graph preload no longer adds a second <link rel="modulepreload"> for a chunk that another loader (such as Vite's preload helper) linked after the first island started. It now checks the document's links each time it preloads.
  • #1457 620d27e Thanks @PuruVJ! - The head's end is found as the browser reads it: an app.html that writes </HEAD> gets ogygia's head injections, and a </head> inside a head script's text (a JSON-LD string) no longer takes them into the script. The body's end is found in any case.
  • #825 6f03b81 Thanks @PuruVJ! - A client navigation to a page at another URL depth no longer adds a second copy of a head tag (the ogygia runtime script, a stylesheet) that the first page wrote with a page-relative URL.
  • #576 7be0138 Thanks @PuruVJ! - The head's duplicate-link pass reads each <link> attribute as HTML does, so a stylesheet or preload hint whose URL has an apostrophe is no longer dropped, and data-rel / data-href no longer count as rel / href.
  • #997 f018ab4 Thanks @PuruVJ! - @ogygia/core: the server's head checks, link dedupe and runtime placement, and the router's prefetch warm read a page the way the browser does: a tag written inside a comment or inside a script's, title's or textarea's text no longer counts, so the runtime is never moved into a commented-out script or a title, a real stylesheet is never dropped as a copy of a commented one, and text that looks like a region no longer makes the router import a module.
  • #826 715744f Thanks @PuruVJ! - A client navigation that keeps a region (a refresh in place, or a link to a page with the same region) now keeps the head tags that region's inner islands wrote, such as the ogygia-kit-island stamp and their stylesheets; each such tag names its owning region in a data-og-owner attribute.
  • #946 b54c1bd Thanks @PuruVJ! - A held region awaited inside another held region's island no longer stays empty when the island re-creates it in the browser: the fresh region paints its value.
  • #1211 c52057f Thanks @PuruVJ! - A held region rendered in a load or by a remote call during the page render no longer mints slot ids the page's own regions also use, and no longer skips more copies on a server-delta navigation than the browser has live.
  • #905 07c4c5d Thanks @PuruVJ! - A server island (render: 'deferred') inside a held region that wakes now shows: the region's HTML is rendered the way its component hydrates, so the server island renders inline as it does inside any island, instead of an empty element that was never fetched.
  • #1252 527fb37 Thanks @PuruVJ! - A page that awaits a held region with an island inside ships the runtime script again with the router off: the island in the held region's own render no longer takes the page's one runtime claim.
  • #1089 c4a1b4a Thanks @PuruVJ! - A router navigation from a styled held region to an unstyled one in the same place no longer keeps the first region's <link data-ogygia-region-css> inside the second: a region's sheet counts as render output in the morph.
  • #440 4a038b4 Thanks @PuruVJ! - A cached hole (maxAge) that reads a flag, or a cookie, header or locals value, for an anonymous visitor is no longer kept and served to other visitors.
  • #830 d5a120a Thanks @PuruVJ! - On a Kit-hydrated page, a deferred region whose props hold a shared object (a wired class instance, a store) now has the same identity in the browser as on the server, so a region Kit mounts afresh finds its server-minted address and loads.
  • #952 7e9f615 Thanks @PuruVJ! - A server island inside a server island that sits in an island no longer waits for that island to wake: it fetches and shows on its own schedule, even when the island waits for a press.
  • #1767 f7e0684 Thanks @PuruVJ! - @ogygia/core: a deferred region refused with sig, shape or foreign-key (a server of another build or key, as in a rolling deploy from 0.12.x) asks once more after half a second, so a load balancer can route it to a server of the page's own build; if that is refused too, region_answer_denied says so and the fallback stands.
  • #1032 4c732c6 Thanks @PuruVJ! - A hole with maxAge whose render reads page.data or calls a remote query is kept in the server's render cache again: the page it renders for is part of its key, not a read about the visitor.
  • #680 f8a4fbf Thanks @PuruVJ! - A hole that a region refresh gives new props while its first fetch is still out now fetches and shows the new answer, instead of keeping the old props' answer.
  • #967 8ef4954 Thanks @PuruVJ! - A deferred region the endpoint rate-limited no longer gives up for good: the endpoint's 429 now carries Retry-After (the time left in the visitor's window), and the region asks again after it (at most a minute) instead of spending its tries inside the window.
  • #1210 a365b26 Thanks @PuruVJ! - A hole whose server render throws is now said in production too (region_render_failed, with the error, in the server's log). It was said only in dev, so a hole that failed only in production answered 500 with nothing logged. The visitor's answer is unchanged: an opaque 500.
  • #897 226364d Thanks @PuruVJ! - A deferred region whose fetch fails while the browser is offline, or an island whose code fails to download then, now tries again once the browser is back online instead of giving up for the life of the page; a region that finally gives up says region_fetch_failed in production too.
  • #446 37a9eaf Thanks @PuruVJ! - A hole whose prefetch warm still waits for a background turn fetches at once when it wakes on screen, the visitor reaches for it, or preload() asks for it, instead of waiting behind the page's other prefetches.
  • #855 db021f1 Thanks @PuruVJ! - @ogygia/core: island code loads only from the page's origin, the runtime's own, and the origins the server names on the runtime's script (a federation peer's); an entry or src anywhere else is refused with island_code_refused, and a region's src re-points only its own island's built file (#851).
  • #1203 2378a3c Thanks @PuruVJ! - A production server that cannot find or read the client build's handoff (og-region-deps.json) now says so (island_deps_handoff_missing, with the paths it tried) instead of rendering every hole without its CSS and preloads in silence. A handoff that failed to read or parse is tried again on the next request instead of being replaced by an empty one for the life of the process.
  • #838 b823bff Thanks @PuruVJ! - @ogygia/core: the island graph keeps every entry whatever its name; one named __proto__ was lost on the way to the page (#994).
  • #1119 4c64ac7 Thanks @PuruVJ! - On a csr=false page, an island's <svelte:head> content stands in <head> where the server wrote it, whatever order the islands wake in, so two islands' head styles that set one property no longer swap winners from one load to the next.
  • #1125 17834e0 Thanks @PuruVJ! - A <style> written over several lines in an island's <svelte:head> is one copy once the island wakes: the page's server copy is retired, as it is for single-line head content.
  • #1924 7929876 Thanks @PuruVJ! - An island whose code failed to load during a short outage wakes once the connection is back. It used to look up the build map first, and if the connection came back during that lookup, the island ended as failed until the page reloaded.
  • #1309 3fde46a Thanks @PuruVJ! - The islands endpoint is decided once per server, by the first handle() (or the first render when none named one), and never moves: a later handle() naming another one, from a second copy of ogygia too, is islands_endpoint_conflict (thrown in dev, said in production) and the first path stays, so the pages already minted and the handle that answers them never name two paths and holes no longer come back empty.
  • #1197 115137c Thanks @PuruVJ! - The islands endpoint answers on its one path under the app's base, the path every capability is minted for: with handle({ endpoint: '/api' }), a page at /docs/api is a page again, not taken for a hole render. A second handle() naming another endpoint in one production server is now said (islands_endpoint_conflict) instead of silently replacing the first.
  • #1086 9f87204 Thanks @PuruVJ! - A head link the router keeps across a client navigation to a deeper or shallower path still names its file: the router reads each page-relative head URL (Kit's default ../_app/...) against the address its page wrote it for and leaves loaded links as they are; only a parked (disabled) sheet, not fetched yet, is made root-relative before the address moves.
  • #1088 59495f6 Thanks @PuruVJ! - A region kept across a client navigation (keep: 'name') now carries the next page's data-og-fp along with its props, so its props sidecar is found and the router lists the islands the page really holds.
  • #841 99e9496 Thanks @PuruVJ! - An island waiting for SvelteKit on a csr=true page no longer waits forever when Kit's own client files fail to download: it fails, and the page says kit_boot_failed once.
  • #2015 19f3a73 Thanks @PuruVJ! - An island waiting for Kit's page on a Kit document now ends its wait with kit_boot_failed when one of the page's own Kit files (a route node) fails to load, not only Kit's entry files: it no longer waits forever.
  • #841 99e9496 Thanks @PuruVJ! - An island waiting for SvelteKit no longer imports a file named by a boot-shaped inline script that came in as markup: only files on the page's or the runtime's origin are imported.
  • #1748 74a5864 Thanks @PuruVJ! - On an app with no router, a page that shows a mounted peer page's islands (a mount.kit catchall) loads the runtime, so those islands wake: no runtime was shipped when the page rendered no region of its own.
  • #1747 bf5db5d Thanks @PuruVJ! - A Kit page's runtime script names the code origins its render learned (a mounted peer page whose runtime is served from another origin): they were dropped, because Kit runs the page transform outside its request store.
  • #1856 a878cae Thanks @PuruVJ! - In dev, a csr=true page whose SvelteKit start script ogygia cannot hold until its runtime booted now warns (kit_start_ungated) instead of letting Kit start first without a word.
  • #1711 a44b2c4 Thanks @PuruVJ! - On a csr=true page with regions, Kit now starts only after ogygia's runtime is ready, so lakes keep their content when Kit remounts the page; before, a fast Kit start could leave every lake empty. Kit still starts if the runtime fails to load, and a hash-based CSP gets the hash of Kit's changed start script.
  • #892 4d7af4c Thanks @PuruVJ! - The server takes an SPA nav's live-copy header over the size the router ever sends as no claim, and renders every region.
  • #1566 c7c1514 Thanks @PuruVJ! - Two lakes of the same component with different props each keep their own content when Kit remounts a csr=true page; before, the second showed the first one's HTML and lost its own islands.
  • #1229 e2ea18d Thanks @PuruVJ! - In dev, an island whose hydrate renders a different number of lakes than its server HTML had says so (rule_lake_restored) instead of dropping a lake's content silently.
  • #1443 94f89d5 Thanks @PuruVJ! - A lake whose host island puts its content back is settled at once when a region inside it waited: a later refresh of that lake no longer re-enters its regions as if they still waited.
  • #1692 a8c1cb4 Thanks @PuruVJ! - An island's hydrate no longer moves its lakes out and back: a custom element in a lake stays connected through the hydrate, and what its own runtime did to its light DOM is no longer taken for drift.
  • #1364 33dc452 Thanks @PuruVJ! - A streamed page's late chunk swaps into its slot when one of its sheet hrefs or its slot id holds a quote or a backslash; before, it stayed out, or its sheet was added twice.
  • #1889 81e1725 Thanks @PuruVJ! - An island a client navigation loads late no longer reports island_load_failed when its load fails after the island was already taken off the page.
  • #594 0a40057 Thanks @PuruVJ! - A lazy chunk whose download failed is asked for again in Safari too, and in Firefox a chunk whose dependency failed is no longer retried as that dependency (which ran a second copy of it and broke the wake): the build hands each lazy loader its own file.
  • #595 98730f8 Thanks @PuruVJ! - A lazy chunk's failed retry fails its caller at once, and a use that comes before the runtime knows why it failed waits for that answer instead of failing with it (in Safari, a click right after a failed prefetch now navigates in place).
  • #2039 e55454d Thanks @PuruVJ! - A remote query refreshed by an island's own handler after the island left the page (a click awaiting a command, then a navigation) is a no-op instead of Kit's "No cached query found" error; the next page still reads that query fresh.
  • #782 bab2aff Thanks @PuruVJ! - A static live region put back on the page after a minute away keeps the newest answer it showed, instead of repainting its last tick over it.
  • #823 6bd663c Thanks @PuruVJ! - A live query in an island now keeps updating after a client navigation that keeps the island; the navigation releases only the query instances that departed islands held.
  • #857 c19ba92 Thanks @PuruVJ! - A live query that a kept island reads only from a component it mounts later keeps running after a client navigation in which another island that read it leaves.
  • #943 08e5c16 Thanks @PuruVJ! - A live region whose island file cannot load stops trying on every tick: it says island_load_failed once, shows each later tick's server HTML, and no longer throws the import's error at the page or asks the server about the file again.
  • #683 0e4f3a8 Thanks @PuruVJ! - A static live region no longer paints a tick over a newer update of the same region (a command that returned it) that landed while the tick was on its way, nor a tick whose data version is older than the one on screen.
  • #491 1e96c8c Thanks @PuruVJ! - Two builds of the same code write the same og-locations map under the same name, so a deploy with no island change no longer busts its cache.
  • #878 08fd293 Thanks @PuruVJ! - A hole answer's region URLs, island graph and region CSS are read as a browser reads the tags: a region or sheet inside an HTML comment is left alone, and upper-case tags, single-quoted values and a quoted > no longer hide one.
  • #1116 9f7eac5 Thanks @PuruVJ! - @ogygia/core: Reading tags out of server HTML (the head dedupe, region CSS, hole answers, seed injection, stitching) costs 2 to 53% fewer steps: each tag is read once, a character at a time. @ogygia/federation: Lifting a peer page and pinning its asset refs costs about half the steps: one walk, each tag's attributes read once.
  • #999 97d59ed Thanks @PuruVJ! - @ogygia/core: holes that read page.data show the data of the page a router navigation leads to, not of the page it left. The navigation's hole batch now names its destination as its referrer.
  • #999 97d59ed Thanks @PuruVJ! - @ogygia/core: a router navigation groups the next page's deferred holes by endpoint, as the first load does. A peer widget's hole no longer sends the whole batch to its own path, which answered 403, and no region call is sent to an endpoint that does not know it.
  • #1048 f848e22 Thanks @PuruVJ! - A page reached by a client navigation loads island code from the code origins its own response names (a federation peer's CDN), instead of refusing them until a full reload.
  • #1963 2bd2d0a Thanks @PuruVJ! - The devtools now say opt-out when a navigation swaps the whole page because the page opted out of the in-place update with data-og-no-reconcile. It used to say shadow-region.
  • #797 69c3a26 Thanks @PuruVJ! - After a client navigation, the next page's head nodes (its <style> and stylesheet <link> among them) sit in the order a fresh load has them, after the app's global styles, so the cascade is the same however the page was reached.
  • #785 1e21a17 Thanks @PuruVJ! - A client navigation to a page with no <title> no longer leaves an empty <title> in the head; the page matches a fresh load of it.
  • #1453 16b6c56 Thanks @PuruVJ! - An island nested beside an {@html} that a third-party script edits before the islands wake is put back from the server markup at the wake, instead of the outer island throwing its hydration away.
  • #1522 9299656 Thanks @PuruVJ! - Dev no longer warns that a nested island's schedule is ignored when it is the same schedule as the island around it (a wake: 'load' island inside a wake: 'load' island, such as one rendered in a mobile menu sheet).
  • #1214 ecd3b32 Thanks @PuruVJ! - data-og-no-reconcile on <body> itself now opts the page out of the router's in-place reconcile, as it does on any element inside the body.
  • #485 ee4cebc Thanks @PuruVJ! - import.meta.og.bake addresses each evaluated bundle by a 64-bit hash of its inputs (was 32-bit), so two modules can no longer share a cached bake by collision.
  • #719 f878494 Thanks @PuruVJ! - ogygia.files checks that each declared path stays inside its package by the path the file really has, so a symlink in the package that leads out of it is refused (package_files_escapes) or left out of a glob.
  • #577 13aa062 Thanks @PuruVJ! - A $page.data promise nested more than 65 levels deep, or inside a cyclic value, now streams into regions like any other: before, it was left in the seed, the page failed to serialize it, and a rejection went unhandled.
  • #577 13aa062 Thanks @PuruVJ! - On a router (non-navigate) request, $page.data with promises keeps its key order in the seed; before, keys came in the order their values settled.
  • #1436 8501aa3 Thanks @PuruVJ! - A streamed page.data promise read again after its value arrived (two regions sharing it, a lazily woken island) is the same settled promise, no longer rejected as page_promise_unresolved.
  • #1627 b43988f Thanks @PuruVJ! - A hole or remote call rendering for a page whose data answer breaks before its first line now renders without the page's facts, as for any other failed look-up, instead of failing.
  • #1000 a29b558 Thanks @PuruVJ! - @ogygia/core: a hole or remote-rendered region that reads page.data always renders with the facts its page look-up returned. Before, it could silently render with an empty page.data when the look-up's answer was not kept.
  • #1768 45632dd Thanks @PuruVJ! - @ogygia/core: the page.data keys a deferred region's answer brings are no longer lost when an island that woke before the answer hydrates first: they wait for devalue to load, then join the page, so islands inside the region read them.
  • #1190 1bc6577 Thanks @PuruVJ! - A region that reunites with an object another region decoded now owns it too, so a navigation that removes the first region no longer releases the object the kept one still shows.
  • #1190 1bc6577 Thanks @PuruVJ! - A client navigation releases the page objects nothing on the next page holds (a seed's values, a decode outside any region), so the hub no longer grows with every page visited in the tab.
  • #1302 0845054 Thanks @PuruVJ! - Dev now says page_payload_unreadable, with the error, when the browser cannot read back data the server wrote for islands (the page seed, page facts, the holes record, the context marker, remote functions' data). Islands used to go on without it and nothing was said; the usual cause is a custom type the server's transport encodes with no decoder in the browser.
  • #1327 239e0e7 Thanks @PuruVJ! - A streamed load promise that never settles no longer holds the server's response open after the visitor leaves: the wait ends with the request and the response closes. A region rendered outside its page now gets a rejected promise (page_promise_unresolved) instead of one that stays pending when Kit's data answer ends without its value. Dev warns (page_promise_pending) when a streamed promise is still pending after 10 s.
  • #1318 295b9a8 Thanks @PuruVJ! - A streamed page.data promise in an island no longer waits forever when its value can no longer come: once the page has loaded with no value for it, or its value came but the code to read it never downloaded, it is rejected with page_promise_unresolved and {#await} shows its catch branch.
  • #1133 8686f2e Thanks @PuruVJ! - A region that leaves the page while its answer waits on its stylesheet no longer stays "painting" for good: its paint ends with the region. In dev and in OGYGIA_RULES=1 builds, a new rule rule_region_left_busy reports a region that left the page with one of its machines still mid-work.
  • #838 b823bff Thanks @PuruVJ! - @ogygia/core: the batch stream reader skips any number of malformed parcel openings in a loop, instead of running out of stack.
  • #912 4cfe3ea Thanks @PuruVJ! - A federated app's production runtime now ships what a peer's regions need (the frame store, morph, lakes, wakes), so a peer's render: 'deferred' widget loads in an app with no deferred region of its own.
  • #958 9e1480b Thanks @PuruVJ! - A peer's island (fragment federation) whose code download fails once is asked for again under a fresh URL, like the app's own islands, instead of never loading. A retry goes only to the origin the island's file was first asked from.
  • #1012 26f7e95 Thanks @PuruVJ! - A deferred peer region (and any plugin capability) names the key that signed it, as a region hole does: a server of another deployment (a rolling deploy without one shared OGYGIA_SECRET) refuses it as foreign-key, with the advice that goes with it, instead of as a bad signature.
  • #1819 dcecc57 Thanks @PuruVJ! - A plugin's handle, and a transformPageChunk passed to resolve() or a plugin's next(), are called on their own object, so one written as a method can use this.
  • #1470 a13ad32 Thanks @PuruVJ! - A plugin's signed hole (federation's /og/frag) now pays the visitor's region rate budgets as a region hole does: the probe budget before the signature check, the render budget after. A federation hole can now answer 429 with Retry-After under load.
  • #1359 5ff44f8 Thanks @PuruVJ! - In dev, a plugin's signed hole (a deferred federation widget) no longer answers 429 after the server hooks module runs a second time.
  • #802 19fa62d Thanks @PuruVJ! - core: a plugin's app.sign, app.verify and app.capability sign in the plugin's own domain (its name, length-prefixed), so nothing a plugin signs checks as a region link or as another plugin's, dotted names included; plugin capability links minted before the upgrade are refused once and fall back like any refused hole
  • #747 771fa53 Thanks @PuruVJ! - @ogygia/postrender: Breaking: a page rendered for a request that carries a cookie or an authorization header is not stored (it is still served a stored copy, and its own render is stamped private, no-store); a route whose pages are the same with them opts in with config = { postrender: 'with-credentials' }. @ogygia/core: a render's per-visitor reads also count a function in locals, in and the keys of locals, the request headers read whole or copied while one is personal, headers.has() and a request clone(), client address, forwarded host, location and session headers, getClientAddress(), per-request platform data, and an own-origin fetch that carries the visitor's cookies.
  • #443 8b120e2 Thanks @PuruVJ! - An island's code that a page prefetch started downloading at low priority is raised when the island wakes on screen or the visitor reaches for it, and a hover no longer waits behind the prefetch it repeats.
  • #712 5320d28 Thanks @PuruVJ! - preload(region) sends no request when the region's address is another origin; every fetch of a hole now checks its endpoint is this origin before it goes out.
  • #760 90a7449 Thanks @PuruVJ! - devtools: in production the profiler accepts only a secret of at least 16 bytes; a shorter one keeps its pages closed and says so (devtools_profiler_secret_short) devtools: the profiler allows ten wrong keys per address in 15 minutes (the login form, x-profiler-key and x-profile share the count), then answers 429 until the window passes devtools: a profiler login is a random session id the server signs; it expires after 12 hours, logout ends it, and any change to it is refused (everyone logs in once again after the upgrade) devtools: the profiler's beacon flag cookie belongs to one login: it ends when that session expires or logs out
  • #1964 733aa1c Thanks @PuruVJ! - The profiler now names seed references as the reason an island's props went to devalue when the props themselves were plain JSON. It used to show no reason at all.
  • #1507 9762036 Thanks @PuruVJ! - A hole whose island module throws as it loads, or whose props do not decode, is said in the server's log in production too (endpoint_props_decode_failed), not only in dev. The visitor's 403 stays opaque.
  • #594 0a40057 Thanks @PuruVJ! - A click on an island that goes live while its wake is still ending acts once: the click queued for the replay no longer also reaches the island's handlers.
  • #1301 cb0633e Thanks @PuruVJ! - Past the region endpoint's rate-limit cap, an address whose window already ended is let go first: a visitor who spent their budget in a window still open no longer gets a fresh one early.
  • #1269 94f10fe Thanks @PuruVJ! - A visitor whose rate-limit window rolled over counts as recently seen, so under pressure it is no longer the first address let go (and handed a fresh budget).
  • #980 6856e83 Thanks @PuruVJ! - When the region render budget runs out for a private, loopback or link-local client address (a proxy's, shared by every visitor behind it), the server warns once with rate_limit_shared_address.
  • #529 32177c7 Thanks @PuruVJ! - - @ogygia/core: four new runtime hooks for a plugin's browser half: regionWoke, regionMismatched, navStarted and loadStarted; navigated now says whether the regions were reconciled, and holeFailed carries the hole's el. - @ogygia/devtools: the dock's Page, Hydration and Session readers and the testing API read the runtime hooks instead of core's event layer. - @ogygia/insights: a recorded session holds the runtime hook calls (SessionData.hooks, HookEntry) instead of core's events.
  • #829 0767267 Thanks @PuruVJ! - The read set (facts.reads) is a plain shape, so core's built types and a plugin's agree on it.
  • #709 62e47da Thanks @PuruVJ! - A batch of holes is sent only to this origin's endpoint and writes nothing from an answer that ended on another origin, and invalidateAll() merges a refreshed page only when its fetch landed on this origin. Every string the runtime turns into DOM now goes through one module.
  • #714 9c93fb1 Thanks @PuruVJ! - Every region response now says how it may be cached: a keepFallback() answer (204) carries its hole's own policy (no-store, or private, max-age when the hole opted in), and refusals and errors (403, 405, 400, 413, 429, 500) are no-store.
  • #778 9b9f253 Thanks @PuruVJ! - core: region links are signed through capability(), naming the islands endpoint they are for and refusing a lifetime longer than the app ever mints; links stay identical between renders, and links signed before (pages cached before the upgrade) still work and are re-signed in the new form when renewed machine: capability().mintUntil() mints a token that expires at a given time, so tokens without a nonce stay identical across a window the caller picks
  • #1371 1073b6a Thanks @PuruVJ! - A region import mark that would do nothing now fails the build: render: 'static' alone, keep on a hole, lake or live region, and a call-shaped schedule like wake: 'visible(200px)' (a media query is now media words around balanced conditions, everywhere a schedule is read).
  • #780 71ff4c7 Thanks @PuruVJ! - core: a region request (a hole's GET, its renewal, each hole of a batch) walks one state machine, so rendering or charging the render budget before its capability verifies cannot happen
  • #800 a14a348 Thanks @PuruVJ! - A deferred region's stylesheet leaves <head> with the page that used it, instead of one navigation later.
  • #1852 db542a7 Thanks @PuruVJ! - In dev, region.snippet(snippet) now freezes a snippet that writes elements; before, Svelte's dev element check found no component around it and the freeze threw.
  • #2040 411a3eb Thanks @PuruVJ! - A hole given a snippet prop now works in the browser, as it does on the server: created fresh in the browser it freezes the snippet to HTML itself, and hydrated on a csr page it keeps the server's frozen HTML, instead of throwing prop_not_serializable. A top-level island given a snippet prop and created fresh in the browser now freezes the snippet to HTML, as the server does, instead of throwing prop_not_serializable.
  • #2017 f54b0d7 Thanks @PuruVJ! - A region's relative entry, src and endpoint are pinned against the address its document was loaded at: a back taken before the runtime ran no longer points its island code one folder too deep.
  • #1199 fff7b91 Thanks @PuruVJ! - A region whose wake is not a trigger now says so (region_wake_unknown, with the region and the value) as it falls back to waking on load.
  • #608 67127a4 Thanks @PuruVJ! - - @ogygia/core: the runtime no longer carries the restore support for an app's own HTML pass (the restore report, a web component's class tokens through hydration, the answer restore hooks); apps without @ogygia/rewrite boot about 0.15 to 0.2 kB (brotli) smaller. - @ogygia/rewrite: rewrite() ships that support to the browser itself; restore_markup_broken and restore_late are its message codes.
  • #757 a403024 Thanks @PuruVJ! - core: the restorer never puts back an event-handler attribute, a srcdoc or a javascript: URL when it returns a host's attributes to Svelte's
  • #834 725eb10 Thanks @PuruVJ! - When the file of an island nested in another island fails to download once, the retry now asks again for the outer island's own file, so the outer island is no longer replaced by the nested one.
  • #1902 84489df Thanks @PuruVJ! - A page with declarative shadow DOM now works after a router navigation: its web components get their shadow roots, no <template shadowrootmode> is left inert, and its islands hydrate instead of being discarded. A host the navigation keeps (same element at the same place on both pages) keeps its live shadow root; give it a different id or data-key on each page to take the new page's render.
  • #2026 face75c Thanks @PuruVJ! - A Back the visitor takes after a reload, before the router has started, no longer leaves the old page on screen under the new address: the router loads the page the address names.
  • #2025 7582a45 Thanks @PuruVJ! - A context set with createContext's setter (or ogygia's setContext) in a server-router page now reaches the islands on that page. A context set with ogygia's setContext reaches the page's islands when the server loads ogygia's handle module twice (the Vite dev server can), not only on the first request.
  • #447 9807aa5 Thanks @PuruVJ! - A click on a link whose page prefetch still waits for its turn sends that request at high priority, the visitor's, instead of the prefetch's low one.
  • #1022 dd93a29 Thanks @PuruVJ! - @ogygia/core: a router return to a page within a minute shows its deferred regions from the answers already held, instead of asking the server for them again.
  • #859 437e91b Thanks @PuruVJ! - In dev and in OGYGIA_RULES=1 builds, a new rule rule_region_answer_behind reports a deferred region that shows an older answer than the newest one its address holds.
  • #524 9df2941 Thanks @PuruVJ! - - @ogygia/core: a plugin's browser half subscribes to the runtime's moments with defineClient({ hooks: { … } }) (region mounted, hydrated, failed, hole answered, navigated and the rest); a hook no plugin subscribes to is left out of the runtime, and regionMount / regionUnmount move inside hooks. - @ogygia/devtools: the profiler's beacon is part of devtools' browser half, so an app without devtools no longer carries it in its runtime.
  • #1886 1b756bf Thanks @PuruVJ! - html and attr read a URL attribute's scheme the way a browser's URL parser does: a value a browser follows as a relative URL (a space before the colon, as in javascript :x, or a leading non-ASCII space) is kept, not replaced with about:invalid#unsafe; every value a browser would run as javascript:, vbscript: or data: is still refused.
  • #1898 adef9d0 Thanks @PuruVJ! - An island prop that matches a page seed node only up to -0 versus 0, or an empty array slot versus undefined, now crosses as its own copy, so the island gets back exactly what it was given.
  • #718 9ef66e4 Thanks @PuruVJ! - The server honors x-ogygia-known (the regions a router navigation already shows) only when the app turned on router: { serverDelta: true }, and a page then answers with Vary: x-ogygia-spa, x-ogygia-known, so a shared cache never serves a copy with regions left out to a visitor who asked for the whole page.
  • #1201 ae5d636 Thanks @PuruVJ! - The server's request ports (the document tail, the page seed and late-region recorders, the context recorder, the devtools recorder, the request stats sink) are one per process, so a second copy of core in the server bundle reads what the handle installed instead of nothing.
  • #721 a9072b3 Thanks @PuruVJ! - A region answer's server-timing (queue and render time) goes only to dev, a browser that turned devtools on, or the profiler's logged-in user; the profiler's beacon flag cookie now carries a value signed under the profiler secret, and a bare 1 no longer turns it on
  • #827 5becc79 Thanks @PuruVJ! - A client navigation that removes one of two regions sharing one live object (a wired class instance, a store) no longer disposes that object while the other region stays on the page.
  • #990 e5f7368 Thanks @PuruVJ! - @ogygia/core: a stylesheet that islands under two different outer islands share stays in the head after a client navigation while any of those islands is still on the page. Before, it named only the first island and could go while the second still needed it. The page's tail now lists the other owners (<script type="application/json" data-og-owners>), and data-og-owner can name several islands, space-separated.
  • #979 1398f5f Thanks @PuruVJ! - Islands read the page seed, remote seed, page context and holes record only from the server's own response, not from a script of the same type the page's markup carries.
  • #1141 3132e4c Thanks @PuruVJ! - A region snippet's slot is found by its id's exact text, with no selector built from it: an id with a quote or a bracket no longer throws or matches another slot, and its fallback marker escapes the id.
  • #1126 c94c8e0 Thanks @PuruVJ! - A soft refresh (invalidateAll) while a navigation waits on the next page's stylesheet no longer takes that sheet out of the head: the navigation goes in as soon as the sheet loads, styled, instead of after the full 2 s wait and unstyled.
  • #784 1497db2 Thanks @PuruVJ! - core: a navigation never adopts a meta http-equiv="set-cookie" from a fetched page (beside <base> and refresh / CSP metas), and a dev and e2e rule (rule_head_adopted) says when the head gains any of them after the first document
  • #594 0a40057 Thanks @PuruVJ! - In dev, a tab whose islands fail to load after a dependency re-optimize reloads once, not once per failing island.
  • #694 4c99764 Thanks @PuruVJ! - @ogygia/core: every answer that reaches a region's address, applied or dropped as older, is now a move of a stored-answer machine, so observe(), a test's machine trace and devtools see each one.
  • #964 3b77e25 Thanks @PuruVJ! - ogygia is now built and tested on Svelte 5.57.3. On Svelte 5.56, a held region whose query fails after another one failed throws a TypeError from inside Svelte; upgrade to 5.57 to avoid it.
  • #1270 11e87f7 Thanks @PuruVJ! - The viewport tracker no longer keeps observing a region with no box of its own after it stops following it (for example once a navigation took the region off the page).
  • #1525 03b75ac Thanks @PuruVJ! - The router reads the address bar for the page on screen, so a page script's own history.replaceState (stripping tracking params, or devtools' ?og-devtools=on|off switch) no longer leaves it remembering the old address for a refresh, a fragment link or a back step.
  • #483 721894d Thanks @PuruVJ! - A hole fetched on interaction and kept as a live region revalidates on load after a remount, instead of waiting on a media query named interaction that never matches.
  • #1479 c807794 Thanks @PuruVJ! - In dev and rules builds, the hydration scheduler's count of waiting islands is checked against the islands it holds (rule_turns_counted), so a drift is said instead of leaving islands waiting.
  • #818 08a09ed Thanks @PuruVJ! - Leaving a page with two identical regions (same component, same props) now removes both of them; one of the pair no longer stays on the next page.
  • #1476 e29dc84 Thanks @PuruVJ! - In dev, a plain error thrown in ogygia's own code that nothing caught (a TypeError, say) now breaks rule_failure_uncoded, not only an [ogygia] message with no code.
  • #1505 8216703 Thanks @PuruVJ! - A streamed page.data promise the page never resolved rejects with ogygia's coded error (code: 'page_promise_unresolved'), not a plain copy of its message.
  • #1729 d3fcc32 Thanks @PuruVJ! - Where there is no IntersectionObserver, a viewport watch still throws to its caller, but no longer leaves a broken tracker behind that fails every later watch and throws when the page's trackers end.
  • #448 ba47506 Thanks @PuruVJ! - A region with no box of its own (its content is position: fixed, or it is display: contents) with a visible schedule now wakes, fetches and takes its hydrate turn when what it renders is on screen, as its download's priority already said; it waited for its own empty box before.
  • #495 6be3ece Thanks @PuruVJ! - ogygia's generated modules answer only to ogygia:<realm>/… ids now; the old virtual:ogygia/… ids are gone, and a portable snippet's scoped class names change once with its new id.
  • #493 42129af Thanks @PuruVJ! - A build fails with virtual_wrong_realm when one of ogygia's server modules would reach the browser bundle (or a browser module the server bundle), at import time and again over the finished bundle.
  • #489 b3bf281 Thanks @PuruVJ! - An import of a virtual:ogygia/… module that does not exist now fails with the virtual_unknown message, instead of an unresolved-import error from the bundler.
  • #492 e858ae2 Thanks @PuruVJ! - The build serves one module per realm, ogygia:server, ogygia:boot and ogygia:region, with named exports, and ogygia/types declares them, generated from the module table so each type is read off the code that makes the value.
  • #1644 77b4f8c Thanks @PuruVJ! - A view-transition name that only the next page has comes back on its element once a client navigation's transition settles, so the next navigation between two such pages animates it again.
  • #1180 5b7f197 Thanks @PuruVJ! - A region whose wake is not a trigger (a typo like visable, or a value computed at runtime through region()'s options) now wakes on load, as an unknown fetch schedule already did. It was taken for a media query that never matches, so the region never woke.
  • #1087 5442971 Thanks @PuruVJ! - A router prefetch no longer imports a lake's or a server-only hole's entry as a module: the page asked the server for /<region id> twice and ended in chunk_reload_needed (a hole nested in an island, after a client navigation).
  • #1311 779fa59 Thanks @PuruVJ! - A kept region whose next page's props carry a live value the build did not predict now shows those props after the navigation: the runtime loads the wire codec first, instead of silently keeping the old props.
  • #1311 779fa59 Thanks @PuruVJ! - An island whose props carry a live value the build did not predict (a forwarded children, a snippet passed as a prop, a spread of $props()) now hydrates: the runtime loads the wire codec when that island wakes, instead of failing with "wired prop but no wire feature". Builds that already ship the codec are unchanged.
  • #812 4282ea0 Thanks @PuruVJ! - A region whose props carry a wired class, a store or an og.$ function keeps the same data-og-fp from one server render to the next, so a navigation that keeps it on screen keeps it mounted with its state, and the server-delta render can skip it.
  • #983 f3f8389 Thanks @PuruVJ! - @ogygia/core: a server island inside a server island that wakes (render: 'deferred', wake, or a held region with a schedule) shows after the outer one wakes, instead of going blank. The outer hole's signed address now says it wakes (&w=1), and the endpoint renders its answer the way the browser hydrates it.

Updated dependencies: @ogygia/[email protected]

0.13.1 patch

@ogygia/core

Patch Changes

  • #454 b954d0a Thanks @PuruVJ! - A shared chunk that fails to download on a large page (one whose resource timing buffer is already full) is asked for again once and then said once with chunk_reload_needed, instead of being retried on every wake without the message.
  • #455 00f367d Thanks @PuruVJ! - An island clicked before it wakes no longer waits for the click-replay code to download: that small chunk is fetched as background work once an island is armed (after the page's critical resources), instead of at the click.
  • #456 2edf97e Thanks @PuruVJ! - Back and Forward land exactly where the page was left when a region above that position gets its height after the page is swapped in: the scroll is held there while the page lays out, until the visitor scrolls or interacts.
  • #453 16302da Thanks @PuruVJ! - A router navigation between pages at different URL depths asks for the next page's stylesheets (and every other head URL) at the next page's address, not resolved against the page being left.
0.13.0 minor

@ogygia/core

Minor Changes

  • #174 413e77f Thanks @PuruVJ! - A page discloses which ogygia it runs on window.__ogygia.v (a Set of versions, as Svelte's window.__svelte.v), on csr=false and csr=true pages alike.
  • #175 a99a49a Thanks @PuruVJ! - Every ogygia error and warning has a code and a page at ogygiajs.dev/e/<code>: dev prints the wording and the link, a production build prints the link alone ([ogygia] https://ogygiajs.dev/e/<code>?<args>), so the wording stays out of the client and server bundles.

Patch Changes

  • #226 019b77e Thanks @PuruVJ! - In dev, a barrel saved while a transform resolves through it is built again: the build in flight stores nothing and its callers get the new export map, instead of imports rewritten to the old files until the next edit (#200).
  • #258 734c4c5 Thanks @PuruVJ! - Barrel imports in dev now resolve each leaf with the environment that asked: a leaf the client and the server resolve to different files (by conditions) no longer gets the other one's file, from a transform running at the same time or from the cached barrel map (#252).
  • #256 25ab8c7 Thanks @PuruVJ! - A batch hole stream whose visitor leaves now stops: the holes not rendered yet never render or take a render slot, and the answers that land after it are dropped instead of thrown into the closed stream (#245).
  • #316 da577ee Thanks @PuruVJ! - A batch of a page's holes stops when the visitor leaves the page (or when the navigation that started it is called off), and every way a batch ends lets go of its answer's body, the server's end mark included.
  • #223 ad8a29a Thanks @PuruVJ! - A batch stream that goes quiet for 10 seconds is given up: the holes it still owes fetch on their own instead of keeping their fallback forever (#214).
  • #225 29d8553 Thanks @PuruVJ! - The profiler's visit beacons no longer take the first tab switch for the page leaving: coming back to the tab or a back/forward cache restore opens the visit again, so later navigations, interactions and shifts go out with the next hide, and the standalone beacon sends no copy after its final visit (#209).
  • #256 25ab8c7 Thanks @PuruVJ! - Concurrent requests for one cached hole (a maxAge region) now share one render instead of each rendering it and taking a render slot; a failed render fails the requests that joined it and is not stored (#244).
  • #321 17e009a Thanks @PuruVJ! - An app's callback that throws (a beforeNavigate or afterNavigate hook, a page store subscriber, a ref watcher or disposer, a source receipt seam, a devtools sink) now reaches the page's error handler (reportError), or the console on a server, instead of being dropped; the others still run.
  • #265 ee66652 Thanks @PuruVJ! - A lazy chunk whose own dependency failed to download is asked for again once, not on every later wake: the runtime then says once that the page needs a reload (chunk_reload_needed), and a runtime that fails to load at all now says so too (runtime_load_failed) (#262).
  • #317 7f64cd1 Thanks @PuruVJ! - On a Kit-hydrated page, a custom element Kit removes (and mounts anew) leaves the class watch, and the watch's observer goes once no host is left, instead of holding the removed hosts for good (#281).
  • #186 01dc5b9 Thanks @PuruVJ! - Compiling a page with many regions is up to 1.9x faster: each region import no longer walks the whole file again to learn whether it is used.
  • #302 a39c26f Thanks @PuruVJ! - A waking region no longer searches the whole page for a script that needs devalue: the page is asked once, and again only when new markup comes in, so a 250-region page spends about 0.2 ms on it instead of about 48 ms.
  • #169 e8cd9f7 Thanks @PuruVJ! - A page whose islands get plain JSON props no longer downloads devalue: it loads only when a props sidecar, the page seed or page facts are in devalue's lane, beside the hydrate code (about 2 KB brotli off each island page of the benchmark).
  • #265 ee66652 Thanks @PuruVJ! - A click on an island before it is live now acts once, when it wakes: the island waits for what replays the click before it goes live, instead of letting the replay come in later, beside the visitor's next click (#260).
  • #256 25ab8c7 Thanks @PuruVJ! - An exposure sink that rejects no longer crashes the server: the failure is logged with a message code, and the sink's send is handed to the platform's waitUntil when it has one, so serverless instances no longer cut exposures off. The response never waits for the send (#243).
  • #384 4da8fe4 Thanks @PuruVJ! - In Firefox a chunk or island file whose download was dropped is asked for again under a fresh URL, as in the other browsers: a resource-timing status of 0 now reads as no response (#388).
  • #187 b46798f Thanks @PuruVJ! - The build's flag inventory takes time in line with a module's size: each flag's line is found from one pass over the file, not counted again from the top.
  • #340 24c6592 Thanks @PuruVJ! - A heading the router focused gives its tabindex back when focus leaves it, even after a second navigation focused it again meanwhile (a refresh in place at its #hash), or when it is kept across the navigation inside an island: it no longer stays in the tab order with tabindex="-1" for good (#278).
  • #253 b60df97 Thanks @PuruVJ! - A forced refresh at an address a navigation batch reserved no longer orphans the holes that joined the batch: they wait on the refresh, which settles them with the first frame written there or fails them with its own error, and a hole that binds after the batch ended fetches on its own (#233).
  • #253 b60df97 Thanks @PuruVJ! - A page's form restore window ends when the visitor goes on: fields restored on a page no longer leak into the next page's islands within 5 s (#235).
  • #324 7b35e33 Thanks @PuruVJ! - A router navigation after another one that brought Kit's FOUC <style> goes in as well, instead of throwing inside the head merge and loading the page whole.
  • #253 b60df97 Thanks @PuruVJ! - The newest frame a region gets paints last: an older live tick or hole refresh still waiting for its stylesheet no longer paints over a newer one that needed none (#231).
  • #305 e605070 Thanks @PuruVJ! - A region refresh that starts while a first fetch of the same hole is still out stops that fetch, and the regions that waited on it get the refreshed HTML.
  • #303 7a4bde1 Thanks @PuruVJ! - A hydrating region records its <head> content from what it added, not by copying and scanning the whole <head>: on a 250-region page with a large head this takes about 0.15 ms instead of about 58 ms.
  • #411 537c7f3 Thanks @PuruVJ! - A hole that loads at once is now asked for once in every browser, including Safari: before, Safari asked twice.
  • #339 f693f50 Thanks @PuruVJ! - A hole's island with wake: 'interaction' wakes on the visitor's first press or key when the hole's own when is another schedule; it used to be armed as the hole's on-demand fetch, which never fired, and stayed server markup for good (#338).
  • #223 ad8a29a Thanks @PuruVJ! - A hole's fetch, its answer and its island's wake are machines: an island wakes whoever fetched its answer, a kept fallback that later gets an answer wakes too, a failed refetch no longer marks the next answer a refresh, a region with two schedules drops both when it leaves, and an interaction island that fails to wake says so (#206).
  • #339 f693f50 Thanks @PuruVJ! - A hole put back on the page after a while off it shows its answer again and wakes its island, instead of showing nothing (its island had taken its markup with it) or keeping an island nothing wakes, once the frame store let the answer go (#336).
  • #223 ad8a29a Thanks @PuruVJ! - A renewed hole capability belongs to its address: every copy of the hole that took the answer moves onto it, not only the one that fetched (#213).
  • #223 ad8a29a Thanks @PuruVJ! - A copy of a hole that leaves the page gives up only its own place in the shared fetch: its twin's retry is no longer cancelled, and a twin that joined a batch no longer waits forever (#205).
  • #173 e7c31c0 Thanks @PuruVJ! - Islands hydrate the component itself instead of through a wrapper component: an island page ships less Svelte (about 0.3–0.4 KB brotli), and a placed island's server markup carries one marker pair fewer.
  • #253 b60df97 Thanks @PuruVJ! - A region put back while its island loads wakes once, and the old run's failure no longer reaches the new visit: no error logged against the new module, no failure report, its drift watch and scheduler place kept (#230).
  • #387 4a45161 Thanks @PuruVJ! - A region or hole answer is parsed in a document with no browsing context, so no engine builds its custom elements before the restore (Firefox 159 did, and the page showed a component's server render twice); a host a component runtime upgraded first keeps its own root, gets its light DOM back without the server's copy, and says restore_late in every build (#382).
  • #253 b60df97 Thanks @PuruVJ! - An early-click capture ends only its own arming: a region put back while its first wake loaded keeps catching clicks, and the old capture no longer replays its clicks onto the new visit (#232).
  • #265 ee66652 Thanks @PuruVJ! - An island whose own file fails to download is asked for again under a fresh URL, at once and by every later wake, like the runtime's lazy chunks: one dropped download no longer leaves the island, and every island of that file, dead for the tab (#261).
  • #305 e605070 Thanks @PuruVJ! - Two islands of one file whose download fails together share one retry, so the module loads once instead of twice (#271).
  • #333 865eb55 Thanks @PuruVJ! - The dev rule that no shared work keeps a failure now checks what is kept now: once that failure is dropped or replaced, it no longer reports it again (#330).
  • #317 7f64cd1 Thanks @PuruVJ! - On a Kit-hydrated page, the wait for Kit's page ends once no island waits for it: an island that leaves the page while it waits no longer keeps the wait going (its timers and its watch of Kit's page).
  • #317 7f64cd1 Thanks @PuruVJ! - On a global that refuses an accessor on Kit's page symbol, an island waiting for Kit's page now hydrates once Kit publishes it, instead of waiting for good.
  • #223 ad8a29a Thanks @PuruVJ! - The islands inside a remounted swr lake wake once its refresh lands, not only when the refresh fails (#204).
  • #321 17e009a Thanks @PuruVJ! - An inline island a client navigation created whose code fails to load now prints island_load_failed, instead of rendering nothing without a word.
  • #384 4da8fe4 Thanks @PuruVJ! - An island file that 404s is no longer asked for again under a fresh URL when the browser's timing entry for it lands late (Firefox on a busy machine): the loader waits for the entry, up to a second.
  • #215 a7ce10d Thanks @PuruVJ! - A lazy runtime chunk (the hydrate core, devalue, the interaction replay) that fails to download is asked for again under a fresh URL, so one dropped request no longer leaves every later island wake in the tab dead (#201).
  • #187 b46798f Thanks @PuruVJ! - Finding the images that downloaded beside a page's largest paint takes time in line with its images.
  • #223 ad8a29a Thanks @PuruVJ! - A live region is one machine: a tick that comes while its island hydrates no longer mounts a second island, turning static disposes the island, and turning interactive stops the static morph (#211).
  • #339 f693f50 Thanks @PuruVJ! - A live region put back on the page goes on in its last tick's mode: a static one follows the writes at its address again, an interactive one hydrates its island again, instead of both stopping until the next tick (#337).
  • #315 7e7c047 Thanks @PuruVJ! - @ogygia/core: draining the load queue reads each waiting download's class once instead of sorting the whole queue every time a download ends, so a big page spends less time picking what to fetch next, in the same order.
  • #339 f693f50 Thanks @PuruVJ! - A region that leaves the page before its load schedule fires starts nothing: no fetch of a hole's answer off the page (which then gave up and reported a failure), and no wake of its island (#335).
  • #360 64431ac Thanks @PuruVJ! - A region's mailbox runs any number of events queued in one turn on a flat stack, instead of overflowing it after a few thousand sync ones (#342).
  • #339 f693f50 Thanks @PuruVJ! - A region whose element leaves the page while one of its waits is queued behind another event ends that wait with STALE, instead of leaving it (and the wake or live tick around it) unsettled for good (#373).
  • #360 64431ac Thanks @PuruVJ! - A region's mailbox hands each handler a turn of its own: a wait from a handler that does not hold the turn (two waits at once, a timer it left behind) no longer ends another handler's turn and lets two events of one element run at once (#341).
  • #316 da577ee Thanks @PuruVJ! - A navigation called off before its swap (back pressed, a link to the page on screen) takes the next page's stylesheets it put in the head out again, and stops waiting for them at once, instead of leaving them to style the page on screen (#267).
  • #216 e788339 Thanks @PuruVJ! - Two links clicked while the router chunk downloads: the last one wins, not the first (#203).
  • #324 7b35e33 Thanks @PuruVJ! - The next page's stylesheets load inert while a navigation waits, and style the page only once it goes in: a sheet that arrived first no longer styles the page still on screen (#267).
  • #324 7b35e33 Thanks @PuruVJ! - A navigation whose swap throws (with or without a view transition), or whose devalue fails to load, now ends and goes to the browser with its error said, instead of staying in flight or finishing as if the page went in (#276).
  • #316 da577ee Thanks @PuruVJ! - The page facts a hole's answer brings are its page's: a navigation that swaps the next page in before any island woke no longer merges them over the next page's page.data (#269).
  • #298 28e957d Thanks @PuruVJ! - A value the page seed cannot carry (a function, a symbol, an unknown class) is left out where it sits, so regions still get the rest of page.data, form and error instead of undefined.
  • #370 9272db9 Thanks @PuruVJ! - A streamed $page.data promise whose value throws as it is staged (a getter that throws) now fails that promise's {#await} instead of keeping the response open for good; the other promises still stream and the stream closes (#367).
  • #321 17e009a Thanks @PuruVJ! - A page made for one browser (devtools events, the profiler's beacon) whose headers cannot be changed now prints personal_response_unmarked, instead of going out without private, no-store and without a word.
  • #221 a5d28b0 Thanks @PuruVJ! - A plugin's shared ask hook throws when no implementation answered and one threw, instead of answering undefined as if nobody knew (#198).
  • #321 17e009a Thanks @PuruVJ! - A plugin's done that throws, or whose work fails after the response, now prints plugin_hook_failed with the error, instead of nothing; the response still never fails on it.
  • #258 734c4c5 Thanks @PuruVJ! - A dev edit that runs a plugin's server half again no longer leaves its old run in the shared hooks: the plugins of the run before leave first, so notify reaches only the current ones and ask answers from them (#251).
  • #381 debb73b Thanks @PuruVJ! - The browser runtime no longer ships the server's render and stream deadlines: each named retry policy is kept only where its code reads it.
  • #216 e788339 Thanks @PuruVJ! - A prefetch answered after a remote mutation cleared the page cache no longer puts the page from before the mutation back (#208).
  • #253 b60df97 Thanks @PuruVJ! - An old prefetch no longer forgets a newer prefetch of the same page when its slot comes up after a cache clear, so a click on that page lifts the newer one instead of waiting behind every other guess (#234).
  • #223 ad8a29a Thanks @PuruVJ! - preload() of a hole fetches it the way the hole does: a keepFallback() answer keeps the fallback instead of wiping it, a page or a redirect is refused, and a renewed capability is kept (#212).
  • #370 9272db9 Thanks @PuruVJ! - A profiler mark() made before the page's beacon loads now waits for it however late it comes, instead of being dropped after 10 s; the beacon takes the waiting marks as it loads (#369).
  • #370 9272db9 Thanks @PuruVJ! - A file the static host could not answer once (a 5xx, a timeout, a network blip) is weighed again by the next profiler report instead of being left out for the life of the process, and reports weighing a file at once share one fetch (#362).
  • #170 6a63ecf Thanks @PuruVJ! - The island prop-mutation warning (a dev aid) no longer ships in production builds: its guard is created only in dev, so the bundler drops it (about 0.4 KB brotli per island page).
  • #340 24c6592 Thanks @PuruVJ! - A region stylesheet whose download failed is asked for again by the next answer that carries it, which waits on that download only: the region no longer stays unstyled for the rest of the tab, nor waits 5 s on a sheet that never loads (#274).
  • #340 24c6592 Thanks @PuruVJ! - A hole kept across a navigation keeps its stylesheet: a region sheet stays in the head while a region on the new page still uses it, instead of going with the head merge because the new page's server head does not list it (#275).
  • #305 e605070 Thanks @PuruVJ! - A cached hole whose first request leaves while its render waits for a slot keeps its place in the render queue for the requests still waiting on it, instead of being rendered again from the back of the queue; a render every request left never takes a slot.
  • #328 cc047cc Thanks @PuruVJ! - A cached region render is keyed by its region, props, session and page as separate fields, so two visitors whose props and session spell one string another way never share a render (#312).
  • #218 e6aed57 Thanks @PuruVJ! - Hole renders never run above the concurrency limit: a freed slot goes straight to the next waiter, and a render past its timeout gives its slot to the next hole, so renders stuck on a hung upstream never block the others (#195).
  • #218 e6aed57 Thanks @PuruVJ! - A hole answers within the render timeout, its wait for a render slot included, and the server logs when a render first outlives it (#195).
  • #173 e7c31c0 Thanks @PuruVJ! - A live region and a woken deferred island now adopt their server HTML: they were thrown away and re-rendered on the client every time they hydrated.
  • #321 17e009a Thanks @PuruVJ! - A request's owned work now stops at once when its answer is a HEAD or a page SvelteKit turns into a 304, instead of running until the visitor leaves (#320).
  • #258 734c4c5 Thanks @PuruVJ! - A router page's CSS in dev is no longer lost after one failed read of the router CSS registry: the next render reads it again (#249).
  • #265 ee66652 Thanks @PuruVJ! - A link the browser keeps the page on screen for (a file download, a 204) works on every click again, not only the first: the router's hand-off of a navigation to the browser now ends it, so a later click on the link no longer joins it and gets swallowed (#266).
  • #265 ee66652 Thanks @PuruVJ! - Back from a page the router handed to the browser (a csr=true Kit page, a page that is not ogygia's) now loads the page before it: the router's history entry for the visit is replaced by the browser's document instead of reloaded, so the router page's entry no longer belongs to the new document (#259).
  • #325 4b63071 Thanks @PuruVJ! - The hashchange the router fires for an app-managed fragment link has the address before the click as its oldURL (#277).
  • #325 4b63071 Thanks @PuruVJ! - The router writes a history entry only when a page goes in: download and 204 clicks add none, and a download sent as HTML (Content-Disposition: attachment) is saved, not swapped into the page (#297).
  • #325 4b63071 Thanks @PuruVJ! - The router keeps the app's own history.state on the entries it takes over (the one it starts on, an app's own pushState met on Back or Forward, one replaced in place): its id goes beside that state instead of over it (#375).
  • #325 4b63071 Thanks @PuruVJ! - The router keeps one record of the visitor's history, and every page left keeps its scroll: Forward after Back lands where the page was left, not at the top (#270).
  • #254 346c692 Thanks @PuruVJ! - The router's navigation code that fails to download is asked for again under a fresh URL: the next click, invalidateAll, invalidate or preloadData loads it, instead of links falling back to full page loads and refreshes failing until a reload, and a prefetch it fails for warms nothing instead of leaving an uncaught error (#238).
  • #305 e605070 Thanks @PuruVJ! - A navigation that was waiting on a prefetch when a remote mutation cleared the page cache fetches the page again instead of showing it as it was, a prefetch of a page a navigation is fetching joins that request, and a prefetch the clear ended gives its turn back without fetching.
  • #265 ee66652 Thanks @PuruVJ! - A link component that clicks its inner <a> again after the visitor's click no longer turns the router's navigation into a full load when that second click never reaches the document (a click event that stays in its shadow root, or an anchor the swap took out of the page): it joins the navigation the first click started (#263).
  • #329 c781aeb Thanks @PuruVJ! - In dev, ogygia checks its own rules after each navigation and machine move (one mount per region, the address bar matches the router's history, nothing of a left page stays open, no failure leaves without a code) and after each response (a request's work ends with it, no shared work keeps a failure), and says a broken one with its code; a production build ships none of them (#313).
  • #253 b60df97 Thanks @PuruVJ! - The hydration scheduler wakes at its earliest wait: a short wait for a region's viewport report set during a long hold no longer waits out the hold (#236).
  • #300 b10c054 Thanks @PuruVJ! - Handing out hydrate turns costs the same per region however many are waiting: a page with 250 load regions spends about a third of the time scheduling them, 2,500 regions about a twentieth.
  • #299 2a970fe Thanks @PuruVJ! - Matching copied records in region props to the page seed takes time in line with the props: a list page whose region gets copies of its products renders its seed references up to 3.5x faster.
  • #380 469d980 Thanks @PuruVJ! - A region's viewport snapshot is held by its lifetime with one cleanup instead of a scope of its own, so a hydrate turn costs about what it did before the scheduler moved onto scopes.
  • #216 e788339 Thanks @PuruVJ! - A soft refresh (invalidateAll) still in flight when the visitor navigates no longer merges the old page's head and data into the new one (#202).
  • #324 7b35e33 Thanks @PuruVJ! - invalidateAll during a navigation refreshes the page on screen, not the page the navigation is still bringing, and a navigation that goes in ends a refresh still out (#268).
  • #323 7a53a56 Thanks @PuruVJ! - A publish's thaw notices go through an outbox handed to the request's waitUntil (the new app.keepAlive), so a serverless instance that freezes after the response no longer loses them and peers no longer keep stale pages until their TTL (#286).
  • #321 17e009a Thanks @PuruVJ! - A peer whose store fails to apply a thaw notice now answers an error, so the sender sends it again, instead of answering done and deduping the retry; app.notify rejects once every hook ran when one failed (#287).
  • #384 4da8fe4 Thanks @PuruVJ! - In Safari an island file whose download failed is asked for again under a fresh URL, as in the other browsers, and its failure is reported as a failed load, not a failed hydration (#383).
  • #254 346c692 Thanks @PuruVJ! - A transportable class whose module fails to download is asked for again: the next island that carries it loads it under a fresh URL and decodes it, instead of every later island decoding without the class until a reload (#237).

Updated dependencies: @ogygia/[email protected]

0.12.3 patch

@ogygia/core

Patch Changes

  • #166 a2eade9 Thanks @PuruVJ! - A component a markdown page imports is styled on a csr=false page: its scoped CSS (and any style file it imports) now ships in the page's content stylesheet beside the page's own <style>.
0.12.2 patch

@ogygia/core

Patch Changes

  • #164 2a4dc9c Thanks @PuruVJ! - ogygia.extensions() and ogygia.preprocess() from ogygia/vite are callable again and do nothing (['.svelte'] and []), so a svelte config written for 0.8 loads; the markdown ones come from @ogygia/content/vite.
0.12.1 patch

@ogygia/core

Patch Changes

  • #162 0f2f6d6 Thanks @PuruVJ! - A render: 'deferred' hole timed with wake builds again: wake times it as fetch does, and the build warns with the fetch to write.
0.12.0 minor

@ogygia/core

Minor Changes

  • #157 a217b91 Thanks @PuruVJ! - An island loaded without a src (a region the browser renders, a held or live region from a remote function or a stream, a hole rebuilt after a failed hydration, a portable snippet with no island graph) loads its content-hashed file: the build writes its locations into one content-hashed map, which the runtime's script names and the first such load reads.
  • #157 a217b91 Thanks @PuruVJ! - A client-side navigation into a page of another build (a deploy since the page was loaded) loads that page as a document instead of swapping it into the running runtime, so two builds' islands, runtimes and Svelte never meet on one page.
  • #157 a217b91 Thanks @PuruVJ! - Every file a build writes under <appDir>/immutable/ is now named by its content, so a host's year-long rule for that directory can never serve another build's code: the stable-name files (og-region.<id>.js, og-runtime.<id>.js), whose content changed every build, are gone. An island's entry is now a name, not a file. The one file at a fixed name is <appDir>/ogygia.json, beside Kit's version.json: the current build's locations, which a page that outlived its build reads to wake its islands on the current code. Serve it as you serve version.json (revalidated); a federated app also needs the same Access-Control-Allow-Origin on it as on its immutable/ files. A page cached from before content hashing, which loaded the runtime by its stable name, no longer recovers.

Patch Changes

  • #151 64f6046 Thanks @PuruVJ! - A client-side navigation no longer removes nodes the page's own code put in <body> (a popover portal's anchor, a toast host), so a popover in an island the navigation keeps still opens afterwards; only the server's body children and attributes are replaced.
  • 75a5cdd Thanks @PuruVJ! - handle({ secret }) signs region capabilities with a secret the app passes (e.g. from $env/static/private), for a server that never sees OGYGIA_SECRET at runtime; it signs exactly as the same OGYGIA_SECRET does, and every copy of ogygia in the process uses it.
0.11.5 patch

@ogygia/core

Patch Changes

  • #144 cdd2ec0 Thanks @PuruVJ! - An app with no deferred, live or lake region no longer ships the region element's fetch, apply and morph code.
  • #144 cdd2ec0 Thanks @PuruVJ! - An island page no longer downloads runtime code for features its app does not use.
  • #144 cdd2ec0 Thanks @PuruVJ! - A +page.md route counts as a page like +page.svelte, so a csr=false markdown page no longer makes every island page ship extra Svelte and runtime code.
  • #144 cdd2ec0 Thanks @PuruVJ! - An app whose islands never read their page no longer ships the page seed runtime or the MPA navigation handle.
0.11.4 patch

@ogygia/core

Patch Changes

  • #130 fede66a Thanks @PuruVJ! - The hook types type-check on SvelteKit 3 too: Handle is the library's own (Kit 3 moved Kit's to @sveltejs/kit/hooks), so a Kit 3 app no longer sees an untyped handle from ogygia, devtools or postrender.
0.11.3 patch

@ogygia/core

Patch Changes

  • #118 acce10a Thanks @PuruVJ! - A web component around a hole is restored like one around an island, so its own runtime no longer adopts it and moves the hole it holds.
0.11.2 patch

@ogygia/core

Patch Changes

  • #107 a83fe25 Thanks @PuruVJ! - The drop-in setContext now reaches islands inside a lake on a csr=true page; a csr=true page with no island ogygia wakes still ships no context.
0.11.1 patch

@ogygia/core

Patch Changes

  • #95 0eced1d Thanks @PuruVJ! - The "uses ogygia marks, but its package declares no ogygia.files" warning fires only for a real marked import, not for a dependency whose comments, strings or error messages merely mention with { wake } (the plugin packages tripped it).
0.11.0 minor

@ogygia/core

Patch Changes

  • #83 e229a9a Thanks @PuruVJ! - Remote deferred holes now share local holes' lifetime and renewal: they were signed for a fixed 5 minutes and answered 410 after, so a stored or cached page older than that showed dead remote regions. Plugins sign with core's rule through app.capability.
0.0.0 minor

@ogygia/core