---
title: TimeWarp.State
description: State management for .NET. Blazor components, JavaScript interop, and render subscriptions are in TimeWarp.State.Blazor.
type: package
latest: 12.0.0-beta.13
stable: 11.0.3
repository: https://github.com/TimeWarpEngineering/timewarp-state
---
State management for .NET. Blazor components, JavaScript interop, and render subscriptions are in TimeWarp.State.Blazor.
| | |
|---|---|
| Latest stable | `11.0.3` |
| Latest prerelease | `12.0.0-beta.13` |
| Downloads | 33,499 |
| Last published | 2026-10-13 |
| Target frameworks | `net11.0` |
## Install
```sh
dotnet add package TimeWarp.State
dotnet add package TimeWarp.State --prerelease
```
[NuGet](https://www.nuget.org/packages/TimeWarp.State) · [Source](https://github.com/TimeWarpEngineering/timewarp-state) · Part of the [timewarp-state](/projects/timewarp-state/) family
---
[](https://github.com/TimeWarpEngineering/timewarp-state)
[](https://github.com/TimeWarpEngineering/timewarp-state/actions)
[](https://github.com/TimeWarpEngineering/timewarp-state)
[](https://github.com/TimeWarpEngineering/timewarp-state/issues)
[](https://github.com/TimeWarpEngineering/timewarp-state/issues)
[](https://scorecard.dev/viewer/?uri=github.com/TimeWarpEngineering/timewarp-state)
[](https://www.nuget.org/packages/TimeWarp.State/)
[](https://www.nuget.org/packages/TimeWarp.State/)
[](https://twitter.com/intent/tweet?url=https://github.com/TimeWarpEngineering/timewarp-state)
[](https://dotnet.microsoft.com)
[](https://discord.gg/7F4bS2T)
[](https://twitter.com/intent/follow?screen_name=StevenTCramer)
[](https://twitter.com/intent/follow?screen_name=TheFreezeTeam1)
# TimeWarp.State
**TimeWarp.State** (previously known as Blazor-State) is a fully asynchronous state management library. The core package has no Blazor dependency, so console and other non-UI hosts can dispatch actions through the same store. Blazor components, JavaScript interop, and render subscriptions are in **TimeWarp.State.Blazor**. It handles both Reducers and Effects consistently using async Handlers.
By utilizing the TimeWarp.Mediator pipeline, TimeWarp.State enables a flexible, middleware-driven architecture for managing state, similar to the request-processing pipeline in ASP.NET. This approach allows developers to inject custom behaviors, such as logging, validation, and caching, directly into the state management flow.
Hosts consume **TimeWarp.Mediator 14-beta** via generated `AddGeneratedMediator()` / named pipelines — not MediatR and not reflection `AddMediator()`.
In addition to the core library, we offer **[TimeWarp.State.Blazor](/source/timewarp-state-blazor)** (components, JavaScript interop, render subscriptions), **[TimeWarp.State.Plus](/source/timewarp-state-plus)** (routing, persistence, action tracking; depends on TimeWarp.State.Blazor; package id unchanged), and **[TimeWarp.State.Telemetry](/source/timewarp-state-telemetry)** (OpenTelemetry action spans for the Aspire dashboard or any OTel backend). **[TimeWarp.State DevTools](/documentation/topics/devtools.md)** is a dev-only Blazor inspector (`AddTimeWarpStateDevTools()`) on top of those spans. It is the action log, state tree, and diff. It is not a production dependency. The [console sample](samples/07-console/overview.md) dispatches an action without Blazor. The [persistence sample](samples/05-persistence/readme.md) shows session storage and local storage with `[PersistentState]`. The [render control sample](samples/06-render-control/readme.md) shows `ShouldRender`, parameter checks, and `RegisterRenderTrigger`. The [telemetry sample](samples/04-telemetry/overview.md) wires the DevTools app into Aspire.
## Give a Star! :star:
If you find this project useful, please give it a star. Thanks!
## Getting Started
I recommend the [state and action handler sample](samples/00-state-action-handler) for a step-by-step guide to building a Blazor app with TimeWarp.State. The published docs are at [timewarpengineering.github.io/timewarp-state](https://timewarpengineering.github.io/timewarp-state/).
See full [documentation](https://timewarpengineering.github.io/timewarp-state/).
## Installation
```console
dotnet add package TimeWarp.State
dotnet add package TimeWarp.State.Blazor
dotnet add package TimeWarp.State.Plus
dotnet add package TimeWarp.State.Telemetry
```
Blazor hosts call `AddTimeWarpState` and `AddTimeWarpStateBlazor`. Console hosts call `AddTimeWarpState` only. See [Migrate to 12.0.0-beta.10](documentation/migrations/migration12.0.0-beta.10.md).
Check out the latest NuGet packages on the [TimeWarp Enterprises NuGet page](https://www.nuget.org/profiles/TimeWarp.Enterprises).
* [TimeWarp.State](https://www.nuget.org/packages/TimeWarp.State/) [](https://www.nuget.org/packages/TimeWarp.State/)
* [TimeWarp.State.Blazor](https://www.nuget.org/packages/TimeWarp.State.Blazor/) [](https://www.nuget.org/packages/TimeWarp.State.Blazor/)
* [TimeWarp.State.Plus](https://www.nuget.org/packages/TimeWarp.State.Plus/) [](https://www.nuget.org/packages/TimeWarp.State.Plus/)
* [TimeWarp.State.Telemetry](https://www.nuget.org/packages/TimeWarp.State.Telemetry/) [](https://www.nuget.org/packages/TimeWarp.State.Telemetry/)
## JavaScript dispatch
JavaScript can dispatch actions with `timeWarpState.DispatchRequest(name, request)`. It is opt-in: allow each action explicitly, everything else is rejected.
```csharp
builder.Services.AddJavaScriptDispatch(b => b.Allow());
```
See [Enable JavaScript interop](documentation/topics/enable-javascript-interop.md).
## Action catalog
Mark user-facing actions with `[CatalogAction]` to enumerate and execute them at runtime, for example from a Ctrl-K command palette or as agent tools:
```csharp
public static class AddPasskeyActionSet
{
[CatalogAction(Description = "Add a passkey to the signed-in account.", Permissions = ["credentials.write"])]
public sealed class Action : IAction
{
public Action(string label) { Label = label; }
public string Label { get; }
}
}
```
```csharp
builder.Services.AddActionCatalog(typeof(AssemblyMarker).Assembly);
ActionCatalogEntry entry = actionCatalog.Find("Credentials.AddPasskey")!;
await entry.Execute(store, ["Laptop"]);
```
The source generator emits a per-assembly registry with name, description, permissions, visibility, parameters and input schema, plus a reflection-free `Execute`. It is opt-in: unmarked actions are never cataloged. Permissions are opaque ids that the consumer enforces; `[TrackAction]` (busy indicator) is unrelated. See [Action catalog](documentation/topics/action-catalog.md).
## Releases
View the [Release Notes](https://timewarpengineering.github.io/timewarp-state/ReleaseNotes/Release11.0.0.html) for detailed information on each release.
## Unlicense
[](https://unlicense.org)
This project is licensed under the [Unlicense](https://unlicense.org).
## Contributing
Your contributions are welcome! Before starting any work, please open a [discussion](https://github.com/TimeWarpEngineering/timewarp-state/discussions).
Help with the [documentation](https://timewarpengineering.github.io/timewarp-state/) is also greatly appreciated.
## Contact
If you have an issue and don't receive a timely response, feel free to reach out on our [Discord server](https://discord.gg/A55JARGKKP).
[](https://discord.gg/7F4bS2T)