chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

create-effex@1.1.3

Patch Changes

• 2b57548: fix(hydrate): make element requirements provably match options.layers

  hydrate's element parameter was locked to Element<A, never, RendererContext | ControlCtx | SuspenseBoundaryCtx>, so any element that also required a user-provided service (NavigationContext, RouteDataProvider, etc.) had to be cast — as never or as unknown as Element<HTMLElement> — even though options.layers was providing exactly those services at runtime.

  HydrateOptions and hydrate are now generic over the layer type. The layer's provided services flow through Layer.Layer.Success<L> into the element's allowed R, so:

  • Passing an element that needs a service without providing a layer for it is a type error.
  • Providing a layer that only covers some of the element's requirements is a type error.
  • hydrate(App(), root, { layers: Platform.makeClientLayer(router) }) typechecks with no casts when the layer fully covers what App() needs.

  NoInfer on the extracted layer type keeps TypeScript from inferring L from the element's requirements — inference flows one way, from options.layers into the element, so forgetting a service is a compile-time error rather than a silent runtime failure.

  Removed the now-obsolete casts from create-effex's SSG and SSR templates, apps/docs, and the hydrate regression test.

@effex/dom@1.4.7

Patch Changes

• 2b57548: fix(hydrate): make element requirements provably match options.layers

  hydrate's element parameter was locked to Element<A, never, RendererContext | ControlCtx | SuspenseBoundaryCtx>, so any element that also required a user-provided service (NavigationContext, RouteDataProvider, etc.) had to be cast — as never or as unknown as Element<HTMLElement> — even though options.layers was providing exactly those services at runtime.

  HydrateOptions and hydrate are now generic over the layer type. The layer's provided services flow through Layer.Layer.Success<L> into the element's allowed R, so:

  • Passing an element that needs a service without providing a layer for it is a type error.
  • Providing a layer that only covers some of the element's requirements is a type error.
  • hydrate(App(), root, { layers: Platform.makeClientLayer(router) }) typechecks with no casts when the layer fully covers what App() needs.

  NoInfer on the extracted layer type keeps TypeScript from inferring L from the element's requirements — inference flows one way, from options.layers into the element, so forgetting a service is a compile-time error rather than a silent runtime failure.

  Removed the now-obsolete casts from create-effex's SSG and SSR templates, apps/docs, and the hydrate regression test.

@effex/router@1.3.8

Patch Changes

• Updated dependencies [2b57548]
  • @effex/dom@1.4.7

docs@0.0.31

Patch Changes

• Updated dependencies [2b57548]
  • @effex/dom@1.4.7
  • @effex/router@1.3.8

[cloudflare-workers-and-pages]

Deploying effex-api with    Cloudflare Pages

Latest commit:	78acf9f
Status:	✅  Deploy successful!
Preview URL:	https://9c6191e5.effex-api.pages.dev
Branch Preview URL:	https://changeset-release-main.effex-api.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying effex with    Cloudflare Pages

Latest commit:	78acf9f
Status:	✅  Deploy successful!
Preview URL:	https://5c2aec74.effex.pages.dev
Branch Preview URL:	https://changeset-release-main.effex.pages.dev

View logs