sibujs 4.13.0 → 4.14.0

package/dist/{routeMiddleware-B1sp4P7a.d.ts → routeMiddleware-BySbueoE.d.ts}

@@ -39,31 +39,6 @@ interface HeadProps {
         target?: string;
     };
 }
-/**
- * Head() manages document <head> tags reactively.
- *
- * META SECURITY: each meta entry is committed TRANSACTIONALLY. All of its
- * attributes — static and reactive — are resolved into one snapshot, duplicate
- * case-insensitive names are rejected, and the assembled snapshot is validated
- * against the shared meta-refresh policy before anything reaches the DOM. An
- * approved snapshot is then materialised on a fresh `<meta>` element while it is
- * still detached and swapped in with a single `replaceWith()`, so no partially
- * updated element is ever connected. A snapshot that fails validation withdraws
- * the element entirely. See `utils/metaRefresh.ts`; the same policy governs SSR.
- *
- * NATIVE REFRESH DIRECTIVES MUST BE STATIC. A browser processes a meta refresh
- * when the element is INSERTED — it records the pending navigation there and
- * then, and removing or replacing the element afterwards is not a defined way to
- * cancel it. `Head()` therefore never publishes a snapshot whose effective
- * `http-equiv` is `refresh` from an entry that contains any reactive attribute,
- * even when the destination is allowed: what cannot be withdrawn must not be
- * handed over. Static refresh directives work as before, and every other
- * reactive meta entry — description, keywords, Open Graph, non-refresh
- * `http-equiv` — is unaffected.
- *
- * Supports dynamic title, meta tags, link tags, and structured data.
- * Each instance tracks its own elements and effects for independent cleanup.
- */
 declare function Head(props: HeadProps): Comment;
 /**
  * Sets structured data (JSON-LD) for SEO.

package/dist/{routeMiddleware-CedQTsLK.d.cts → routeMiddleware-CijZD5eW.d.cts}

@@ -39,31 +39,6 @@ interface HeadProps {
         target?: string;
     };
 }
-/**
- * Head() manages document <head> tags reactively.
- *
- * META SECURITY: each meta entry is committed TRANSACTIONALLY. All of its
- * attributes — static and reactive — are resolved into one snapshot, duplicate
- * case-insensitive names are rejected, and the assembled snapshot is validated
- * against the shared meta-refresh policy before anything reaches the DOM. An
- * approved snapshot is then materialised on a fresh `<meta>` element while it is
- * still detached and swapped in with a single `replaceWith()`, so no partially
- * updated element is ever connected. A snapshot that fails validation withdraws
- * the element entirely. See `utils/metaRefresh.ts`; the same policy governs SSR.
- *
- * NATIVE REFRESH DIRECTIVES MUST BE STATIC. A browser processes a meta refresh
- * when the element is INSERTED — it records the pending navigation there and
- * then, and removing or replacing the element afterwards is not a defined way to
- * cancel it. `Head()` therefore never publishes a snapshot whose effective
- * `http-equiv` is `refresh` from an entry that contains any reactive attribute,
- * even when the destination is allowed: what cannot be withdrawn must not be
- * handed over. Static refresh directives work as before, and every other
- * reactive meta entry — description, keywords, Open Graph, non-refresh
- * `http-equiv` — is unaffected.
- *
- * Supports dynamic title, meta tags, link tags, and structured data.
- * Each instance tracks its own elements and effects for independent cleanup.
- */
 declare function Head(props: HeadProps): Comment;
 /**
  * Sets structured data (JSON-LD) for SEO.