open-index/open-npm huggingface dataset:
npm package: @showpune/azure-migration-dotnet-mcp
Description: MCP server for dotnet migrate to Azure
Author: zhiyongli
Latest version: 1.0.1

# app-migration-java-mcp

1. Run `npm install`
2. Run `npm run compile`
3. Configure (another instance of) VS Code with:

```
{
    "workbench.startupEditor": "none",
    "mcp": {
        "servers": {
            "app-migration-java": {
                "type": "stdio",
                "command": "node",
                "args": ["<repo path>/build/index.js"]
            }
        }
    },
    "git.enableSmartCommit": true
}
```

4. Start the MCP server (open settings.json and use codelens, or use the command pallete)

5. How to package as npm
1) npm install 
2) npm publish --access public
npm package: @showpune/azure-migration-java-mcp
Description: MCP server for Java migrate to Azure
Author: zhiyongli
Latest version: 3.0.3

# app-migration-java-mcp

1. Run `npm install`
2. Run `npm run compile`
3. Configure (another instance of) VS Code with:

```
{
    "workbench.startupEditor": "none",
    "mcp": {
        "servers": {
            "app-migration-java": {
                "type": "stdio",
                "command": "node",
                "args": ["<repo path>/build/index.js"]
            }
        }
    },
    "git.enableSmartCommit": true
}
```

4. Start the MCP server (open settings.json and use codelens, or use the command pallete)
npm package: @showtime-xyz/apple-music-auth
Description: My new module
Author: Nishan
Latest version: 0.1.0

# @showtime-xyz/apple-music-auth

My new module

# API documentation

- [Documentation for the main branch](https://github.com/expo/expo/blob/main/docs/pages/versions/unversioned/sdk/@showtime-xyz/apple-music-auth.md)
- [Documentation for the latest stable release](https://docs.expo.dev/versions/latest/sdk/@showtime-xyz/apple-music-auth/)

# Installation in managed Expo projects

For [managed](https://docs.expo.dev/versions/latest/introduction/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects &mdash; it is likely to be included in an upcoming Expo SDK release.

# Installation in bare React Native projects

For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.

### Add the package to your npm dependencies

```
npm install @showtime-xyz/apple-music-auth
```

### Configure for iOS

Run `npx pod-install` after installing the npm package.


### Configure for Android



# Contributing

Contributions are very welcome! Please refer to guidelines described in the [contributing guide]( https://github.com/expo/expo#contributing).
npm package: @showtime-xyz/date-picker
Description: My new module
Author: Nishan
Latest version: 0.2.1

# @showtime-xyz/date-picker

My new module

# API documentation

- [Documentation for the main branch](https://github.com/expo/expo/blob/main/docs/pages/versions/unversioned/sdk/@showtime-xyz/date-picker.md)
- [Documentation for the latest stable release](https://docs.expo.dev/versions/latest/sdk/@showtime-xyz/date-picker/)

# Installation in managed Expo projects

For [managed](https://docs.expo.dev/versions/latest/introduction/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects &mdash; it is likely to be included in an upcoming Expo SDK release.

# Installation in bare React Native projects

For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.

### Add the package to your npm dependencies

```
npm install @showtime-xyz/date-picker
```

### Configure for iOS

Run `npx pod-install` after installing the npm package.


### Configure for Android



# Contributing

Contributions are very welcome! Please refer to guidelines described in the [contributing guide]( https://github.com/expo/expo#contributing).
npm package: @showtimefinance/uikit
Description: Set of UI components for pancake projects
Latest version: 0.0.1

# 🥞 Pancake UIkit

[![Version](https://img.shields.io/npm/v/@showtimefinance/uikit)](https://www.npmjs.com/package/@showtimefinance/uikit) [![Size](https://img.shields.io/bundlephobia/min/@showtimefinance/uikit)](https://www.npmjs.com/package/@showtimefinance/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 @showtimefinance/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 '@showtimefinance/uikit'
...
<ThemeProvider theme={isDark}>...</ThemeProvider>
```

### Reset

A reset CSS is available as a global styled component.

```
import { ResetCSS } from '@showtimefinance/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/)
npm package: @showwhat/configurator
Description: Reusable configurator component library for showwhat library
Latest version: 2.0.0

# @showwhat/configurator

A reusable React component library for visually editing showwhat definitions — like Swagger UI for your flag and config rules.

Provides a complete rule-builder UI while letting your app own storage, workflow, and persistence.

## Installation

```bash
npm install @showwhat/configurator
```

Peer dependencies: React 19, React DOM 19.

## Quick start

```tsx
import { Configurator } from "@showwhat/configurator";
import "@showwhat/configurator/styles.css";

function App() {
  return <Configurator store={myStore} />;
}
```

## Features

- Visual rule builder for all built-in condition types
- Drag-and-drop variation reordering
- Nested AND/OR condition groups
- Condition simulator and JSON context preview
- Store-agnostic — bring your own state management and persistence
- Exports individual components for custom layouts
- shadcn-based UI primitives included
- Tailwind CSS v4 with customisable theme tokens

## Documentation

- [Configurator](https://showwhat.yeojz.dev/docs/configurator) — store interfaces, components, hooks, styling, and examples
npm package: @showwhat/core
Description: Core rule engine and schemas for showwhat library
Latest version: 2.0.0

# @showwhat/core

Low-level schemas, parsers, and rule engine for [`showwhat`](https://www.npmjs.com/package/showwhat).

Use `@showwhat/core` when you want the evaluation primitives without the higher-level convenience API.

## Installation

```bash
npm install @showwhat/core
```

## Quick start

```ts
import { MemoryData, resolve, builtinEvaluators } from "@showwhat/core";

const data = await MemoryData.fromObject({
  definitions: {
    checkout_v2: {
      variations: [{ value: true, conditions: [{ type: "env", value: "prod" }] }, { value: false }],
    },
  },
});

const def = await data.get("checkout_v2");

const result = await resolve({
  definitions: { checkout_v2: def! },
  context: { env: "prod" },
  options: { evaluators: builtinEvaluators },
});
console.log(result.checkout_v2.value); // true
```

> **Note:** The resolver is strict — evaluators must be passed explicitly. There is no default evaluator set injected automatically.

## Features

- Built-in condition types: `string`, `number`, `datetime`, `bool`, `env`, `startAt`, `endAt`
- Composite conditions with `and`/`or` logic
- Custom condition types via evaluator composition
- YAML and JSON parsing with schema validation
- Pluggable data sources (`DefinitionReader` / `DefinitionWriter`)
- Typed error hierarchy
- Preset condition shortcuts

## Documentation

- [Quick Start](https://showwhat.yeojz.dev/docs/) — installation and first definition
- [Conditions](https://showwhat.yeojz.dev/docs/conditions) — built-in condition types and usage
- [Context](https://showwhat.yeojz.dev/docs/context) — runtime context object
- [Definitions](https://showwhat.yeojz.dev/docs/definitions) — definition structure and variations
- [Core API](https://showwhat.yeojz.dev/docs/core) — `showwhat()`, `resolve()`, parsing, and more
- [Errors](https://showwhat.yeojz.dev/docs/errors) — error types and when they are thrown
- [Custom Conditions](https://showwhat.yeojz.dev/docs/custom-conditions) — writing your own evaluators
- [Custom Data Sources](https://showwhat.yeojz.dev/docs/custom-data-sources) — implementing `DefinitionReader`
- [MemoryData](https://showwhat.yeojz.dev/docs/memory) — in-memory data source
npm package: @showwhat/openfeature
Description: OpenFeature provider for showwhat library
Latest version: 2.0.0

# @showwhat/openfeature

[OpenFeature](https://openfeature.dev/) provider for **showwhat**.

Bridge showwhat's rule engine to the standard OpenFeature Server SDK. Evaluate flags and config through OpenFeature clients using showwhat definitions.

## Installation

```bash
npm install showwhat @showwhat/openfeature @openfeature/server-sdk
```

`@openfeature/server-sdk` is a peer dependency.

## Quick start

```ts
import { OpenFeature } from "@openfeature/server-sdk";
import { ShowwhatProvider } from "@showwhat/openfeature";
import { MemoryData } from "showwhat";

const data = await MemoryData.fromYaml(yamlString);

await OpenFeature.setProviderAndWait(new ShowwhatProvider({ data }));

const client = OpenFeature.getClient();

const enabled = await client.getBooleanValue("checkout_v2", false, {
  env: "production",
});
```

## Features

- All four evaluation types: boolean, string, number, object
- Automatic context mapping from OpenFeature to showwhat
- Custom condition support via `evaluators` option
- Lifecycle management (`initialize` / `onClose`)
- Error mapping to OpenFeature error codes
- Resolution reason tracking

## Documentation

- [OpenFeature Integration](https://showwhat.yeojz.dev/docs/openfeature) - provider options, context mapping, evaluation types, error mapping, and lifecycle