statelyai/xstate
xstate@5.33.4Curated state management / ai tools / ai-agent repository (statelyai/xstate) tracked via conditional GitHub .atom polling.
XState is an orchestration library for modeling application logic and state machines in JavaScript and TypeScript. As applications grow complex, managing asynchronous flows, side effects, and UI transitions with uncoordinated boolean flags often leads to impossible states and race conditions. XState provides a formal, predictable way to declare and execute states and events with compile-time type safety.
Fixes assertEvent type narrowing for generic parameters and wildcards. Update dependency. Migration: None.
Key Release Highlights (xstate@5.33.4)
- Fixes
assertEventtype narrowing when operating on generic parameters (<TEvent extends EventUnion>), resolving false-positive 'Property does not exist' compiler errors. - Maintains narrowing for union-of-literals event types across both concrete and generic event inputs.
- Aligns type inference with runtime behavior for partial wildcard descriptors (such as
'FEEDBACK.*') inassertEventandExtractEventby retaining bare prefix events.
Verified safe drop-in upgrade for xstate in package.json.
npm install xstate@5.33.4Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (2)
Format: [Core Change] + [Required Action] + [Migration Effort]Fixes assertEvent type narrowing for generic parameters and wildcards. Update dependency. Migration: None.
Ships xstate@xstate@6.0.0-alpha.73 with upstream runtime. Pre-release build; test in staging. Migration: Low.
Upgrade & Migration Q&A (statelyai/xstate xstate@5.33.4)
Direct Answers for Engineers & AI AgentsIs statelyai/xstate xstate@5.33.4 safe to upgrade in production?
statelyai/xstate xstate@5.33.4 is classified as COMPATIBLE (PATCH release). Fixes assertEvent type narrowing for generic parameters and wildcards. Update dependency. Migration: None.
What breaking changes or compatibility risks exist in statelyai/xstate xstate@5.33.4?
No breaking API changes or peer dependency conflicts are recorded for statelyai/xstate xstate@5.33.4 in the RepoSense compatibility graph.
What is the bundle size impact of xstate xstate@5.33.4?
Measured bundle size telemetry is currently unavailable for xstate xstate@5.33.4; verify build output locally before deploying.
How do I upgrade xstate to xstate@5.33.4?
Upgrade xstate to xstate@5.33.4 by running "npm install xstate@xstate@5.33.4" and applying the migration steps: npm install xstate@5.33.4