open-index/open-npm huggingface dataset:
npm package: @microsoft/teams.graph-endpoints-beta
Description: <p>     <a href="https://www.npmjs.com/package/@microsoft/teams.graph-endpoints-beta" target="_blank">         <img src="https://img.shields.io/npm/v/@microsoft/teams.graph-endpoints-beta/latest" />     </a>     <a href="https://www.npmjs.com/package/@mic
Latest version: 2.0.7

# Teams: Graph Endpoints, Beta Schema

<p>
    <a href="https://www.npmjs.com/package/@microsoft/teams.graph-endpoints-beta" target="_blank">
        <img src="https://img.shields.io/npm/v/@microsoft/teams.graph-endpoints-beta/latest" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.graph-endpoints-beta?activeTab=code" target="_blank">
        <img src="https://img.shields.io/bundlephobia/min/@microsoft/teams.graph-endpoints-beta" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.graph-endpoints-beta?activeTab=dependencies" target="_blank">
        <img src="https://img.shields.io/librariesio/release/npm/@microsoft/teams.graph-endpoints-beta" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.graph-endpoints-beta" target="_blank">
        <img src="https://img.shields.io/npm/dw/@microsoft/teams.graph-endpoints-beta" />
    </a>
    <a href="https://microsoft.github.io/teams-sdk" target="_blank">
        <img src="https://img.shields.io/badge/📖 docs-open-blue" />
    </a>
</p>

A collection of strongly typed request configuration builders for Microsoft Graph preview endpoints, designed to be used
together with <a href="https://www.npmjs.com/package/@microsoft/teams.graph" target="_blank">@microsoft/teams.graph</a>.

The code in this package is based on the Graph schema published in commit <a href="https://github.com/microsoftgraph/msgraph-metadata/blob/08ecd2f8597b074d8e65927900fc8a63ca39c8a7/openapi/beta/openapi.yaml">08ecd2f</a>.

Use this package if you need to call Microsoft Graph APIs that are still in preview. Note that these APIs are subject to
change. We don't recommend that you use them in your production apps.

To use APIs that are generally available, please refer to <a href="https://www.npmjs.com/package/@microsoft/teams.graph-endpoints" target="_blank">@microsoft/teams.graph-endpoints</a>.

<a href="https://microsoft.github.io/teams-sdk" target="_blank">
    <img src="https://img.shields.io/badge/📖 Getting Started-blue?style=for-the-badge" />
</a>

## Install

```bash
$: npm install @microsoft/teams.graph-endpoints-beta
```

## Links

- [Microsoft Graph REST API beta endpoint reference](https://learn.microsoft.com/en-us/graph/api/overview?view=graph-rest-beta)

## Dependencies

- None
npm package: @microsoft/teams.mcp
Description: <p>     <a href="https://www.npmjs.com/package/@microsoft/teams.mcp" target="_blank">         <img src="https://img.shields.io/npm/v/@microsoft/teams.mcp/latest" />     </a>     <a href="https://www.npmjs.com/package/@microsoft/teams.mcp?activeTab=code" t
Latest version: 2.0.7

# Teams: MCP (Model Context Protocol)

<p>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcp" target="_blank">
        <img src="https://img.shields.io/npm/v/@microsoft/teams.mcp/latest" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcp?activeTab=code" target="_blank">
        <img src="https://img.shields.io/bundlephobia/min/@microsoft/teams.mcp" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcp?activeTab=dependencies" target="_blank">
        <img src="https://img.shields.io/librariesio/release/npm/@microsoft/teams.mcp" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcp" target="_blank">
        <img src="https://img.shields.io/npm/dw/@microsoft/teams.mcp" />
    </a>
    <a href="https://microsoft.github.io/teams-sdk" target="_blank">
        <img src="https://img.shields.io/badge/📖 docs-open-blue" />
    </a>
</p>

https://modelcontextprotocol.io/introduction

<a href="https://microsoft.github.io/teams-sdk" target="_blank">
    <img src="https://img.shields.io/badge/📖 Getting Started-blue?style=for-the-badge" />
</a>

## Install

```bash
$: npm install @microsoft/teams.mcp
```

## Dependencies

- [`@modelcontextprotocol/sdk`](https://www.npmjs.com/package/@modelcontextprotocol/sdk)
npm package: @microsoft/teams.mcpclient
Description: <p>     <a href="https://www.npmjs.com/package/@microsoft/teams.mcpclient" target="_blank">         <img src="https://img.shields.io/npm/v/@microsoft/teams.mcpclient/latest" />     </a>     <a href="https://www.npmjs.com/package/@microsoft/teams.mcpclient
Latest version: 2.0.7

# Teams: mcpclientpluginplugin

<p>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcpclient" target="_blank">
        <img src="https://img.shields.io/npm/v/@microsoft/teams.mcpclient/latest" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcpclient?activeTab=code" target="_blank">
        <img src="https://img.shields.io/bundlephobia/min/@microsoft/teams.mcpclient" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcpclient?activeTab=dependencies" target="_blank">
        <img src="https://img.shields.io/librariesio/release/npm/@microsoft/teams.mcpclient" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.mcpclient" target="_blank">
        <img src="https://img.shields.io/npm/dw/@microsoft/teams.mcpclient" />
    </a>
    <a href="https://microsoft.github.io/teams-sdk" target="_blank">
        <img src="https://img.shields.io/badge/📖 docs-open-blue" />
    </a>
</p>

High level MCP Client Plugin which allows connecting to various sse servers and consume exposed tools.

<a href="https://microsoft.github.io/teams-sdk" target="_blank">
    <img src="https://img.shields.io/badge/📖 Getting Started-blue?style=for-the-badge" />
</a>

## Install

```bash
npm install @microsoft/teams.mcpclient
```

## Overview

The MCP Client Plugin enables seamless integration with Model Context Protocol (MCP) servers through SSE (Server-Sent Events). It allows you to connect to various MCP servers and consume their exposed tools within your Teams.js applications.

## Usage

```typescript
import { ChatPrompt } from "@microsoft/teams.ai";
import { McpClientPlugin } from "@microsoft/teams.mcpclient";

const prompt = new ChatPrompt(
    {
        instructions: "You are a helpful assistant.",
        model: yourModel,
    },
    [new McpClientPlugin()],
).usePlugin("mcpClient", { url: "http://your-mcp-server/mcp" });
```

## Features

- 🔌 Automatic tool discovery from MCP servers
- 💾 Optional caching of tool parameters (if you'd like to avoid the discovery call or only pass in a subset of tools)
npm package: @microsoft/teams.openai
Description: <p>     <a href="https://www.npmjs.com/package/@microsoft/teams.openai" target="_blank">         <img src="https://img.shields.io/npm/v/@microsoft/teams.openai/latest" />     </a>     <a href="https://www.npmjs.com/package/@microsoft/teams.openai?activeTa
Latest version: 2.0.7

# Teams: OpenAI

<p>
    <a href="https://www.npmjs.com/package/@microsoft/teams.openai" target="_blank">
        <img src="https://img.shields.io/npm/v/@microsoft/teams.openai/latest" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.openai?activeTab=code" target="_blank">
        <img src="https://img.shields.io/bundlephobia/min/@microsoft/teams.openai" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.openai?activeTab=dependencies" target="_blank">
        <img src="https://img.shields.io/librariesio/release/npm/@microsoft/teams.openai" />
    </a>
    <a href="https://www.npmjs.com/package/@microsoft/teams.openai" target="_blank">
        <img src="https://img.shields.io/npm/dw/@microsoft/teams.openai" />
    </a>
    <a href="https://microsoft.github.io/teams-sdk" target="_blank">
        <img src="https://img.shields.io/badge/📖 docs-open-blue" />
    </a>
</p>

OpenAI model implementations to be used with `@microsoft/teams.ai`. Supports all OpenAI-like API models.

<a href="https://microsoft.github.io/teams-sdk" target="_blank">
    <img src="https://img.shields.io/badge/📖 Getting Started-blue?style=for-the-badge" />
</a>

## Install

```bash
$: npm install @microsoft/teams.openai
```

## Dependencies

- [`openai`](https://www.npmjs.com/package/openai)
npm package: @microsoft/tiktokenizer
Description: Tokenizer for OpenAI large language models.
Author: Microsoft Corporation
Latest version: 1.0.10

# Tokenizer

This is a Typescript implementation of byte pair encoding(BPE) tokenizer for OpenAI LLMs, it's based on open sourced rust implementation in the [OpenAI tiktoken](https://github.com/openai/tiktoken). It's valuable to run prompt tokenization in Nodejs or web browser before feeding prompt into a LLM.


# How to use

The npm package `@microsoft/tiktokenizer` is published in [NPMJS Packages Registry](https://www.npmjs.com/package/@microsoft/tiktokenizer).
Install the npm package in your project:

```bash
npm install @microsoft/tiktokenizer
```

Example Typescript code to use @microsoft/tiktokenizer in your code:
```typescript
import {
    createByModelName
  } from '@microsoft/tiktokenizer';

const IM_START = "
";
const IM_END = "
";
const specialTokens: ReadonlyMap<string, number> = new Map([
  [IM_START, 100264],
  [IM_END, 100265],
]);

const str = "
Hello World
";
let tokenizer = null;
const createTokenizer = async () => {
    tokenizer = await createByModelName("gpt-3.5-turbo", specialTokens);
    var out1 = tokenizer.encode(str, Array.from(specialTokens.keys()));
    console.log(out1);
    var out2 = tokenizer.encodeTrimSuffix(str, 3, Array.from(specialTokens.keys()));
    console.log(out2.tokenIds);
    console.log(out2.text);
    var out3 = tokenizer.encodeTrimPrefix(str, 3, Array.from(specialTokens.keys()));
    console.log(out3.tokenIds);
    console.log(out3.text);
}
createTokenizer();

```
In production setting, you should pre-download the BPE rank file and call `createTokenizer` API to avoid downloading the BPE rank file on the fly.
You can find the model to encoder and encoder to BPE rank file link mapping in: [tokenizerBuilder.ts](https://github.com/microsoft/Tokenizer/blob/main/tokenizer_ts/src/tokenizerBuilder.ts#L15-L55).

# Contributing

We welcome contributions. Please follow [this guideline](https://github.com/microsoft/Tokenizer/blob/main/CONTRIBUTING.md).

# Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft 
trademarks or logos is subject to and must follow 
[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.
npm package: @microsoft/ts-command-line
Description: (Please use "@rushstack/ts-command-line" instead.)
Latest version: 5.0.1

# @microsoft/ts-command-line

> Please use [@rushstack/ts-command-line](https://www.npmjs.com/package/@rushstack/ts-command-line) instead of this package.

IMPORTANT: This package has moved under the `@rushstack` NPM scope.

```
  OLD NAME: @microsoft/ts-command-line (4.3.10)
  NEW NAME: @rushstack/ts-command-line (4.3.11)
```

The new package's CHANGELOG.md preserves version history from before the rename.

The new package starts with a SemVer PATCH increment, since no code has changed.

To learn about the Rush Stack project, please visit https://rushstack.io/
npm package: @microsoft/tsdoc
Description: A parser for the TypeScript doc comment syntax
Latest version: 0.16.0

# @microsoft/tsdoc

<div>
  <br />
  <a href="https://tsdoc.org/">
    <img width="200" src="https://tsdoc.org/images/site/tsdoc.svg">
  </a>
  <p />
</div>

This library is the reference implementation of a parser for the TSDoc syntax.  Using this library is an easy way to ensure that your tool is 100% compatible with the standard.


##  What is TSDoc?

**TSDoc** is a proposal to standardize the doc comments used in [TypeScript](http://www.typescriptlang.org/) source files.  It allows different tools to extract content from comments without getting confused by each other's syntax.   The **TSDoc** notation looks pretty familiar:

```typescript
export class Statistics {
  /**
   * Returns the average of two numbers.
   *
   * @remarks
   * This method is part of the {@link core-library#Statistics | Statistics subsystem}.
   *
   * @param x - The first input number
   * @param y - The second input number
   * @returns The arithmetic mean of `x` and `y`
   *
   * @beta
   */
  public static getAverage(x: number, y: number): number {
    return (x + y) / 2.0;
  }
}
```

## Give it a try!

Check out the [TSDoc Playground](https://tsdoc.org/play) for a cool live demo of our parser!


## API Usage

The [api-demo](https://github.com/microsoft/tsdoc/tree/main/api-demo) folder on GitHub illustrates how
to invoke the TSDoc parser.

A separate NPM package [`@microsoft/tsdoc-config`](https://www.npmjs.com/package/@microsoft/tsdoc-config)
is used for loading the **tsdoc.json** file.


## Get involved

The **TSDoc** project is actively evolving.  Please visit the website for the latest documentation, instructions for building/debugging the projects, and other resources:

https://tsdoc.org/
npm package: @microsoft/typescript-etw
Description: ETW logging native Node.js module for the TypeScript project
Author: Microsoft
Latest version: 0.1.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @microsoft/typescript-etw

**@microsoft/typescript-etw** is a native Node.js module for logging ETW events for the TypeScript project.

## Compatibility

ETW is a Windows technology, so this module only works on Windows (Win7 or later). The module is built using the N-API interface and works on Node.js 8.9 or later. (See https://nodejs.org/docs/v8.9.0/api/n-api.html)

## Installing

Install from npm via: `npm install @microsoft/typescript-etw`

Since this dependency only supports Windows, consider using the `--save-optional` flag to add this as an optional dependency or `--no-save` to omit this as a listed dependency altogether.

The module will build from source using node-gyp. Use the flag `--target_arch=ia32` or `--target_arch=x64` to target a specific architecture.

If you would like to take advantage of types for this package information, install them from DefinitelyTyped via: `npm install @types/microsoft__typescript-etw --save-dev`

This will allow you to compile your code with types even if the optional dependency was not installed.

## Usage

Be aware that calling `require` on this package may return `undefined` if it fails the compatibility checks in `index.js`. It may also throw an exception if it is an optional dependency that is not installed. This example shows a way to `require` this module that accounts for both cases:

```javascript
var etw;
try {
    etw = require('typescript-etw');
} catch (e) {
    // Optional package not found
    etw = undefined;
}
```

Then you can log events conditionally:

```javascript
if (etw) etw.logInfoEvent('message');
```

## Misc

See the `notes.txt` file for details on the implementation, TODOs, etc.

## Contributing

This project welcomes contributions and suggestions.  Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
npm package: @microsoft/useragent-plugin-keyvault
Description: A CryptoSuite for intercepting keyvault requests.
Author: Microsoft Corporation
Latest version: 0.0.1-alpha.0


# Contributing

This project welcomes contributions and suggestions.  Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
npm package: @microsoft/useragent-plugin-secp256k1
Description: User agent plugin to support secp256k1 in the browser as a W3C cryptographic API plugin.
Author: Microsoft Corporation
Latest version: 1.0.13

[![Build Status](https://decentralized-identity.visualstudio.com/Core/_apis/build/status/Microsoft%20User%20Agent%20Plugin%20SECP256K1%20(Build)?branchName=master)](https://decentralized-identity.visualstudio.com/Core/_build/latest?definitionId=25&branchName=master)

# User Agent SECP256K1 Plugin

User agent plugin to support secp256k1 in the browser as a W3C cryptographic API plugin.

# Contributing

This project welcomes contributions and suggestions.  Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
npm package: @microsoft/vscode-azext-azureappservice
Description: Common tools for developing Azure App Service extensions for VS Code
Author: Microsoft Corporation
Latest version: 4.2.4

# VSCode Azure SDK for Node.js - App Service Tools (Preview)

This package provides common Azure App Service elements for VS Code extensions.

All functionality for this package is built around the `SiteClient`, a wrapper of a `WebSiteManagementClient` for use with a specific Site. It reduces the number of arguments needed for every call and automatically ensures the 'slot' method is called when appropriate. Support for all methods on the `WebSiteManagementClient` are being added on an as-needed basis.

On top of that, this package provides functionality specifically designed for use in VS Code, including but not limited to:
* createFunctionApp/createWebApp: Guides the user through creation of a Function App or Web App.
* deploy: Automatically detects a site's deployment source and deploys based on that.
* startStreamingLogs: Creates a stream of the Site's logs to the outputChannel in VS Code.

> NOTE: This package throws a `UserCancelledError` if the user cancels an operation. This error should be handled appropriately by your extension.

## License
[MIT](LICENSE.md)
npm package: @microsoft/vscode-azext-dev
Description: Common dev dependency tools for developing Azure extensions for VS Code
Author: Microsoft Corporation
Latest version: 3.0.1
Deprecated: This package has been deprecated in favor of @microsoft/vscode-azext-eng

# VSCode Azure SDK for Node.js - Dev Dependency Tools (Preview)

This package provides common Azure dev dependency elements for VS Code extensions

## License
[MIT](LICENSE.md)
npm package: @microsoft/vscode-fabric-api
Description: Contains APIs for interacting with Microsoft Fabric and VS Code Fabric extensions
Author: Microsoft Corporation
Latest version: 0.35.6

# @microsoft/vscode-fabric-api

APIs for interacting with Microsoft Fabric and VS Code Fabric extensions.

## Overview

This package provides TypeScript/JavaScript APIs for building extensions and integrations with Microsoft Fabric in Visual Studio Code. It defines public contracts and interfaces for extension authors and consumers, enabling safe and consistent interaction with Fabric services and extension points.

## Features

- Public API contracts for Microsoft Fabric VS Code extensions
- TypeScript type definitions for strong typing and IntelliSense
- Designed for use by both core and satellite Fabric extensions
- No implementation logic—contracts only

## Installation

```sh
npm install @microsoft/vscode-fabric-api
```

## Usage

Import the API contracts in your extension or application:

```ts
import { IFabricExtensionManager } from '@microsoft/vscode-fabric-api';
// ...other imports as needed
```

Refer to the documentation and code comments for details on available interfaces and usage patterns.

## Documentation

- [Extensibility Overview](https://github.com/microsoft/vscode-fabric/blob/main/docs/extensibility-overview.md)
- [Architecture Overview](https://github.com/microsoft/vscode-fabric/blob/main/docs/architecture-overview.md)

## License

[MIT](LICENSE)
npm package: @microsoft/vscode-fabric-util
Description: Contains utilities for interacting with Microsoft Fabric and VS Code Fabric extensions
Author: Microsoft Corporation
Latest version: 0.35.5

# @microsoft/vscode-fabric-util

Utilities for interacting with Microsoft Fabric and VS Code Fabric extensions.

## Overview

This package provides utility functions and helpers for building extensions and integrations with Microsoft Fabric in Visual Studio Code. It is designed to be used alongside the core API package to simplify common tasks and promote code reuse across Fabric-related projects.

## Features

- Utility functions for telemetry, error handling, logging, and more
- Helpers for working with URIs, file systems, and configuration
- TypeScript type definitions for strong typing and IntelliSense
- Designed for use by both core and satellite Fabric extensions

## Installation

```sh
npm install @microsoft/vscode-fabric-util
```

## Usage

Import the utilities in your extension or application:

```ts
import { TelemetryService, FabricError } from '@microsoft/vscode-fabric-util';
// ...other imports as needed
```

Refer to the documentation and code comments for details on available utilities and usage patterns.

## Documentation

- [Extensibility Overview](https://github.com/microsoft/vscode-fabric/blob/main/docs/extensibility-overview.md)
- [Architecture Overview](https://github.com/microsoft/vscode-fabric/blob/main/docs/architecture-overview.md)

## License

[MIT](LICENSE)
npm package: @microsoft/vscode-serial-monitor-api
Description: Public API for vscode-serial-monitor
Author: Microsoft Corporation
Latest version: 0.1.7

# Serial Monitor

The Serial Monitor extension for Visual Studio Code provides a way to read from and write to serial ports.

**This repository is used for tracking feedback and for exposing the public API. It contains no source code for the extension itself.**

## Public API for the ms-vscode.vscode-serial-monitor VS Code extension

The purpose of this API is to allow for any extension to interact with Microsoft's Serial Monitor extension for VSCode.

When your extension activates, you can use the following code to get access to the API:

```Typescript
    import {SerialMonitorApi, Version, getSerialMonitorApi, LineEnding, Parity, StopBits, Port} from '@microsoft/vscode-serial-monitor-api';
 
    let api: SerialMonitorApi|undefined = await getSerialMonitorApi(Version.latest, extensionContext);
    if (api) {
        // open a serial port
        const port: Port = await api.startMonitoringPort({port: "COM1", baudRate: 115200, lineEnding: LineEnding.None, dataBits: 8, stopBits: StopBits.One, parity: Parity.None});
        port.onClosed(() => console.log("My port was closed"));

        const tcpConnection: Port = await api.startMonitoringTCPConnection({host: "localhost", port: 1234, swoEnabled: false});
        port.onClosed(() => console.log("My tcp port was closed"));
    }
    // Dispose of the 'api' in your extension's deactivate() method.
```

## Feedback

We appreciate any feedback you have to help improve this extension. To submit feedback, please [create an issue](https://github.com/microsoft/vscode-serial-monitor/issues/new/choose).

*Note: this repository is for feedback on the VS Code extension. To provide feedback on Serial Monitor in Visual Studio 2022, please go to [Visual Studio Developer Community](https://developercommunity.visualstudio.com/home).*

## Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft 
trademarks or logos is subject to and must follow 
[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.
npm package: @microsoft/vscodetestcover
Description: A Mocha test runner with code coverage support for VS Code Azure Data Studio Extensions.
Author: Microsoft
Latest version: 1.2.2

# vscodetestcover

A Mocha test runner with code coverage support for VS Code and Azure Data Studio Extensions. This replaces the standard test runner from `vscode/lib/testrunner` and adds in code coverage support.

## Usage
 In a standard VSCode extension project, replace the `src/test/index.ts` file with the contents of `sample/index.ts` installed as part of this node module. This will use the test runner with coverage.

 To configure coverage settings, copy the `samples/coverconfig.json` beside the `index.ts` file and edit its contents. It defines where the expected src directory is, where to save coverage files, and more.

## Development

- Run `yarn install` to install dependencies
- Run `yarn compile` or `yarn watch` to compile


## Releasing

Release a new version of the extension by:

1. Bump the version in [package.json](./package.json)
2. Merge into main
3. Create a new tag with the version number specified in step 1
4. The release will be created in Github automatically by the CD pipeline, go to it and download the package artifact (tgz)
5. Run `npm publish <path to tarball>`

## Licensing
This code is originally from https://github.com/Microsoft/vscode-mssql. I have preserved the MIT license statement and Copyright from that project so things are still marked as Copyright Microsoft.
npm package: @microsoft/web-library-build
Description: `web-library-build` is a `gulp-core-build` build rig for building web libraries. It includes build subtasks for processing css, typescript, serving, and running browser tests using karma.
Latest version: 8.0.3

# @microsoft/web-library-build

`web-library-build` is a `gulp-core-build` build rig for building web libraries. It includes build subtasks for processing css, typescript, serving, and running browser tests using karma.

[![npm version](https://badge.fury.io/js/%40microsoft%2Fweb-library-build.svg)](https://badge.fury.io/js/%40microsoft%2Fweb-library-build)
[![Build Status](https://travis-ci.org/Microsoft/web-library-build.svg?branch=master)](https://travis-ci.org/Microsoft/web-library-build)
[![Dependencies](https://david-dm.org/Microsoft/web-library-build.svg)](https://david-dm.org/Microsoft/web-library-build)
npm package: @microsoft/webpack-project-references-alias
Description: [TypeScript](https://www.typescriptlang.org/) introduced a feature called [Project References](https://www.typescriptlang.org/docs/handbook/project-references.html) in version 3.0.
Latest version: 1.2.1

# Webpack alias generator for TypeScript project references

## Description

[TypeScript](https://www.typescriptlang.org/) introduced a feature called [Project References](https://www.typescriptlang.org/docs/handbook/project-references.html) in version 3.0.

Project References required compiled .d.ts files either checked-in or generated after each branch switch. Not doing this would result in a broken IntelliSense experience.

This drawback was fixed in version 3.7. The TypeScript language server can now inderstand project references. This improves the IntelliSense experience across projects while removing the need to have the compiled files on disk.

The goal of this package is to provide a tool to make webpack understand project references as well. This is needed when optimizing build time when using transpile-only loaders (ts-loader in transpile-only mode or babel-loader) without the need to have the generated files on disk.

This package create aliases that makes webpack resolve the TypeScript files instead of the generated JavaScript files.

For instance, when package A is a referenced project, the alias will let you do the following import:

```js
import "A/lib/foo"; // webpack will resolve A/src/foo.ts
```

## Usage

```js
const { getAliasForProject } = require("@microsoft/webpack-project-references-alias");

module.exports = {
  entry: "./src/index.ts",
  mode: "production",
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: "bundle.js"
  },
  resolve: {
    extensions: [".ts"],
    alias: getAliasForProject()
  },
  module: {
    rules: [
      { test: /\.ts$/, loader: "ts-loader", options: { transpileOnly: true } }
    ]
  }
};
```

# Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
npm package: @microsoft/webpack-stats-report
Description: A library for generating a markdown report for a bundle stats diff.
Latest version: 2.4.1

# webpack-stats-report
A library for generating a markdown report for a bundle stats diff.

## Installation
Using npm:
```sh
npm install @microsoft/webpack-stats-report
```
Using Yarn:
```sh
yarn add @microsoft/webpack-stats-report
```

## Usage
```typescript
import { createReport, getAppName } from "@microsoft/webpack-stats-report";
import { diff } from "@microsoft/webpack-stats-differ";
import * as path from "path";
import * as fs from "fs";

const baselineDir = path.resolve('/baseline');
const candidateDir = path.resolve('/candidate');

const diffResult = await diff(baselineDirUnzipped,candidateDir);

const report = createReport(diffResult);
const appName = getAppName(path.resolve('myAwesomeApp_default.json'));
```
# API

## createReport() function

Generates a bundle size report from webpack bundle stats diff

## Parameters

|  Parameter | Type | Description |
|  --- | --- | --- |
|  bundleStatsResults | [FileDiffResults](https://github.com/microsoft/ardiffact/blob/68e27505a9f7f97334592676bbd43b827f53c552/docs/webpack-stats-differ.filediffresults.md) | Diff results created by [FileDiffResults](https://github.com/microsoft/ardiffact/blob/68e27505a9f7f97334592676bbd43b827f53c552/docs/webpack-stats-differ.filediffresults.md) object |
|  minimumIncrease | number | number indicating the smallest increase in bytes that must be reported |

<b>Returns:</b>

string

markdown report

## getAppName() function

Returns the app name from webpack bundle stats filepath

## Parameters

|  Parameter | Type | Description |
|  --- | --- | --- |
|  filePath | string | path to webpack bundle stats file |

<b>Returns:</b>

string

- App name from stat filepath  


# Contributing

This project welcomes contributions and suggestions. Most contributions require you to
agree to a Contributor License Agreement (CLA) declaring that you have the right to,
and actually do, grant us the rights to use your contribution. For details, visit
https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need
to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the
instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

# License

MIT
npm package: @microsoft/webpack5-load-themed-styles-loader
Description: This simple loader wraps the loading of CSS in script equivalent to `require('load-themed-styles').loadStyles( /* css text */ )`. It is designed to be a replacement for style-loader.
Latest version: 0.4.12

# @microsoft/webpack5-load-themed-styles-loader

## Installation

`npm install @microsoft/webpack5-load-themed-styles-loader --save-dev`

## Overview

This simple Webpack loader that wraps the loading of CSS in script equivalent
to `require("@microsoft/load-themed-styles").loadStyles( /* css text */ )`.
It is designed to be a replacement for style-loader.

## Usage

[Documentation: Using loaders](http://webpack.github.io/docs/using-loaders.html)

This loader is designed to be used in conjunction with css-loader.

``` javascript
var css = require("@microsoft/webpack5-load-themed-styles-loader!css!./file.css");
// => returns css code from file.css, uses load-themed-styles to load the CSS on the page.
```

### Example config

``` javascript
        use: [
          {
            loader: "@microsoft/webpack5-load-themed-styles-loader",  // creates style nodes from JS strings
            options: {
              async: false
            }
          },
          {
            loader: "css-loader", // translates CSS into CommonJS
            options: {
              modules: true,
              importLoaders: 2,
              localIdentName: '[name]_[local]_[hash:base64:5]',
              minimize: false
            }
          },
          {
            loader: 'postcss-loader',
            options: {
              plugins: function () {
                return [
                  require('autoprefixer')
                ];
              }
            }
          },
          {
            loader: "sass-loader",
          }
        ]

```

## Options

### `async` (boolean, defaults to `false`)

By default, `@microsoft/load-themed-styles` loads styles synchronously. This can have adverse performance effects
if many styles are loaded in quick succession. If the `async` option is set to `true`, the `loadStyles` function
is called with the second parameter set to `true`, directing the function to debounce style loading causing fewer
changes to the DOM.


## Links

- [CHANGELOG.md](
  https://github.com/microsoft/rushstack/blob/main/webpack/webpack5-loader-load-themed-styles/CHANGELOG.md) - Find
  out what's new in the latest version

`@microsoft/webpack5-load-themed-styles-loader` is part of the [Rush Stack](https://rushstack.io/) family of projects.
npm package: @microssr/ts-jsx-str
Description: JSX to string renderer for TypeScript
Author: David Delassus
Latest version: 0.1.1

# TypeScript JSX renderer

This project provides a very simple renderer for JSX, without React/Vue or any
other big framework.

This is especially useful for **Server-Side Rendering**, in order to transform
JSX templates to string.

## :package: Installation

```
$ yarn add -D @microssr/ts-jsx-str @microssr/typings-ts-jsx-str
```

## :construction: Usage

In your `tsconfig.json` add the following:

```json
{
  "compilerOptions": {
    "jsx": "react",
    "jsxFactory": "JSX.createElement",
    "types": ["@microssr/typings-ts-jsx-str"]
  }
}
```

Then in `your-file.tsx`:

```tsx
import JSX from '@microssr/ts-jsx-str'

const greetings = (<h1>Hello World</h1>)
console.log(greetings)
// <h1>Hello World</h1>
```

Or with a function-based template:

```tsx
import JSX from '@microssr/ts-jsx-str'

const Greet = ({ name }) => (<p>Hello {name}</p>)
const greetings = (<Greet name="world" />)
console.log(greetings)
// <p>Hello world</p>
```

## :memo: License

This library is released under the terms of the [MIT License](./LICENSE.txt).
npm package: @microssr/tsconfig
Description: TypeScript configuration preset
Author: David Delassus
Latest version: 0.1.0

# TypeScript configuration preset

## :package: Installation

```
$ yarn add -D @microssr/tsconfig
```

## :construction: Usage

Add the following to your `tsconfig.json`:

```json
{
  "extends": "@microssr/tsconfig/tsconfig.json"
}
```