.NET Aspire 13.2: Expanding the Ecosystem with TypeScript AppHost and AI-Ready CLI

Microsoft has released .NET Aspire 13.2, introducing a series of updates designed to lower the barrier for non-.NET developers and streamline the local development experience. The most significant addition is the preview of TypeScript AppHost support, which allows developers to orchestrate cloud-native applications using idiomatic TypeScript instead of C#.

Breaking the Language Barrier: TypeScript AppHost Support

For the first time, Aspire 13.2 allows teams to define their application architecture using TypeScript. This means developers who primarily operate in JavaScript and TypeScript can now adopt Aspire’s orchestration capabilities without needing to move their AppHost authoring into C#.

Despite the change in syntax, the underlying application model remains the same. Users still define resources, references, startup dependencies, endpoints, and deployment intent in code. The core benefits—including the Aspire dashboard, service discovery behavior, health checks, and deployment artifacts—remain consistent across both C# and TypeScript implementations.

How the TypeScript AppHost Works

The TypeScript AppHost operates as a guest process. The Aspire CLI transpiles the TypeScript code and manages communication via JSON-RPC with the .NET orchestration host, which continues to handle service management and the developer dashboard. When developers use the aspire add command for integrations, the CLI downloads the necessary NuGet package, inspects the .NET assembly, and generates a corresponding TypeScript SDK in a .modules/ folder.

Prerequisites for TypeScript AppHost

• Node.js: Version 20 or later is required as the runtime.
• Container Runtime: An OCI-compatible runtime such as Podman or Docker Desktop.
• Aspire CLI: The standalone executable must be installed.
• .NET 10 SDK: Only required if the application graph includes .NET projects or if the AppHost is written in C#.

Enhanced CLI and Developer Experience

The Aspire 13.2 release focuses heavily on making the CLI more “language-aware.” The aspire new and aspire init commands now offer improved scaffolding for language-specific full-stack starter apps. Developers can now create starters for C#, TypeScript, and Python.

the release introduces an AI-focused CLI designed specifically for coding agents, making local development more streamlined for both human developers and AI tools. Other improvements include dashboard updates and revised integrations to support a more robust cloud-native foundation.

Getting Started with Aspire 13.2

Users can upgrade to the latest version using the aspire update --self command to update the CLI, or aspire update to update the apphost packages. For those starting fresh, the official Aspire blog highlights two new TypeScript templates:

• aspire-ts-empty: For a clean TypeScript AppHost.
• aspire-ts-starter: A starter project featuring Express, and React.

Frequently Asked Questions

Does the TypeScript AppHost change how service discovery works?

No. You still get the same service discovery behavior, health checks, and dashboard experience as the C# AppHost.

How do I add Aspire to an existing TypeScript codebase?

Navigate to your workspace and run aspire init --language typescript followed by aspire run. This will generate the apphost.ts, aspire.config.json, and necessary configuration files.

Looking Ahead

By decoupling the orchestration layer from a strict C# requirement, Microsoft is positioning .NET Aspire as a general-purpose orchestrator for polyglot cloud-native applications. The introduction of AI-agent CLI support further suggests a move toward autonomous development workflows, where the infrastructure definition is as flexible as the application code itself.