{"version":3,"names":["isServer","isHydrating","isSolidHydrating"],"sources":["is-hydrating.ts"],"sourcesContent":["import { isServer } from \"@solidjs/web\";\nimport { isHydrating as isSolidHydrating } from \"solid-js\";\n\n/**\n * Whether we are inside the hydration window — the Solid-2 equivalent of Base\n * UI React's `useIsHydrating`.\n *\n * Returns `true` while the markup is being produced or attached and must stay\n * byte-stable across the server→client boundary, and `false` for a\n * client-only (CSR) render. Concretely:\n *\n *   - **Server** (`renderToString*`): `isServer` is `true`. Solid's\n *     `isHydrating()` is always `false` on the server, so the `isServer` arm\n *     is what reports the hydration window here.\n *   - **Client, hydrating** (`hydrate()` or a resuming streamed `<Loading>`\n *     boundary): Solid's `isHydrating()` is `true` while server DOM is being\n *     claimed — so the first client pass sees the same value the server did\n *     and emits identical markup (no mismatch).\n *   - **Client, CSR or post-hydration**: both arms are `false`.\n *\n * Used to gate pre-paint `visibility: hidden` on geometry-positioned parts\n * (slider thumb / indicator in `renderBeforeHydration` mode) so the SSR'd\n * HTML doesn't flash at a wrong position before the prehydration script /\n * first measurement runs.\n *\n * NOTE: this is a plain read, not a reactive source, so read it where the\n * component is created. A consumer that needs to re-reveal *after* hydration\n * should depend on a measurement signal (which updates post-mount) rather\n * than expecting this to re-fire on its own.\n */\nexport function isHydrating(): boolean {\n\treturn isServer || isSolidHydrating();\n}\n"],"mappings":"AAAA,SAASA,QAAQ,QAAQ,cAAc;AACvC,SAASC,WAAW,IAAIC,gBAAgB,QAAQ,UAAU;;AAE1D;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA,OAAO,SAASD,WAAWA,CAAA,EAAY;EACtC,OAAOD,QAAQ,IAAIE,gBAAgB,CAAC,CAAC;AACtC","ignoreList":[]}