Microsoft's latest release of Aspire 13.3 brings exciting new features that streamline deployment, improve frontend development, and introduce powerful debugging tools. From a new destroy command to native Kubernetes support and browser log capture, this update is packed with changes that developers should explore. Below, we break down the key updates in a Q&A format to help you understand what's new and how it impacts your workflows.
1. What is the new 'aspire destroy' command and how does it work?
The aspire destroy command is a brand-new feature in Aspire 13.3 designed to tear down deployments across multiple environments, including Azure, Kubernetes, and Docker Compose. Instead of manually cleaning up resources after testing or production, you can now run a single command to remove all provisioned infrastructure. This helps prevent resource waste and ensures a clean state for the next deployment. The command intelligently identifies deployed resources and safely deletes them, handling dependencies and order. It's particularly useful for CI/CD pipelines where environments are created and destroyed frequently. Developers should test it in non-production first, especially when using Kubernetes clusters, to avoid accidental removal of critical services.
2. How does Aspire 13.3 improve Kubernetes support?
This release introduces native Kubernetes deployment as a preview feature. Previously, deploying to Kubernetes required additional tooling or manual steps, but now Aspire 13.3 can directly generate and apply Kubernetes manifests. This simplifies the transition from local development to cluster deployment. The feature supports common patterns like Deployments, Services, and ConfigMaps. It's built on top of the existing deployment model, so you can reuse your Aspire configuration. Note that this is a preview—Microsoft encourages feedback but advises caution in production environments. To try it, enable the feature flag and ensure your cluster context is set correctly. This move makes Aspire a more complete solution for cloud-native development.
3. What frontend updates are included for JavaScript developers?
JavaScript developers get a major boost with first-class publishing support for Next.js and Vite. Aspire 13.3 can now automatically detect these frameworks and configure the deployment pipeline accordingly. For Next.js, it handles server-side rendering and static assets; for Vite, it optimizes build outputs. This means you can deploy modern frontends without writing custom Dockerfiles or complex YAML. Additionally, the browser log capture feature streams client-side logs directly into your Aspire console, making it easier to debug issues in real time. This is especially helpful for single-page applications where server logs don't show UI bugs. Together, these updates make Aspire a more attractive choice for full-stack development teams.
4. How does the new browser log capture feature work?
The browser log capture feature in Aspire 13.3 automatically collects console logs, errors, and warnings from the client's browser and forwards them to the Aspire logging system. When you enable it, a small JavaScript snippet is injected into your frontend application that captures log entries and sends them via a WebSocket connection. This gives you a unified view of both server and client logs in the Aspire dashboard. It's default-enabled for new projects, but you can disable it if privacy or performance concerns arise. The feature supports filtering by log level and source, allowing developers to pinpoint client-side issues without asking users to inspect their browser console. It works with any framework, but is especially seamless with the new Next.js and Vite integrations.
5. What is the container tunnel and why is it now enabled by default?
The container tunnel is a networking feature that provides a secure, internal proxy between your local machine and containers running in Azure Container Apps or Kubernetes. In Aspire 13.3, it is enabled by default to simplify development workflows. Previously, developers had to manually configure port forwarding to access services running in the cloud. Now, once you deploy, Aspire sets up a tunnel that maps remote service endpoints to local ports, allowing you to test against a live environment as if it were local. This is especially useful for debugging microservices that depend on cloud-native resources like databases or message queues. The tunnel is encrypted and automatically cleaned up when you stop debugging. However, be aware that it uses additional network bandwidth and may incur costs if left running.
6. What breaking changes should developers watch out for in Aspire 13.3?
This release includes several breaking changes that developers need to review. Key changes include: the deprecation of the old `aspire deploy` command in favor of the new destroy-aware workflow, modifications to the resource manifest schema (especially for Kubernetes), and the removal of the legacy container tunnel configuration flag (since it's now default). Additionally, some environment variable names have been updated for consistency. The Microsoft documentation provides a full migration guide, but common steps include updating your Aspire project files and testing your pipeline after upgrading the CLI. If you use custom Dockerfiles, check the base image version as Aspire 13.3 expects newer SDKs. Also, note that the preview Kubernetes feature may require updates to your deployment scripts. Plan a testing phase before rolling out to production.
7. How does Aspire 13.3 affect deployment workflows?
Aspire 13.3 streamlines deployment workflows by introducing the destroy command and native Kubernetes support, reducing manual steps. For CI/CD, you can now script a full lifecycle: build, deploy, test, and destroy without leaving the Aspire ecosystem. The default container tunnel also means developers can verify deployments in minutes without extra networking setup. The frontend publishing improvements eliminate the need to maintain separate build configurations for Next.js or Vite projects. However, the breaking changes require updating existing pipelines—especially if you rely on deprecated commands or custom manifests. Overall, the focus is on consistency and automation, making Aspire a more cohesive tool for both development and operations teams. Expect shorter iteration cycles and fewer environment-related bugs.