open-index/open-npm huggingface dataset:
npm package: @funjs/route-parser
Description: Simple and fast functional route parser...
Author: Mauro Junior
Latest version: 1.4.0

[![travis build](https://img.shields.io/travis/fun-js/route-parser.svg?style=flat)](https://travis-ci.org/fun-js/route-parser)
[![Dependency Status](https://david-dm.org/fun-js/route-parser.svg?theme=shields.io)](https://david-dm.org/fun-js/route-parser)
[![devDependency Status](https://david-dm.org/fun-js/route-parser/dev-status.svg?theme=shields.io)](https://david-dm.org/fun-js/route-parser#info=devDependencies)
[![Codecov](https://img.shields.io/codecov/c/github/fun-js/route-parser.svg)]()
[![MIT License](https://img.shields.io/npm/l/starwars-names.svg?style=flat)](http://opensource.org/licenses/MIT)
[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg?style=flat)](https://github.com/semantic-release/semantic-release)

## What is it?

A 10X FASTER and functional route parser (run the benchmark for yourself), for Javascript in Node and the browser. Its api is inspired by [route-parser](https://github.com/rcs/route-parser), but is implemented in a functional way, don't rely in 'this' keyword.


## How do I install it?

```Shell
npm install --save @funjs/route-parser
or
yarn add @funjs/route-parser
```

## How do I use it?

```javascript
const Router = require('@funjs/route-parser');
const route = Router('/books/:section=(programming|romance|horror)/:title');
route.match('/books/programming/JavaScript-Good-Parts'); // { section: 'programming', title: 'JavaScript-Good-Parts' }
```

## How do I customize delimiters and named segment?

```javascript
const Router = require('@funjs/route-parser', { delimiter: ':', namedSegment: '$' });
const route = Router('books:$section=(programming|romance|horror):$title');
route.match('books:programming:JavaScript-Good-Parts'); // { section: 'programming', title: 'JavaScript-Good-Parts' }
```


## What can I use in my routes?

| Example         | Description          |
| --------------- | -------- |
| `:name`         |  a named parameter to capture from the route up to `/`, `?`, or end of string  |
| `*`        |  a splat to capture from the route up to `?` or end of string |
| <code>:name=(a&#124;b&#124;c)</code>  |  a named parameter group that doesn't have to be part of the query. Can contain nested optional groups, params, and splats
| anything else   | free form literals |

Some examples:

* `/some/:thing`
* `/users/:id/comments/:comment/rating/:rating`
* `/*/foo/*`
* `/books/:section=(Romance|Horror)/:title`


## How does it work?

For performance reasons the matching is done by generating regulars expressions.


## How to run the benchmark?

```Shell
cd benchmark
npm install
node index.js
```


## TODO:

- [x] RegExp Matching
- [x] Named parameters
- [x] named parameters Options
- [ ] Reverse Matching
- [x] Customizables delimiters and named segments
- [ ] Querystrings
npm package: @funk-team/elm-interreactor
Description: An elm reactor with interactive error messages
Author: Jan Wirth
Latest version: 0.0.6

# Elm interReactor
An elm reactor that allows you to apply the suggestions included in the report of the elm compiler.

![screenshot of interReactor](interreactor-screenshot.png)

Usage:
```
npx @funk-team/elm-interreactor
```

:warning: **This is experimental software. Please commit your files before using this tool and be aware of the known issues.**

## Known issues
- sometimes the report for the first compilation is not loaded / stale data is presented. Reloading the browser helps.
- end of imports can not be detected, adding an import fails silently
- field names sometimes are suggested on type problems with records

## Rationale
As a terminal user, I find myself often just applying suggestions from the elm compiler by reading the line number and applying the fix.
Because copying from the output is cumbersome I type the changes manually and make mistakes.
This tool automates the process.

## Demo (click to play)
[demo](https://user-images.githubusercontent.com/7485959/120943953-f0a71380-c729-11eb-8db8-e270953bfb0b.mp4)
## Usage
```
cd same-directory-as-elm-json
npx @funk-team/elm-interreactor
```
npm package: @funkai/cli
Description: CLI for the funkai AI SDK framework
Latest version: 0.4.0

<div align="center">
  <p><strong>@funkai/cli</strong></p>
  <p>CLI for the funkai prompt SDK — codegen, lint, create, and setup commands for <code>.prompt</code> files.</p>

<a href="https://www.npmjs.com/package/@funkai/cli"><img src="https://img.shields.io/npm/v/@funkai/cli" alt="npm version" /></a>
<a href="https://github.com/joggrdocs/funkai/blob/main/LICENSE"><img src="https://img.shields.io/github/license/joggrdocs/funkai" alt="License" /></a>

</div>

## Features

- :gear: **Code generation** — Generate typed TypeScript modules from `.prompt` files.
- :mag: **Validation** — Validate prompt files for undefined and unused variables.
- :sparkles: **Scaffolding** — Create new `.prompt` files and partials with a single command.
- :wrench: **Project setup** — Configure VSCode, `.gitignore`, and `tsconfig.json` interactively.

## Install

```bash
npm install @funkai/cli
```

## Usage

### `funkai prompts generate`

Generate typed TypeScript modules from `.prompt` files.

```bash
funkai prompts generate --out .prompts/client --includes "src/agents/**"
```

| Flag         | Description                               |
| ------------ | ----------------------------------------- |
| `--out`      | Output directory for generated files      |
| `--includes` | Glob patterns to scan for `.prompt` files |
| `--partials` | Custom partials directory                 |
| `--silent`   | Suppress output except errors             |

### `funkai prompts lint`

Validate `.prompt` files without generating output.

```bash
funkai prompts lint --includes "src/agents/**"
```

| Flag         | Description                                              |
| ------------ | -------------------------------------------------------- |
| `--includes` | Glob patterns to scan for `.prompt` files                |
| `--partials` | Custom partials directory (default: `.prompts/partials`) |
| `--silent`   | Suppress output except errors                            |

### `funkai prompts create`

Scaffold a new `.prompt` file.

```bash
funkai prompts create my-agent
funkai prompts create my-agent --out src/agents/my-agent
```

| Flag        | Description                                                   |
| ----------- | ------------------------------------------------------------- |
| `--name`    | Prompt name (kebab-case)                                      |
| `--out`     | Output directory (defaults to cwd)                            |
| `--partial` | Create as a partial in `.prompts/partials/` (ignores `--out`) |

### `funkai prompts setup`

Interactive project configuration for `.prompt` file development.

```bash
funkai prompts setup
```

Configures VSCode file associations, Liquid extension recommendation, `.gitignore` entries, and `tsconfig.json` path aliases.

## Documentation

See the [Prompts concept](/concepts/prompts) and [Prompts CLI reference](/reference/prompts/cli) for the full file format, library API, and guides.

## License

[MIT](https://github.com/joggrdocs/funkai/blob/main/LICENSE)
npm package: @funkai/prompts
Description: Prompt SDK with LiquidJS templating and Zod validation
Latest version: 0.4.1

<div align="center">
  <p><strong>@funkai/prompts</strong></p>
  <p>Prompt SDK for authoring <code>.prompt</code> files with LiquidJS templating and Zod validation.</p>

<a href="https://www.npmjs.com/package/@funkai/prompts"><img src="https://img.shields.io/npm/v/@funkai/prompts" alt="npm version" /></a>
<a href="https://github.com/joggrdocs/funkai/blob/main/LICENSE"><img src="https://img.shields.io/github/license/joggrdocs/funkai" alt="License" /></a>

</div>

## Features

- :pencil2: **built-in templating** — Write prompts as Liquid templates (in `.prompt` format) with YAML frontmatter.
- :shield: **Zod validation** — Schema variables are validated at render time.
- :package: **Codegen** — Generate typed TypeScript modules from `.prompt` files.
- :jigsaw: **Partials** — Reusable prompt fragments with `{% render %}` tags, flattened at build time.
- :file_folder: **Groups** — Organize prompts into nested namespaces via the `group` field.

## Install

```bash
npm install @funkai/prompts
```

## Usage

### Define a prompt

Create a `.prompt` file with YAML frontmatter and a Liquid template body:

```
---
name: writer
schema:
  tone: string
---
You are a {{ tone }} writer.
```

### Generate typed modules

```bash
npx funkai prompts generate --out .prompts/client --includes "src/agents/**"
```

### Consume prompts

Add the `~prompts` alias to your `tsconfig.json`:

```json
{
  "compilerOptions": {
    "paths": {
      "~prompts": ["./.prompts/client/index.ts"]
    }
  }
}
```

Then import and use:

```ts
import { prompts } from "~prompts";

const instructions = prompts.agents.writer.render({ tone: "concise" });
```

### Frontmatter

| Field     | Required | Description                       |
| --------- | -------- | --------------------------------- |
| `name`    | Yes      | Unique kebab-case identifier      |
| `group`   | No       | Namespace path for grouping       |
| `version` | No       | Version number                    |
| `schema`  | No       | Variable declarations (see below) |

### Schema variables

Each key under `schema` declares a template variable:

| Field         | Default  | Description                             |
| ------------- | -------- | --------------------------------------- |
| `type`        | `string` | Variable type (only `string` supported) |
| `required`    | `true`   | Whether the variable must be provided   |
| `description` | —        | Human-readable description              |

Shorthand: `tone: string` is equivalent to `tone: { type: string, required: true }`.

### Partials

Use `{% render 'name', key: 'value' %}` to include shared partials. Partials resolve from:

1. **Custom partials** — `.prompts/partials/` in your project (takes precedence)
2. **Built-in partials** — SDK's bundled `identity`, `constraints`, `tools`

## Documentation

For comprehensive documentation, see the [Prompts concept](/concepts/prompts) and [Prompts CLI reference](/reference/prompts/cli).

## License

[MIT](https://github.com/joggrdocs/funkai/blob/main/LICENSE)
npm package: @funkeai/funkecontext
Description: Context Manager for Funke AI
Author: Marco Müllner
Latest version: 0.1.0-beta.20250423124217

# FunkeContext

> Context management MCP server for Funke AI

FunkeContext is a Model Context Protocol (MCP) server that manages code context for the Funke coding assistant. It handles file scanning, content caching, and context configuration persistence.

## Features

- 📁 **Intelligent File Management**: Add files to context using glob patterns
- 🔄 **Smart Caching**: Cache file contents with automatic invalidation
- 💾 **Configuration Persistence**: Save and load context configurations
- 🔍 **Content Search**: Search across files in context
- 🚀 **MCP Integration**: Full Model Context Protocol server implementation

## Usage

### As a standalone server

```bash
# Start the MCP server
funkecontext
```

### As an MCP server within Funke

The Funke CLI automatically connects to this MCP server when running, providing the LLM with context management capabilities.

## MCP Tools

FunkeContext exposes the following MCP tools:

1. `list-context-files` - Lists all files currently in context
2. `add-context-files` - Adds files to context using glob patterns
3. `remove-context-files` - Removes files from context
4. `get-file-content` - Gets content of a file with caching
5. `save-context` - Saves context configuration
6. `load-context` - Loads context configuration
7. `search-context` - Searches for content in context files

## Development

```bash
# Install dependencies
pnpm install

# Build
pnpm build

# Test
pnpm test

# Run in development mode
pnpm dev
```

## Architecture

FunkeContext consists of three main components:

1. **File Cache** - Manages caching of file content with automatic invalidation
2. **Context Manager** - Maintains the state of the context, including file tracking
3. **Config Storage** - Handles persistence of context configurations

## License

MIT
npm package: @funkel1989/nuxt-auth0-js
Description: Simplified auth0-spa-js integration with Nuxt.js
Author: michael cavanaugh
Latest version: 0.2.4

# nuxt-auth0-spa

Simplifies [auth0-spa-js](https://github.com/auth0/auth0-spa-js) integration with Nuxt.js

 * [nuxt/nuxt.js: The Vue.js Framework](https://github.com/nuxt/nuxt.js)
 * [auth0/auth0-spa-js: Auth0 authentication for Single Page Applications (SPA) with PKCE](https://github.com/auth0/auth0-spa-js)

## Install

```
yarn add nuxt-auth0-spa
```

## Setup

add modules and auth0 setting to nuxt.config.js

```nuxt.config.js
  modules: [
    'nuxt-auth0-spa'
  ],
  auth0: {
    domain: '<YOUR_AUTH0_DOMAIN>',
    clientId: '<YOUR_AUTH0_CLIENT_ID>',
    audience: 'http://localhost:3000/'
  }
```

## Development

Running demo for development

```
yarn install
yarn dev
```

## License

[MIT License](./LICENSE)
npm package: @funkia/rudolph
Description: A purely functional router based on Hareactive
Author: Funkia
Latest version: 0.1.0

<img align="right" src="https://avatars0.githubusercontent.com/u/21360882?v=3&s=200">

# Rudolph
A pure and functional router using classic FRP. Written in TypeScript.
Experimental.

[![Build Status](https://travis-ci.org/funkia/rudolph.svg?branch=master)](https://travis-ci.org/funkia/rudolph)
[![codecov](https://codecov.io/gh/funkia/rudolph/branch/master/graph/badge.svg)](https://codecov.io/gh/funkia/rudolph)


## Install
```
npm install --save @funkia/rudolph @funkia/hareactive
```
npm package: @funkit/connect
Description: Funkit Connect SDK elevates DeFi apps via web2 sign-ins and one-click checkouts.
Author: https://fun.xyz/
Latest version: 9.5.1

## FunkitConnect

The `@funkit/connect` package elevates decentralize applications via web2 & web3 sign-ins together with one-click onramps & checkouts.

### Version Information

- Package versions `< 1.x.x` support wagmi v1 only.
- Package versions `>= 1.x.x` support wagmi v2 only.

### 📝 Note

This package is currently in closed beta. To learn more, reach out to [developers@fun.xyz](mailto:developers@fun.xyz).
npm package: @funkit/connect-v2
Description: Funkit Connect SDK elevates DeFi apps via web3 & web2 sign-ins.
Author: https://fun.xyz/
Latest version: 0.0.4

## FunkitConnect

The `@funkit/connect` package elevates decentralize applications via web2 & web3 sign-ins.

### 📝 Note

This package is currently in closed beta. To learn more, reach out to [developers@fun.xyz](mailto:developers@fun.xyz).
npm package: @funkitools/n8n-nodes-funkitools
Description: Funkitools publish node
Author: Dmitry Blinov
Latest version: 0.1.3

# n8n-nodes-funkitools

This is an n8n community node. It lets you use _app/service name_ in your n8n workflows.

_App/service name_ is _one or two sentences describing the service this node integrates with_.

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/sustainable-use-license/) workflow automation platform.

[Installation](#installation)
[Operations](#operations)
[Credentials](#credentials)
[Compatibility](#compatibility)
[Usage](#usage)
[Resources](#resources)
[Version history](#version-history)

## Installation

Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations

_List the operations supported by your node._

## Credentials

_If users need to authenticate with the app/service, provide details here. You should include prerequisites (such as signing up with the service), available authentication methods, and how to set them up._

## Compatibility

_State the minimum n8n version, as well as which versions you test against. You can also include any known version incompatibility issues._

## Usage

_This is an optional section. Use it to help users with any difficult or confusing aspects of the node._

_By the time users are looking for community nodes, they probably already know n8n basics. But if you expect new users, you can link to the [Try it out](https://docs.n8n.io/try-it-out/) documentation to help them get started._

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/#community-nodes)
* _Link to app/service documentation._

## Version history

_This is another optional section. If your node has multiple versions, include a short description of available versions and what changed, as well as any compatibility impact._