open-index/open-npm huggingface dataset:
npm package: @mattstratton/tiger-den-mcp-setup
Description: CLI installer to configure the Tiger Den MCP server in Claude Desktop
Latest version: 0.1.3

# Tiger Den MCP Setup

CLI installer to configure the Tiger Den MCP server for Claude Desktop.

## Requirements

- Node.js 18+
- Claude Desktop installed

## Install Tiger Den MCP

Run:

```bash
npx -y @mattstratton/tiger-den-mcp-setup
```

The installer will:
- Prompt for your Tiger Den API key
- Locate your Claude Desktop settings.json
- Configure the Tiger Den MCP server
- Create a backup if needed

Restart Claude Desktop after installation.

## Doctor Mode

To verify your setup without modifying files:

```bash
npx -y @mattstratton/tiger-den-mcp-setup --doctor
```

## Releasing Updated Versions (developer)

```bash
npm version patch
npm publish
```
npm package: @mattstyles/alias
Description: The amazing string mutator
Author: Matt Styles
Latest version: 1.0.0


# alias

[![Build
Status](https://travis-ci.org/mattstyles/alias.svg?branch=master)](https://travis-ci.org/mattstyles/alias)

> Turns one string into another

```sh
$ npm i -S @mattstyles/alias
```

```js
// from -> to
const ALIASES = {
  ls: 'list'
}

const alias = require( '@mattstyles/alias' )( ALIASES )

console.log( alias( 'ls' ) )
// list

console.log( alias( 'unknown' ) )
// unknown
```
npm package: @mattstyles/temple
Description: Creates files from templates
Author: Matt Styles
Latest version: 1.4.0


# Temple

> Super simple utility to scaffold templated files

## Example

```sh
temple render readme.hjs > README.md
```

Temple will pull templates from its storage and use data from your `package.json` to output a rendered file.

## Installation

```sh
npm i -g @mattstyles/temple
```

## Usage

Temple is self-documenting as much as possible, use `--help` to get additional information about Temple and each command.

```sh
temple --help
temple render --help
```

Temple needs only a couple of things to work

* A template engine specification
* Some templates

### Specifying and installing templating engines

Temple uses [consolidate](http://github.com/tj/consolidate.js) to render templates and will not install engines unless instructed to do so.

A template engine specification consists of three fields that you need to consider:

```json
{
  "name": "hogan",
  "module": "hogan.js",
  "extensions": [
    "hjs",
    "hogan"
  ]
}
```

* `name` the identifier shared with consolidate
* `module` the module name to install from [npm](http://npmjs.com) when required
* `extensions` Temple will attempt to match template file extensions to those listed by the engine specification i.e. `readme.hjs` would imply using `hogan` to render the template.

The easiest way to register a template is to stream in a specification

```sh
echo '{"module":"hogan.js","extensions":["hjs"]}' | temple engine hogan
```

There are a few other options, see `temple engine --help`.

Once the specification is loaded then you’re free to install it, although Temple will prompt you if you forget this step and try to use a template file requiring the engine.

```sh
temple engine --install hogan
```

### Specifying a template file

Easiest way is to stream the template file in.

```sh
echo '# {{ name }}' | temple register readme.hjs
```

See `temple register --help`

### Rendering a template file

Once you have a few templates and at least one engine registered with Temple you’re set to get going

```sh
temple render readme.hjs > README.md
```

In these examples we have registered `hogan` as a templating engine and added a `readme.hjs` template file, when we attempt to render it Temple checks the extensions, finds that it matches `hogan` and uses `hogan.js` to render the template to stdout, additionally prompting to install `hogan.js` if necessary.

## License

MIT
npm package: @matttelliott/react-select-theme
Description: react component to select bootstrap theme
Author: Matt T Elliott
Latest version: 1.0.0

# react-select theme

create a `select` element with a list of bootstrap themes from [bootswatch](https://bootswatch.com)


```typescript
import { SelectTheme } from '@matttelliott/react-select-theme'

export const MyApp = () => (
  <div>
    <SelectTheme></SelectTheme>
  </div>
)
```
npm package: @matttelliott/tiny-redux
Description: tiny redux
Author: Matt T Elliott
Latest version: 1.0.3

# Tiny Redux

Just a tiny bit of state management

## Usage

### Via `<script>` tag

```html
<!DOCTYPE html>
<html lang="en">
  <head>
    <title></title>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <script
      src="https://cdn.jsdelivr.net/gh/matttelliott/tiny-redux/index.min.js"
      type="text/javascript"
    ></script>
    <script>
      const initialState = { clicked: false }
      const { getState, registerReducer, registerEffect, dispatchAction } =
        tinyRedux(initialState)
    </script>

    <!-- Optional React scripts -->
    <script
      src="https://unpkg.com/react@17/umd/react.development.js"
      crossorigin
    ></script>
    <script
      src="https://unpkg.com/react-dom@17/umd/react-dom.development.js"
      crossorigin
    ></script>
    <script src="https://unpkg.com/babel-standalone@6/babel.min.js"></script>
  </head>
  <body>
    <main id="root"></main>

    <script type="text/babel">
      function update(state) {
        ReactDOM.render(
          <div>
            <p>clicked: {getState().clicked.toString()}</p>
            <button type='button' onClick={() => dispatchAction('clickButton')}>
              Click Me
            </button>
          </div>,
          document.getElementById('root')
        )
      }

      update(getState())
      registerEffect((state, action) => {
        setTimeout(() => update(state), 0)
      })
      registerReducer((state, action) => {
        if (action.type !== 'clickButton') return state
        state.clicked = true
        return state
      })
    </script>
  </body>
</html>
```

### Via NPM

```bash
npm install --save @matttelliott/tiny-redux
```

```typescript
import { tinyRedux } from '@matttelliott/tiny-redux'

const initialState = {}
const { getState, registerReducer, registerEffect, dispatchAction } =
  tinyRedux(initialState)
```
npm package: @matttelliott/tokyonight.scss
Description: Bootstrapa theme based on tokyonight
Author: Matt T Elliott
Latest version: 1.0.1

# Tokyo Night

### Bootstrap theme based on [folke/tokyonight.nvim](https://github.com/folke/tokyonight.nvim)

## [Demo](https://matttelliott.github.io/tokyonight.scss)

## Usage

### As plain CSS

```html
<link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/matttelliott/tiny-redux/index.min.js">
```
### As a SCSS module

```scss
@import '@matttelliott/tokyonight.scss';
```

### As Bootstrap SCSS variables

```scss
@import './node_modules/bootstrap/scss/_functions.scss';
@import './node_modules/@matttelliott/tokyonight.scss/variables.scss';
@import './node_modules/bootstrap/scss/bootstrap.scss';
```
npm package: @matttennison/sveltekit-adapter-aws
Description: SvelteKit to deploy your project using AWS CDK. Fork of https://github.com/MikeBild/sveltekit-adapter-aws
Author: matt@matttennison.com
Latest version: 4.5.3

# SvelteKit Adapter AWS

This project contains a SvelteKit adapter to deploy SvelteKit to AWS using AWS-CDK.

## How to use?

1. Create a SvelteKit project "my-app" - `npm create svelte@latest my-app`
2. `cd my-app`
3. `npm install`
4. `npm install -D sveltekit-adapter-aws`
5. edit **svelte.config.js**

## Basic setup example

**svelte.config.js**

```javascript
import { adapter } from 'sveltekit-adapter-aws';
import preprocess from 'svelte-preprocess';

export default {
  preprocess: preprocess(),
  kit: {
    adapter: adapter({
      autoDeploy: true,
    }),
  },
};
```

## Architecture

![Architecture](architecture.png)

## Configuration

```typescript
export interface AWSAdapterProps {
  cdkProjectPath?: string; // AWS-CDK App file path for AWS-CDK custom deployment applications (e.g. ${process.cwd()}/deploy.js)
  artifactPath?: string; // Build output directory (default: build)
  autoDeploy?: boolean; // Should automatically deploy in SvelteKit build step (default: false)
  stackName?: string; // AWS-CDK CloudFormation Stackname (default: AWSAdapterStack-Default)
  esbuildOptions?: any; // Override or extend default esbuild options. Supports `external` (default `['node:*']`), `format` (default `cjs`), `target` (default `node16`), `banner` (default `{}`).
  FQDN?: string; // Full qualified domain name of CloudFront deployment (e.g. demo.example.com)
  MEMORY_SIZE?: number; // Memory size of SSR lambda in MB (default 128 MB)
  LOG_RETENTION_DAYS?: number; // Log retention in days of SSR lambda (default 7 days)
  zoneName?: string; // The name of the hosted zone in Route 53 (defaults to the TLD from the FQDN)
}
```

## Example usages

- [Basic](https://github.com/MikeBild/sveltekit-adapter-aws-basic-example)
- [Advanced](https://github.com/MikeBild/sveltekit-adapter-aws-advanced-example)
- [Full Workshop Example](https://github.com/MikeBild/serverless-workshop-sveltekit)
npm package: @mattthurling/ore
Description: Open Rights Engine (ORE) – self-custodial encryption and access control for music and media.
Author: Matt Thurling
Latest version: 0.0.6

# Open Rights Engine (ORE)

> Self-custodial encryption and access control for music and media.

This is an early work-in-progress SDK.  
The goal: let creators encrypt tracks and users decrypt them locally,
using self-custodied keys, with optional NFT/rights integration.

## Install

```bash
npm install open-rights-engine
npm package: @mattvagni/typewriter
Description: A compiler for generating strongly typed analytics clients via Segment Protocols
Author: Colin King
Latest version: 7.1.0

<p align="center">
	<br>
	<br>
  <img src=".github/assets/typewriter-logo.svg?sanitize=true" alt="Typewriter logo" />
  <br>
  <br>
</p>

This is a custom fork to test some changes. **Do not use this.** It is temporary and will be deleted.
npm package: @mattvick/infobox-parser
Description: Parse Wikipedia Infobox Source
Author: Richard van der Dys
Latest version: 3.6.5-b

[![NPM Version](https://img.shields.io/npm/v/infobox-parser.svg)](https://www.npmjs.com/package/infobox-parser)
[![Build Status](https://travis-ci.org/dijs/infobox-parser.svg)](https://travis-ci.org/dijs/infobox-parser)

<a href="https://www.buymeacoffee.com/2tmRKi9" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/default-yellow.png" alt="Buy Me A Coffee" height="41" width="174"></a>

## Infobox Parser

This was originally written as a companion module for `wikijs`. But it can work great on it's own as well. The main function of this module is parsing wikipedia article's infobox data. The infobox source is in wikitext format and
difficult to parse. This module analyzes it and outputs JSON for you.

### Usage

```js
var parseInfo = require("infobox-parser")

parseInfo(`
{{Infobox Batman
|name      = Bruce Wayne
|hero      = y
}}`);
// Outputs {
	general: {
		hero: true,
		name: 'Bruce Wayne'
	}
}
```

### Parsing Options

```js
/**
 * Parse Wiki Infobox Text
 * @param {string} source - Infobox source text
 * @param {Object} options - Parsing options
 * @param {boolean} [options.simplifyDataValues=true] - Only use primary data values
 * @param {boolean} [options.removeSmall=false] - Remove <small>...</small> chunks of source data
 * @param {boolean} [options.removeReferences=true] - Remove <ref>...</ref> chunks of source data
 * @returns {Object} Structured information from source text
 */
const info = parseInfo(source, options);
```

### Support

It supports many of wikipedia features, but not all yet. If there is a feature you need it to support, but it does not. Please create an issue and I will add the functionality.