Repository navigation
Extension ClearScript
Stateflows.Extensions.ClearScript lets State Machine hooks, Activity actions, and reusable Actions execute scripts through Microsoft ClearScript. It provides convenience registration methods and configurable scripted behavior implementations; it does not select or install a JavaScript engine for the host.
Install Stateflows.Extensions.ClearScript and a ClearScript engine implementation supported by your application. Supply a factory that returns an IScriptEngine:
using Microsoft.ClearScript;
using Microsoft.ClearScript.V8;
using Stateflows;
services.AddStateflows(stateflows => stateflows
.AddClearScript(_ =>
Task.FromResult<IScriptEngine>(new V8ScriptEngine())));This example uses Microsoft.ClearScript.V8; install that package and deploy its platform-specific native dependencies. A different engine can be supplied through the same factory. The extension creates an engine for each script execution and disposes it after execution. If no factory has been registered, script execution throws a StateflowsException.
For example, a State Machine state can run a script on entry:
using Stateflows;
using Stateflows.StateMachines;
public sealed class Order : IStateMachine
{
public static void Build(IStateMachineBuilder machine) => machine
.AddInitialState("Waiting", state => state
.AddOnEntry_ClearScript("Console.WriteLine('Entered Waiting');")
.AddTransition<Confirm>("Confirmed"))
.AddFinalState("Confirmed");
}The extension also provides _ClearScript methods for state exit and composite initialization/finalization, transition and deferral guards/effects, and Activity actions. For reusable Actions, AddAction_ClearScript registers a named script as the Action implementation. See the extension source for the supported builder overloads.
The base script contexts expose behaviorContext and executionContext; State Machine hooks also expose stateContext, and Action implementations expose actionContext. Console is added as a host type. Treat scripts as trusted application code: the script can access the host objects deliberately exposed to it, so do not execute untrusted script text.
Home page Support Code licensed under an MIT-style License. Documentation licensed under CC BY 4.0. © by Mikołaj Milewski, 2026
Overview
Installation
Runtimes
Orleans runtime
Concepts
Events and Structural Events
Messaging Patterns
Validation
Scheduling
Observability
Behaviors
Behavior Values
Dependency Injection
Behavioral Groups
State Machines
Concepts
State Identity
In-State Event Deferrals
Evaluation of Transitions
Exception Handling
Building blocks
Regions
States
State
Composite State
Orthogonal State
Final State
Pseudostates
Choice
Junction
Fork
Join
History
Transitions
Transition
Default Transition
Internal Transition
Activities
Concepts
Exception Handling
Implicit Fork and Join
Tokens
Building blocks
Nodes
Action Node
Decision Node
Merge Node
Initial Node
Final Node
Input Node
Output Node
Fork Node
Join Node
Accept Event Action Node
Send Event Action Node
Publish Event Action Node
Time Event Action Node
Data Store Node
Structured Activity Node
Iterative Activity Node
Parallel Activity Node
Flows
Data Flow
Control Flow
Actions
Entities
Fields
Mutations
Projections
Extensions
ClearScript
FluentValidation
JSON definitions
Minimal APIs
OneOf
OpenTelemetry
PlantUML
Scheduling