npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@microsoft/aspire-cli

v13.4.6

Published

The Aspire CLI lets you build, run, manage, and deploy distributed applications in a terminal.

Readme

@microsoft/aspire-cli

CI Tests

The Aspire CLI, published for npm-based installs.

What is Aspire?

Your stack, streamlined. Aspire is a multi-language, code-first orchestration and observability layer for building, running, and deploying distributed applications.

Use an AppHost to describe how services, frontends, containers, databases, caches, and connections fit together in code. The Aspire CLI runs the whole app locally, opens the OpenTelemetry dashboard for logs, traces, metrics, and health checks, and carries the same app model into deployment.

A simple app definition

You describe your app in a TypeScript AppHost (apphost.mts). The example below runs an Express API and a Vite frontend, exposes the API over HTTP, and wires the frontend to it:

import { createBuilder } from './.aspire/modules/aspire.mjs';

const builder = await createBuilder();

// Run the Express API and expose its HTTP endpoint externally.
const app = await builder
  .addNodeApp("app", "./api", "src/index.ts")
  .withHttpEndpoint({ env: "PORT" })
  .withExternalHttpEndpoints();

// Run the Vite frontend after the API and inject the API URL for local proxying.
const frontend = await builder
  .addViteApp("frontend", "./frontend")
  .withReference(app)
  .waitFor(app);

// Bundle the frontend build output into the API container for publish/deploy.
await app.publishWithContainerFiles(frontend, "./static");

await builder.build().run();

Each builder call returns a promise, so await is used to get the resource before referencing it from another resource. aspire run builds and launches everything, then opens the dashboard.

Add backing services

Resources like databases and caches are added the same way and connected with withReference. waitFor holds dependents until the resource is ready:

import { createBuilder } from './.aspire/modules/aspire.mjs';

const builder = await createBuilder();

const postgres = await builder.addPostgres("postgres");
const db = await postgres.addDatabase("db");

const cache = await builder.addRedis("cache");

await builder
  .addNodeApp("api", "./api", "src/index.ts")
  .withHttpEndpoint({ env: "PORT" })
  .withExternalHttpEndpoints()
  .withReference(db)
  .withReference(cache)
  .waitFor(db)
  .waitFor(cache);

await builder.build().run();

addPostgres and addRedis become available once the matching integrations are installed with aspire add postgresql and aspire add redis.

Install

This package requires Node.js 20 or later.

npm install -g @microsoft/aspire-cli

Then verify the install:

aspire --version
aspire --help

Start from a repo with one or more app projects:

aspire init
aspire run

The native platform packages are installed through npm optional dependencies. Do not install this package with optional dependencies disabled, or the aspire launcher will not be able to find the native CLI binary.

Standalone dashboard

The Aspire dashboard shows logs, traces, and metrics for any app that exports OpenTelemetry, even without an AppHost. Start one in a single command:

aspire dashboard run

This launches the dashboard with an OTLP endpoint your apps can point at via OTEL_EXPORTER_OTLP_ENDPOINT. Use aspire dashboard run --help to see options such as --frontend-url, --otlp-grpc-url, and --allow-anonymous.

Update

npm install -g @microsoft/aspire-cli@latest

If you run aspire update --self from an npm install, the CLI points you back to this npm update command.

Learn more