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

msw-azure-kusto

v1.1.0

Published

TypeScript Azure Data Explorer (Kusto) HTTP emulator for local testing with MSW.

Readme

msw-azure-kusto

TypeScript Azure Data Explorer (Kusto) HTTP emulator for local testing with MSW.

Disclaimer: Primarily coded by Codex and Opus, this emulator is not feature complete. Only inline ingestion and URI-based CSV ingestion.

Usage

  1. Install msw (https://mswjs.io/docs/getting-started)
  2. Install msw-azure-kusto
  3. Import handlers from msw-azure-kusto and pass them to your MSW setup

CLI emulator

You can run a standalone local Kusto emulator with npx:

npx msw-azure-kusto --port 80 --dashboard 4000

Flags:

  • --port (-p) HTTP port for the Kusto emulator endpoints.
  • --dashboard Optional dashboard UI port.

Install

npm install msw-azure-kusto

Setup

import { setupServer } from "msw/node";
import { handlers } from "msw-azure-kusto";

export const server = setupServer(...handlers());

azure-kusto-data client example

msw-azure-kusto emulates Kusto REST endpoints such as https://<cluster>/v1/rest/mgmt and https://<cluster>/v2/rest/query. Use your normal azure-kusto-data client setup and point it at a mocked cluster host.

import { Client, KustoConnectionStringBuilder } from "azure-kusto-data";
import { setupServer } from "msw/node";
import { handlers } from "msw-azure-kusto";

const server = setupServer(...handlers());
server.listen();

const cluster = "https://example.kusto.windows.net";
const kcsb = KustoConnectionStringBuilder.withTokenProvider(cluster, async () => "mock-token");
const client = new Client(kcsb);

await client.executeMgmt("Samples", ".create table StormEvents (EventId:int, State:string, Damage:int)");
await client.executeMgmt("Samples", ".ingest inline into table StormEvents <| 1,WA,10\n2,CA,20\n3,WA,5");

const response = await client.executeQuery(
  "Samples",
  "StormEvents | where State == 'WA' | project EventId, State",
);

const primary = response.primaryResults[0];
const json = primary?.toJSON() as { data: Array<Record<string, unknown>> };
console.log(json.data);

await client.close();
server.close();

Supported hosts:

  • https://*.kusto.windows.net
  • https://kusto.local

Snapshot tests

Snapshots are in src/tests/snapshots/commands.test.snapshot.ts, based on .kql files in src/tests/commands.

Set CLUSTER in your shell or .env before running command tests, for example:

export CLUSTER="https://kusto.local"

Run snapshot-backed command tests

node --run build
node --env-file-if-exists=.env --test dist/tests/commands.test.js

To run only medium guide command cases:

node --env-file-if-exists=.env --test dist/tests/commands.test.js --test-name-pattern "command - medium-guide"

Update snapshots

node --run build
node --run test-update-snapshots