open-index/open-npm huggingface dataset:
npm package: @relevanc/rcap-sdk-web
Description: RCAP Display - Web SDK providing useful primitives to instrument websites looking to sell digital inventories
Author: Relevanc
Latest version: 3.1.1
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# RC AP Web SDK

This library aims to provide useful tools to integrate retailer websites with
the RC AP ecosystem. Those might include wrappers, validators, formatters and
other primitives.
npm package: @relevance/angular-apps
Description: Relevance.io application toolkitlibrary for Angular
Author: Relevance.io
Latest version: 1.0.6
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Relevance.io Angular Applications toolkit

This software development kit aims to provide reuseable modules and components for building
web applications on top of the Relevance.io APIs, through the Angular library.

## Getting started

### Requirements

These are the general requirements for using this package:

- Node 12 or higher is recommended
- npm 6.14 or higher is recommended
- Angular 9+

### Installation

To install from the public repositories, run:

    npm install @relevance/angular-apps

Remember to install any peer dependencies for Angular (like `@angular/material` and `@angular/cdk`).

## Usage

This library is an Angular library that augments the `@relevance/angular-core` library for the
specific purpose of rapid application development.

To use this library, first load the module with want to use in an `NgModule`:

    import { SearchModule, SearchServiceConfig } from '@relevance/angular-apps';

    @NgModule({
        imports: [
            SearchModule.forRoot({
                queryConfig: {
                    url: 'https://url/to/query/api',
                },
            })
        ],
    })
    export class MyModule { }

Then use the DI mechanisms from Angular, e.g.:

    @Component({ ... })
    export class MyComponent {
        constructor(
            private searchService: SearchService,
        ) { }

        public suggestSomething() {
            this.searchService.suggest('something').then(() => { ... });
        }
    }

## Building and testing

To test a distribution, use:

    npm run test            # runs the tests
    npm run lint            # validates code syntax

Then build with:

    npm run build

### Development mode

This package provides an stream-lined way of locally installing dependencies, building and
linking for a development environment. The "development mode" basically installs the
dependencies and builds the package so that it can be used in cross-linked packages.

To use it, first install the dependencies in development mode:

    npm run install:dev

When building, use:

    npm run build:dev

This installs and builds the package as a *global package* that can be linked to other
dependent packages without first having to publish it.

## License

This code and its documentation is provided under the MIT License, bundled as the `LICENSE`
file. All original rights are reserved to Relevance.io 2020-.
npm package: @relevance/angular-core
Description: Relevance.io wrapper library for Angular
Author: Relevance.io
Latest version: 1.0.6
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Relevance.io Angular SDK

This software development kit aims to provide a standard interface to connect to the Relevance.io
APIs in Angular applications.

## Getting started

### Requirements

These are the general requirements for using this package:

- Node 12 or higher is recommended
- npm 6.14 or higher is recommended
- Angular 9+

### Installation

To install from the public repositories, run:

    npm install @relevance/angular-core

Make sure the proper `@angular` dependencies are installed as well, as they are defined as
peer dependencies.

## Usage

This library is an Angular wrapper for the `@relevance/core` package and exposes the same
interfaces, with the addition of Angular dependency injection support.

To use this library, first load the module with want to use in an `NgModule`:

    import { QueryModule, QueryServiceConfig } from '@relevance/angular-core';

    @NgModule({
        imports: [
            QueryModule.forRoot({
                url: 'https://url/to/query/api',
            })
        ],
    })
    export class MyModule { }

Then use the DI mechanisms from Angular, e.g.:

    @Component({ ... })
    export class MyComponent {
        constructor(
            private queryService: QueryService,
        ) { }

        public doSomething() {
            this.queryService.search().then(() => { ... });
        }
    }

## Building and testing

To test a distribution, use:

    npm run test            # runs the tests
    npm run lint            # validates code syntax

Then build with:

    npm run build

### Development mode

This package provides an stream-lined way of locally installing dependencies, building and
linking for a development environment. The "development mode" basically installs the
dependencies and builds the package so that it can be used in cross-linked packages.

To use it, first install the dependencies in development mode:

    npm run install:dev

When building, use:

    npm run build:dev

This installs and builds the package as a *global package* that can be linked to other
dependent packages without first having to publish it.

## License

This code and its documentation is provided under the MIT License, bundled as the `LICENSE`
file. All original rights are reserved to Relevance.io 2020-.
npm package: @relevanceai/eslint-plugin
Description: Relevance AI ESLint rules
Author: Soorria Saruva
Latest version: 0.5.0

This package contains custom ESLint rules that we use here at [Relevance AI](https://relevanceai.com/). These rules aren't intended for public usage (some of them are quite specific and opinionated), so we don't recommend using them in your projects.

## Rule overviews

See the implementations for more specifics.

### no-vitest-and-expect-package

This rule errors when importing from both `expect` and `vitest` in the same file. When using vitest, you should use its version of `expect()`.

### prefer-function-as-describe-label

This rule errors when a string literal or `Function.name` is passed to Vitest's `describe` function. You should pass the function directly, so the describe block name stays in-sync with the function name.

Bad:

```js
function Foo() {}
describe('Foo', () => {})
```

```js
function Foo() {}
describe(Foo.name, () => {})
```

Good:

```js
function Foo() {}
describe(Foo, () => {})
```

### prefer-vi-mock-import-expression

This rule errors when passing a path to `vi.mock`. You should pass an import expression instead as this:

- makes `vi.mock` type-safe since we can't refer to modules that don't exist.
- allows TypeScript to infer the correct type for the mock factory (2nd arg to `vi.mock`).
- makes refactoring by moving files around easier since VSCode updates import expressions when you do.

Bad:

```js
vi.mock('~/dependencies', () => {})
```

Good:

```js
vi.mock(import('~/dependencies'), () => {})
```

### pascal-case

This rule errors when a variable, containing a function, doesn't have a PascalCase name.
The rule was written to replace @typescript-eslint/naming-convention for our needs, since it was taking up about 25 seconds, or about 40%, of the time taken to lint one of our repos.

Bad:

```js
const foo = () => {}
```

Good:

```js
const Foo = () => {}
```

We intentionally don't generate fixes for the naming violations, since that would require analysing which parts of a variable are words/acronyms.
npm package: @relevanceai/relevanceai-mcp-server
Description: MCP server for using relevanceai tools
Latest version: 0.1.1

# Relevanceai MCP Server

This server allows you to use your Relevance AI tools (or studios) within MCP-compatible clients like Cursor or Claude.

## Usage with NPX

The easiest way to run this server is using `npx`. You need Node.js and npm installed.

In your MCP client's configuration (e.g., Cursor's settings), set the "MCP Server Command" to the following.
First, ensure you have the `RELEVANCE_AUTH_TOKEN` environment variable set with your Relevance AI API key.
Then, use the command, replacing the placeholders with your actual values:

```bash
npx @relevanceai/relevanceai-mcp-server@latest --region YOUR_RELEVANCE_REGION --tools YOUR_TOOL_ID1,YOUR_TOOL_ID2
```

**Environment Variable:**

- `RELEVANCE_AUTH_TOKEN`: Your Relevance AI API key (create one under Account -> Integrations in your Relevance AI dashboard). **This must be set in your environment.**

**Command-line Arguments:**

- `--region YOUR_RELEVANCE_REGION`: Your Relevance AI region (e.g., `1e3042`).
- `--tools YOUR_TOOL_ID1,YOUR_TOOL_ID2`: A comma-separated list of the Tool IDs you want to expose.

**Example:**

Assuming `RELEVANCE_AUTH_TOKEN` is set in your environment (e.g., `export RELEVANCE_AUTH_TOKEN="abcdef12345"`):

```bash
npx @relevanceai/relevanceai-mcp-server@latest --region 1e3042 --tools tooldId1,toolId2
```

## Development Setup

If you want to contribute or modify the server:

1.  Clone the repository: `git clone https://github.com/RelevanceAI/relevanceai-mcp-server`
2.  Navigate to the directory: `cd relevanceai-mcp-server`
3.  Install dependencies: `npm install`
4.  Build the project: `npm run build`
5.  Run locally (for testing):
    First, set the environment variable:
    `export RELEVANCE_AUTH_TOKEN="YOUR_RELEVANCE_AUTH_TOKEN"`
    Then, run the server with arguments:
    `npm start -- --region <region> --tools <toolId1,toolId2>`

## Logging

The server uses `console.error` for logging. This is compatible with how MCP clients capture server output. Avoid using `console.log` as it can interfere with the MCP communication protocol.
npm package: @relevanceai/sdk
Description: The official JavaScript/TypeScript SDK for building applications with Relevance AI agents and workforces.
Latest version: 3.1.0

# Relevance AI JavaScript SDK

The official JavaScript/TypeScript SDK for building applications
with Relevance AI agents and workforces.

- **Universal runtime support** - Node.js, Deno, Bun, Cloudflare
  Workers, and browsers
- **Event-driven architecture** - real-time updates via the native
  EventTarget API
- **Type-safe** - full TypeScript support with comprehensive type
  definitions
- **Zero dependencies** - built entirely on web standards

## Installation

```bash
npm install @relevanceai/sdk@latest
```

For Deno, Bun, CDN, and browser bundler setup, see the
[Setup guide](./docs/00_SETUP.md).

## Quick Start

```typescript
import { Agent, createClient, REGION_US } from "@relevanceai/sdk";

createClient({
  apiKey: process.env.RELEVANCE_API_KEY,
  region: REGION_US,
  project: process.env.PROJECT_ID,
});

const agent = await Agent.get("agent-id");
const task = await agent.sendMessage("Hello!");

task.addEventListener("message", ({ detail: { message } }) => {
  if (message.isAgent()) {
    console.log("Agent:", message.text);
  }
});
```

## Documentation

| Guide | Description |
| ----- | ----------- |
| [Setup](./docs/00_SETUP.md) | Installation and runtime configuration |
| [Authentication](./docs/01_AUTH.md) | API keys, embed keys, and regions |
| [Client](./docs/02_CLIENT.md) | Client initialization and singleton pattern |
| [Agents](./docs/03_AGENTS.md) | Loading agents and starting conversations |
| [Tasks](./docs/04_TASKS.md) | Task lifecycle, events, and subscriptions |
| [Messaging](./docs/05_MESSAGING.md) | Messages, attachments, and type guards |
| [Workforces](./docs/06_WORKFORCES.md) | Multi-agent orchestration |
| [Streaming](./docs/07_STREAMING.md) | Real-time thinking and typing tokens |

## Examples

Working examples are available in `internal/examples/`:

- **Deno** (`internal/examples/deno/`) - agent tasks, pagination,
  embed keys, image OCR, workforce tasks
- **Browser** (`internal/examples/browser/chat/`) - full chat
  application built with Preact

## Development

The SDK is developed with Deno and published to npm and JSR.

```bash
# clone the repository
git clone https://github.com/RelevanceAI/relevance-js-sdk.git
cd relevance-js-sdk

# build the npm package
deno run -A internal/tasks/dnt.ts
```

## License

MIT

## Security

For security vulnerabilities, please email security@relevanceai.com
directly rather than using public issue trackers.

## Support

- [GitHub Issues](https://github.com/RelevanceAI/relevance-js-sdk/issues)
- [Discord](https://discord.gg/relevanceai)
npm package: @relevant/compiler
Description: > Relevant Compiler
Author: Simon Siefke
Latest version: 0.0.12

# @relevant/compiler

> Relevant Compiler

## Installation

```sh
npm i @relevant/compiler
```

## Usage

```js
import { compile } from '@relevant/compiler'

const code = `x = 1`
compile(code) // 'let x = 1'
```
npm package: @relewise/medusa
Description: A Relewise integration for Medusa
Author: Relewise
Latest version: 1.1.0

<p align="center">
  <a href="https://www.relewise.com/">
    <img alt="Relewise" src=".github/banner.png">
  </a>
</p>

---
# Relewise plugin for Medusa [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE) [![npm version](https://badge.fury.io/js/@relewise%2Fmedusa.svg)](https://badge.fury.io/js/@relewise%2Fmedusa) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/Relewise/relewise-integrations-medusa/pulls)
Relewise is a modern personalization and search engine that creates the truly personalized experiences your customers expect.

The plugin helps integrating products into Relewise with a single click and keeping products in sync every hour!

## Installation
Run the following command to install the plugin:

```W
npm install @relewise/medusa
```

## Configuration

The plugin requires som options that we recommended you to store in a `.env` file.

```W
RELEWISE_DATASET_ID=
RELEWISE_API_KEY=
RELEWISE_SERVER_URL=
```

Fill the `RELEWISE_DATASET_ID`, `RELEWISE_API_KEY`, `RELEWISE_SERVER_URL` with your dataset, api-key and server-url found at [My.Relewise](https://my.relewise.com/developer-settings).

Configure the plugin by adding it to `plugins` in your `medusa-config.ts`.

Note that providing a language and a list of currenies is also required!

```W
module.exports = defineConfig({
  // ...
  plugins: [
    {
      resolve: "@relewise/medusa",
      options: {
        datasetId: process.env.RELEWISE_DATASET_ID!,
        apiKey: process.env.RELEWISE_API_KEY!,
        serverUrl: process.env.RELEWISE_SERVER_URL!,
        language: "en",
        currencies: ["eur", "usd"]
      },
    },
  ],
})
```
## Storing workflow executions
To store workflow executions, you need to have redis installed and running.

You can read how to do so in the [Medusa Documentation](https://docs.medusajs.com/resources/infrastructure-modules/workflow-engine/redis).

## Contributing

Pull requests are always welcome.  
Please fork this repository and make a PR when you are ready with your contribution.  

Otherwise you are welcome to open an Issue in our [issue tracker](https://github.com/Relewise/relewise-integrations-medusa/issues).

## License

relewise-integrations-medusa is licensed under the [MIT license](./LICENSE).
npm package: @relewise/uniform-canvas
Description: Relewise data enhancers for Uniform Canvas
Author: Relewise
Latest version: 1.1.0

## Relewise data enhancers for Uniform Canvas.

Used on the [Uniform Platform](https://uniform.app).

## Usage examples

For usage documentation go to our [GitHub repository](https://github.com/Relewise/relewise-integrations-uniform-canvas).
npm package: @relforce/morebnb-uikit
Description: Set of UI components for pancake projects
Latest version: 1.0.0

# 🥞 Pancake UIkit

[![Version](https://img.shields.io/npm/v/@pancakeswap-libs/uikit)](https://www.npmjs.com/package/@pancakeswap-libs/uikit) [![Size](https://img.shields.io/bundlephobia/min/@pancakeswap-libs/uikit)](https://www.npmjs.com/package/@pancakeswap-libs/uikit)

Pancake UIkit is a set of React components and hooks used to build pages on Pancake's apps. It also contains a theme file for dark and light mode.

## Install

`yarn add @pancakeswap-libs/uikit`

## Setup

### Theme

Before using Pancake UIkit, you need to provide the theme file to styled-component.

```
import { ThemeProvider } from 'styled-components'
import { light, dark } from '@pancakeswap-libs/uikit'
...
<ThemeProvider theme={isDark}>...</ThemeProvider>
```

### Reset

A reset CSS is available as a global styled component.

```
import { ResetCSS } from '@pancakeswap-libs/uikit'
...
<ResetCSS />
```

### Types

This project is built with Typescript and export all the relevant types.

## How to use the UIkit

If you want to use components from the UIkit, check the [Storybook documentation](https://pancakeswap.github.io/pancake-uikit/)