[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

@typeonce/effect-machine@0.43.0

Minor Changes

• c9934ae: MachineState now renders child machines: pass a child bridge such as machine.child(QuantityChild) and the path and snapshot are typed by the child machine. inactive also renders while the state that owns the child is not active. MachineStateProps now takes the bridge type and the path, MachineStateProps<A, Path>.

  Add useMachineResult(atom) for custom readers of result atoms such as AtomMachine.select, matches, or can. It serves the planned value during server rendering and hydration and keeps the last success while the machine starts, so hydrated markup is not replaced. Add AtomMachine.isMachineAtom to tell machine bridges from child bridges.

  createMachineContext factories can declare a per-owner capability layer as a second parameter, and the Provider then requires a matching layer prop:

  const SignIn = createMachineContext((input: SignInInput, navigation: Layer.Layer<Navigation>) =>
    AtomMachine.bind(Atom.runtime(Layer.provideMerge(navigation, AppLayer))).make(SignInMachine, input)
  )
  
  <SignIn.Provider input={input} layer={navigationLayer(router)} />

Patch Changes

• 1d6c808: Serve referentially stable server values from machine atoms, so React no longer warns that getServerSnapshot should be cached while hydrating MachineState or other hooks that read machine atoms.

@typeonce/effect-machine-react@0.43.0

Minor Changes

• c9934ae: MachineState now renders child machines: pass a child bridge such as machine.child(QuantityChild) and the path and snapshot are typed by the child machine. inactive also renders while the state that owns the child is not active. MachineStateProps now takes the bridge type and the path, MachineStateProps<A, Path>.

  Add useMachineResult(atom) for custom readers of result atoms such as AtomMachine.select, matches, or can. It serves the planned value during server rendering and hydration and keeps the last success while the machine starts, so hydrated markup is not replaced. Add AtomMachine.isMachineAtom to tell machine bridges from child bridges.

  createMachineContext factories can declare a per-owner capability layer as a second parameter, and the Provider then requires a matching layer prop:

  const SignIn = createMachineContext((input: SignInInput, navigation: Layer.Layer<Navigation>) =>
    AtomMachine.bind(Atom.runtime(Layer.provideMerge(navigation, AppLayer))).make(SignInMachine, input)
  )
  
  <SignIn.Provider input={input} layer={navigationLayer(router)} />

Patch Changes

• 1d6c808: Serve referentially stable server values from machine atoms, so React no longer warns that getServerSnapshot should be cached while hydrating MachineState or other hooks that read machine atoms.
• Updated dependencies [c9934ae]
• Updated dependencies [1d6c808]
  • @typeonce/effect-machine@0.43.0

@typeonce/effect-machine-devtools@0.43.0

Patch Changes

• Updated dependencies [c9934ae]
• Updated dependencies [1d6c808]
  • @typeonce/effect-machine@0.43.0

@typeonce/oxlint-plugin-effect-machine@0.43.0