Files
bunext/dist/functions/server/server-post-build-fn.d.ts
T
tbenandClaude Opus 5.5 4d4a79a6dd Push HMR updates before the SSR rebuild in dev
Client-only edits are sent to the browser right after the hydration build,
without re-running server functions; SSR rebuilds afterwards and props are
re-fetched only when a .server.ts output changed or after fullRebuild. Page
requests wait for an in-flight SSR rebuild. The SSR build no longer runs
Tailwind, the PostCSS processor is reused across rebuilds, and the watcher
debounce drops from 200ms to 50ms.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-05 07:32:33 +01:00

24 lines
1.0 KiB
TypeScript

type Params = {
reload_all_controllers?: boolean;
/**
* Relative page paths whose client entry outputs changed in the last
* build. When provided with at least one entry, only controllers
* targeting those pages are re-rendered/re-pushed. When empty or
* omitted, every controller is refreshed (covers server-file-only
* changes, where hydration outputs are untouched but server props must
* still be re-fetched).
*/
changed_pages?: string[];
};
/**
* # Push a client-only HMR update
* Sends the new client bundle to every controller whose page is in
* `changed_pages`, without re-running server functions. The payload carries
* no `page_props`, so the browser keeps its current props and only swaps the
* hydration script/CSS. Used right after the hydration build so the browser
* doesn't wait for the SSR rebuild.
*/
export declare function pushClientUpdate(changed_pages: string[]): void;
export default function serverPostBuildFn(params?: Params): Promise<void>;
export {};