open-index/open-npm huggingface dataset:
npm package: @instriker/demolibraryforaot
Description: Sample Angular library built using ngx-library yeoman generator to demonstrate an AOT bug with barrel files.
Author: Alexandre Emond
Latest version: 0.0.8

# instriker demo - Sample Angular library built using ngx-library yeoman generator to demonstrate an AOT bug.

## Dependencies

* [Angular](https://angular.io) (*requires* Angular 5 or higher, tested with 5.0.0)

## Installation
Install above dependencies via *npm*.

Now install `demolibraryforaot` via:
```shell
npm install --save @instriker-demo/demolibraryforaot
```

## Usage

```typescript
import { SimpleCoreComponent1 } from '@instriker-demo/demolibraryforaot';
import { SimpleCoreComponent2 } from '@instriker-demo/demolibraryforaot';

@Component({
  selector: 'app-sample',
  templateUrl: './sample.component.html',
  styleUrls: ['./sample.component.css']
})
export class SampleComponent extends SimpleCoreComponent1 {
}
```

## License

Copyright (c) 2018 Alexandre Emond. Licensed under the MIT License (MIT)
npm package: @instructa/mcp-youtube-music
Description: Simple MCP Starter Package
Author: Kevin Kern
Latest version: 0.0.3

# YouTube Music MCP 🎵

This is a simple MCP server that allows you to search for and play tracks on YouTube Music directly from your AI assistant like Cursor or Claude Desktop.

Built with:

- [YouTube Music](https://music.youtube.com/)
- [Anthropic MCP](https://docs.anthropic.com/en/docs/agents-and-tools/mcp)
- [Cursor](https://cursor.so/)

## Available Tools

- `searchTrack`: Search for tracks on YouTube Music by name.
- `playTrack`: Play tracks directly by searching and opening them in your default browser.


# Installation

## 1. Get a key

To make this work you need a valid [Google Youtube API Key](https://console.cloud.google.com/marketplace/product/google/youtube.googleapis.com)

## 2. Add to cursor

Add the following MCP configuration to your Cursor `.cursor/mcp.json` settings:

```json
{
  "mcpServers": {
    "youtube-music-mcp": {
      "command": "npx",
      "args": ["-y", "@instructa/youtube-music-mcp"],
      "env": {
        "YOUTUBE_API_KEY": "<INSERT_API_KEY_HERE>"
      }
    }
  }
}
```

**Develop**

This MCP is typically run directly using `npx` and doesn't require local installation or building unless you intend to modify the source code. If you want to develop it locally, you would typically clone the source repository (if available) and follow its specific contribution guidelines.

## License

This project is licensed under the MIT License - see the LICENSE file for details.

---

## Links

- X/Twitter: [@kregenrek](https://x.com/kregenrek)
- Bluesky: [@kevinkern.dev](https://bsky.app/profile/kevinkern.dev)

## Courses
- Learn Cursor AI: [Ultimate Cursor Course](https://www.instructa.ai/en/cursor-ai)
- Learn to build software with AI: [instructa.ai](https://www.instructa.ai)

## See my other projects:

* [AI Prompts](https://github.com/instructa/ai-prompts/blob/main/README.md) - Curated AI Prompts for Cursor AI, Cline, Windsurf and Github Copilot
* [codefetch](https://github.com/regenrek/codefetch) - Turn code into Markdown for LLMs with one simple terminal command
* [aidex](https://github.com/regenrek/aidex) A CLI tool that provides detailed information about AI language models, helping developers choose the right model for their needs.
* [codetie](https://github.com/codetie-ai/codetie) - XCode CLI
npm package: @instructure/babel-plugin-transform-class-display-name
Description: A babel plugin to add a displayName property to React component class declarations
Author: Instructure, Inc. Engineering and Product Design
Latest version: 5.52.3
Deprecated: Deprecated as of Instructure UI v7.0.0

---
category: packages
---

## @instructure/babel-plugin-transform-class-display-name

[npm]: https://img.shields.io/npm/v/@instructure/babel-plugin-transform-class-display-name.svg
[npm-url]: https://npmjs.com/package/@instructure/babel-plugin-transform-class-display-name

[![npm][npm]][npm-url]

A transform to add a displayName to React components. This is required for
[@instructure/ui-themeable](#ui-themeable) because it uses the displayName to
scope the CSS variables.

### Installation

```sh
yarn add --dev @instructure/babel-plugin-transform-class-display-name
```

### Usage

In your `.babelrc` file:

```json
{
  "plugins": ["@instructure/babel-plugin-transform-class-display-name"]
}
```
npm package: @instructure/browserslist-config-canvas-lms
Description: The official list of browsers supported by Canvas LMS & the Canvas product ecosystem. To use this, just add `"browserslist": ["extends @instructure/browserslist-config-canvas-lms"]` to your package.json
Latest version: 2.0.0

# supported-browsers
The list of browsers that should be supported by Canvas LMS and all the products that are part of the Canvas Ecosystem

## Canvas supports the current and first previous major releases of the following browsers:

*   **Chrome**
*   **Firefox** ([Extended Releases](http://www.mozilla.org/en-US/firefox/organizations/) are not supported)
*   **Internet Explorer** 11 (_Windows only—_functionally supported; may exhibit slight visual differences from other browsers, but these differences do not restrict product functionality or accessibility)
*   **Edge**  _(Windows only)_
*   **Respondus Lockdown Browser** (supporting the latest [system requirements](https://www.respondus.com/products/lockdown-browser/requirements.shtml))
*   **Safari**  _(Macintosh only_)

Because browsers are constantly releasing new versions, the actual version numbers that  "current and first previous major release" translates to will change over time. [click here to see what that currently means](http://browserl.ist/?q=last+2+chrome+versions%2C+last+2+firefox+versions%2C+last+2+edge+versions%2C+last+2+ios+versions%2C+last+2+opera+versions%2C+last+2+safari+versions%2C+last+2+ChromeAndroid+versions%2C+ie+%3E%3D+11)

If you are using one of the mainstream browsers that updates itself automatically (eg: [Chrome](https://www.google.com/chrome/), [Firefox](https://www.mozilla.org/firefox/), [Microsoft Edge](https://www.microsoft.com/windows/microsoft-edge) or [Safari](https://support.apple.com/en-us/HT204416)), you should not ever have to worry about this.
npm package: @instructure/canvas-supported-browsers
Description: The official list of browsers supported by Canvas LMS & the Canvas product ecosystem
Latest version: 1.0.0

# supported-browsers
The list of browsers that should be supported by Canvas LMS and all the products that are part of the Canvas Ecosystem

## Canvas supports the current and first previous major releases of the following browsers:

*   **Chrome**
*   **Firefox** ([Extended Releases](http://www.mozilla.org/en-US/firefox/organizations/) are not supported)
*   **Internet Explorer** 11 (_Windows only—_functionally supported; may exhibit slight visual differences from other browsers, but these differences do not restrict product functionality or accessibility)
*   **Edge**  _(Windows only)_
*   **Respondus Lockdown Browser** (supporting the latest [system requirements](https://www.respondus.com/products/lockdown-browser/requirements.shtml))
*   **Safari**  _(Macintosh only_)

Because browsers are constantly releasing new versions, the actual version numbers that  "current and first previous major release" translates to will change over time. [click here to see what that currently means](http://browserl.ist/?q=last+2+chrome+versions%2C+last+2+firefox+versions%2C+last+2+edge+versions%2C+last+2+ios+versions%2C+last+2+opera+versions%2C+last+2+safari+versions%2C+last+2+ChromeAndroid+versions%2C+ie+%3E%3D+11)

If you are using one of the mainstream browsers that updates itself automatically (eg: [Chrome](https://www.google.com/chrome/), [Firefox](https://www.mozilla.org/firefox/), [Microsoft Edge](https://www.microsoft.com/windows/microsoft-edge) or [Safari](https://support.apple.com/en-us/HT204416)), you should not ever have to worry about this.
npm package: @instructure/conventional-changelog
Description: Commitizen adapter following the conventional-changelog format.
Latest version: 1.0.0

# conventional-changelog

Provides prompt configuration for commitizen.  The following questions are asked:

1. Select the type of change that you're committing
     * Simply select the type from the provided list of options.  Selecting `feat` will cause a minor version bump and
       selecting `fix` will cause a bugfix version bump.  Marking your change as "breaking" (explained below) will cause
       a major version bump.
2. Denote the scope of this change
     * This is a freeform input that allows you to specify one or more "scopes".  This scope is used for grouping
       together like changes in the CHANGELOG.  It's best to make this as specific as possible, and some great
       candidates are:
          * A specific component name (i.e. GradingHeader, Autocomplete, etc)
          * A specific section of the project (i.e. store, documentation, dependencies, etc)
 
       In the future, we may lint against a specific set of scope names.
3. Write a short, imperative tense description of the change
     * This is the subject of your commit and should be kept to 72 characters or less
4. List any issues closed by this change
    * List your JIRA tickets here.  Whatever you type will be prefixed with "fixes", so entering "QUIZ-123" will result
      in "fixes QUIZ-123".  You should ammend your commit message if you need to use a resolution type other than
      "fixes".
5. Provide a test plan
     * List out your test plan steps.  Whatever you type will be prefixed with "Test plan:\n".
6. Is this a breaking change?
     * If this change is not backwards compatible to any potential consumer, then you should answer yes here.  Answering
       yes here will cause a major version bump.
7a. Provide any important details about the breaking change
     * This question is only asked if you said yes when asked if the change is a breaking change.  You should include 
       details about why this is a breaking change, what the change impacts, and how consumers can mitigate it.
7b. (Optional) Provide any additional information you think might be useful
     * This question is only asked if you said no when asked if the change is a breaking change.  Additional in-depth
       details that might be useful.  This section is optional if the previously provided short description is simple
       enough.
npm package: @instructure/cz-lerna-changelog
Description: Prompts for conventional changelog standard in a lerna environment.
Author: Instructure, Inc. Engineering and Product Design
Latest version: 9.11.1

---
category: packages
---

## cz-lerna-changelog

[![npm][npm]][npm-url]
[![MIT License][license-badge]][license]
[![Code of Conduct][coc-badge]][coc]

Prompts for conventional changelog standard in a lerna environment.

### Installation

```sh
npm install @instructure/cz-lerna-changelog
```

Add the following to your package.json file:

```json
"config": {
  "commitizen": {
    "path": "./node_modules/@instructure/cz-lerna-changelog"
  }
}
```

[npm]: https://img.shields.io/npm/v/@instructure/cz-lerna-changelog.svg
[npm-url]: https://npmjs.com/package/@instructure/cz-lerna-changelog
[license-badge]: https://img.shields.io/npm/l/instructure-ui.svg?style=flat-square
[license]: https://github.com/instructure/instructure-ui/blob/master/LICENSE
[coc-badge]: https://img.shields.io/badge/code%20of-conduct-ff69b4.svg?style=flat-square
[coc]: https://github.com/instructure/instructure-ui/blob/master/CODE_OF_CONDUCT.md
npm package: @instructure/file-type-jmp
Description: JMP detection plugin for file-type
Latest version: 0.1.4

# @instructure/file-type-jmp

JMP detection plugin for [file-type](https://github.com/sindresorhus/file-type).

This plugin detects files from [JMP](https://www.jmp.com), a statistical discovery and data analysis software suite used for interactive exploratory data analytics, visualization, and statistical modeling.

## Install

```bash
npm install @instructure/file-type-jmp
```

## Usage

```js
import {fileTypeFromFile} from 'file-type';
import {detectJmp} from '@instructure/file-type-jmp';

const fileType = await fileTypeFromFile('sample.jmp', {customDetectors: [detectJmp]});
console.log(fileType);
//=> {ext: 'jmp', mime: 'application/x-jmp-data'}
```

## API

### detectJmp

Type: `Detector`

Detector for JMP files.

## Development

The detection logic will be implemented once JMP file format specifications are provided, including:

- Magic byte sequences for file identification
- Proper MIME type
- File structure details

## License

MIT
npm package: @instructure/generate-examples
Description: A utility for automatically generating component examples
Author: Instructure, Inc. Engineering and Product Design
Latest version: 5.52.3
Deprecated: Deprecated as of Instructure UI v7.0.0. Use @instructure/ui-component-examples instead.

---
category: packages
---

## generate-examples

[![npm][npm]][npm-url]
[![build-status][build-status]][build-status-url]
[![MIT License][license-badge]][LICENSE]
[![Code of Conduct][coc-badge]][coc]

A utility for automatically generating component examples.

### Installation

```sh
yarn add @instructure/generate-examples
```

### Usage

```js
import generateExamples from '@instructure/generate-examples/lib/generateExamples'

const examples = generateExamples(modules, options)
```

For more detailed usage and documentation, see [generateExamples](#generateExamples)

[npm]: https://img.shields.io/npm/v/@instructure/ui-generate-examples.svg
[npm-url]: https://npmjs.com/package/@instructure/ui-generate-examples

[build-status]: https://travis-ci.org/instructure/instructure-ui.svg?branch=master
[build-status-url]: https://travis-ci.org/instructure/instructure-ui "Travis CI"

[license-badge]: https://img.shields.io/npm/l/instructure-ui.svg?style=flat-square
[license]: https://github.com/instructure/instructure-ui/blob/master/LICENSE

[coc-badge]: https://img.shields.io/badge/code%20of-conduct-ff69b4.svg?style=flat-square
[coc]: https://github.com/instructure/instructure-ui/blob/master/CODE_OF_CONDUCT.md