open-index/open-npm huggingface dataset:
npm package: @fluid-app/fluid-payments
Description: Framework-agnostic JavaScript SDK for integrating Fluid payment methods
Latest version: 0.1.0
Deprecated: This package has been renamed to @fluid-app/payments-api-client. Install @fluid-app/payments-api-client instead.

# @fluid-app/fluid-payments

Framework-agnostic JavaScript SDK for integrating Fluid payment methods.

## Installation

```bash
npm install @fluid-app/fluid-payments
# or
pnpm add @fluid-app/fluid-payments
# or
yarn add @fluid-app/fluid-payments
```

## Usage

### ESM (Modern bundlers)

```typescript
import { FluidPayments } from "@fluid-app/fluid-payments";

const fluid = new FluidPayments({
  apiKey: "pk_live_xxx",
  environment: "production",
});

// Check available payment methods
const capabilities = await fluid.getCapabilities();
console.log(capabilities); // { applePay: true, googlePay: false, paypal: true }
```

### CommonJS

```javascript
const { FluidPayments } = require("@fluid-app/fluid-payments");

const fluid = new FluidPayments({
  apiKey: "pk_live_xxx",
  environment: "production",
});
```

### Script tag (CDN)

```html
<script src="https://unpkg.com/@fluid-app/fluid-payments"></script>
<script>
  const fluid = new FluidPayments.FluidPayments({
    apiKey: "pk_live_xxx",
    environment: "production",
  });
</script>
```

## API Reference

### `FluidPayments`

Main SDK class for initializing and managing payment methods.

#### Constructor

```typescript
new FluidPayments(config: FluidConfig)
```

#### Properties

- `version` - Current SDK version
- `environment` - Configured environment ('production' | 'sandbox')

#### Methods

- `getCapabilities()` - Returns available payment methods for current browser

## License

MIT
npm package: @fluid-app/react-widgets-types
Description: Type definitions for the `@fluid-app/react-widgets` package.
Latest version: 1.0.10

# @fluid-app/react-widgets-types

Type definitions for the `@fluid-app/react-widgets` package.

## Overview

This package contains TypeScript interfaces and type definitions extracted from the `@fluid-app/react-widgets` package. It allows other packages to use these type definitions without having to install the entire React widgets package.

## Usage

```typescript
import type {
  BannerWidgetProps,
  CartWidgetProps,
  LeadCaptureWidgetProps,
} from "@fluid-app/react-widgets-types";

// Use the types in your code
const cartWidgetConfig: CartWidgetProps = {
  position: "bottom-right",
  size: 60,
  zIndex: 9999,
};
```

## Types Included

- `CartWidgetProps`: Properties for the shopping cart widget
- `BannerWidgetProps`: Properties for the banner widget
- `LeadCaptureWidgetProps`: Properties for the lead capture form widget
- `FluidConfig`: Configuration options for the Fluid SDK
- Re-exports of types from `@fluid-app/fluid`: `ApiTypes`, `Schemas`, `EventType`

## License

MIT
npm package: @fluid-app/web-widgets-types
Description: Type definitions for the `@fluid-app/web-widgets` package.
Latest version: 0.0.30

# @fluid-app/web-widgets-types

Type definitions for the `@fluid-app/web-widgets` package.

## Overview

This package contains TypeScript interfaces and type definitions extracted from the `@fluid-app/web-widgets` package. It allows other packages to use these type definitions without having to install the entire Web Components widgets package.

## Usage

```typescript
import type {
  FluidWindow,
  WebComponentOptions,
  WidgetInfo,
} from "@fluid-app/web-widgets-types";

// Use the types in your code
const widgetDefinition: WidgetInfo = {
  dirName: "cart-widget",
  componentName: "CartWidget",
  tagName: "fluid-cart-widget",
  propsJsonPath: "./generated/cart-widget-props.js",
};
```

## Types Included

- `WidgetInfo`: Configuration for web component widgets
- `FluidWindow`: Type definitions for window object extensions
- `WebComponentOptions`: Options for web component creation
- Re-exports of types from `@fluid-app/react-widgets-types`: `CartWidgetProps`, `BannerWidgetProps`, `LeadCaptureWidgetProps`

## License

MIT
npm package: @fluid-experimental/bubblebench-baseline
Description: Bubblemark inspired DDS benchmark
Author: Microsoft and contributors
Latest version: 0.59.2004

# @fluid-experimental/bubblebench-baseline

## Getting Started

You can run this example using the following steps:

1. Run `npm install` and `npm run build:fast -- --nolint` from the `FluidFramework` root directory.
   a. For an even faster build, you can add the package name to the build command, like this:
      `npm run build:fast -- --nolint @fluid-experimental/bubblebench`
1. Run `npm run start` from this directory (experimental/examples/bubblebench/baseline) and open <http://localhost:8080> in a web browser to see the app running.
<!-- AUTO-GENERATED-CONTENT:END -->

## Testing

```bash
    npm run test:jest
```

For in browser testing update `./jest-puppeteer.config.js` to:

```javascript
  launch: {
    dumpio: true, // output browser console to cmd line
    slowMo: 500,
    headless: false,
  },
```
npm package: @fluid-experimental/bubblebench-ot
Description: Bubblemark inspired DDS benchmark
Author: Microsoft and contributors
Latest version: 0.59.2004

# @fluid-experimental/bubblebench-ot

## Getting Started

You can run this example using the following steps:

1. Run `npm install` and `npm run build:fast -- --nolint` from the `FluidFramework` root directory.
   a. For an even faster build, you can add the package name to the build command, like this:
      `npm run build:fast -- --nolint @fluid-experimental/bubblebench-ot`
1. Run `npm run start` from this directory (experimental/examples/bubblebench/ot) and open <http://localhost:8080> in a web browser to see the app running.
<!-- AUTO-GENERATED-CONTENT:END -->

## Benchmarking
Remember to produce a production bundle when taking measurements:
```bash
npm run start -- --env.production
```

## Testing

```bash
npm run test:jest
```

For in browser testing update `./jest-puppeteer.config.js` to:

```javascript
launch: {
  dumpio: true, // output browser console to cmd line
  slowMo: 500,
  headless: false,
},
```
npm package: @fluid-experimental/bubblebench-sharedtree
Description: Bubblemark inspired DDS benchmark
Author: Microsoft and contributors
Latest version: 0.59.2004

# @fluid-experimental/bubblebench-sharedtree

## Getting Started

You can run this example using the following steps:

1. Run `npm install` and `npm run build:fast -- --nolint` from the `FluidFramework` root directory.
   a. For an even faster build, you can add the package name to the build command, like this:
      `npm run build:fast -- --nolint @fluid-experimental/bubblebench`
1. Run `npm run start` from this directory (experimental/examples/bubblebench/sharedtree) and open <http://localhost:8080> in a web browser to see the app running.
<!-- AUTO-GENERATED-CONTENT:END -->

## Benchmarking
Remember to produce a production bundle when taking measurements:
```bash
npm run start -- --env.production
```

## Testing

```bash
npm run test:jest
```

For in browser testing update `./jest-puppeteer.config.js` to:

```javascript
launch: {
  dumpio: true, // output browser console to cmd line
  slowMo: 500,
  headless: false,
},
```
npm package: @fluid-experimental/get-container
Description: Tool for getting a container for testing app scenarios
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluid-experimental/get-container

The functions provided in this package are tools to get a `Container` that is configured for use with the respective services.

## Deprecated

This package should not be consumed and is in the process of being removed.

[Issue #5853 for cleaning up references to this package](https://github.com/microsoft/FluidFramework/issues/5853)
npm package: @fluid-experimental/partial-checkout
Description: A sample using property-dds and property-binder to create a reactive application.
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluid-experimental/partial-checkout
Creates a simple colored squares board. After installing and starting (directions below) you can create start creating and moving squares going to localhost:8080. Your path variable is the unique identifier for that collaborative session.

## Getting Started

After cloning the repository, install dependencies with:

Go back to the root folder and run:
```bash
npm install
alias fb='clear && node "$(git rev-parse --show-toplevel)/node_modules/.bin/fluid-build"'
fb --install --symlink:full
fb --all @fluid-experimental/partial-checkout  @fluid-experimental/property-query tinylicious
```

Then, go to property-query package and start the server to run MH:
```bash
cd experimental/PropertyDDS/services/property-query
npm start
```

You can then run the example with:

```bash
npm start
```

This will open a browser window to the example.  You can navigate to the same URL in a second window to see changes propagating between clients.

To webpack the bundle and output the result in `./dist`, you can run:

```bash
npm run build
```

## Trademark

This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks
or logos must follow Microsoft's [Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
npm package: @fluid-experimental/property-inspector
Description: TreeTable representation for property-dds which allow browsing, editing and searching.
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluid-experimental/property-inspector
An app for inspecting documents created by PropertyDDS using an efficient table-tree.

## Getting Started

After cloning the repository, install dependencies with:

Go back to the root folder and run:
```bash
npm install
alias fb='clear && node "$(git rev-parse --show-toplevel)/node_modules/.bin/fluid-build"'
fb --install --symlink:full
fb --all @fluid-experimental/property-inspector tinylicious
```

You can then run the example with:

```bash
npm start
```

This will open a browser window to the example.  You can navigate to the same URL in a second window to see changes propagating between clients.

To webpack the bundle and output the result in `./dist`, you can run:

```bash
npm run build
```
npm package: @fluid-experimental/task-manager
Description: Distributed data structure for queueing exclusive tasks
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluid-experimental/task-manager

<!-- AUTO-GENERATED-CONTENT:START (TEMPLATE:src=readme-simple.md) -->
<!-- This section is automatically generated. To update it, edit docs/md-magic.config.js  then run
'npm run build:md-magic' in the docs folder. -->

Documentation available at <https://fluidframework.com/docs/apis/task-manager>.

## Trademark

This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks
or logos must follow Microsoft's [Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.

<!-- AUTO-GENERATED-CONTENT:END -->
npm package: @fluid-internal/eslint-plugin-fluid
Description: Custom ESLint rules for the Fluid Framework
Author: Microsoft and contributors
Latest version: 0.4.1

# @fluid-internal/eslint-plugin-fluid

This package contains custom ESLint rules specific for Fluid Framework. It is consumed by the `@fluidframework/eslint-config-fluid` package as a custom plugin (check `minimal.js`'s `plugins` array).

An ESLint Plugin is an extension for ESLint that adds additional custom rules and configuration options.

See [ESLint: Name a Plugin](https://eslint.org/docs/latest/extend/plugins) for more details.

## Background

The `@fluid-internal/eslint-plugin-fluid` is directly consumed by the `@fluidframework/eslint-config-fluid` package. Although, it is a best practice to avoid multiple packages which serve similar purpose, this decision was inevitably induced by the `ESLint`'s requirements which enforce:

- Each plugin to be an npm module with a name in the format of `eslint-plugin-foo` or `@scope/eslint-plugin-foo`.

See [ESLint: Name a Plugin](https://eslint.org/docs/latest/extend/plugins#name-a-plugin) for more details. If there is a development in unifying the separate package structure, it should be done to ensure stronger package maintainability.

## Rules

Browser `src/rules` to check more information on the individual rules.
npm package: @fluid-music/utils
Description: CLI Helpers for building fluid music recipes
Author: Charles Holbrow
Latest version: 0.8.3

# Fluid Music Utilities

This installs several CLI helper tools for creating `fluid-music` recipes.

Use `npm install -g @fluid-music/utils` to install:

- `afactory`
- `transcribe-chords`

## `afactory`

Recursively searches a directory for audio files, and generates a fluid-music
AudioFile technique for each audio file it finds. The output techniques will be
written to a common.js formatted JavaScript file which exports a deeply nested
JavaScript object reflecting the input directory structure.

### Usage:

`$ afactory ./search/dir [outfile='audio-files.js']`

### Example:
Assume your working directory contains the following files:

```
./drums/snare.wav
./drums/hi-hat/close.wav
./drums/hi-hat/open.wav
```

**Step 1:** Run `afactory` from the working directory:

```
$ afactory ./ audio.js
```

**Step 2:** `afactory` will create an `audio.js` file, which looks like this:
```javascript
const { AudioFile } = require('fluid-music').techniques
module.exports = {
  "drums": {
    "snare.wav":   new AudioFile({ /* init options */ }),
    "hi-hat": {
      "close.wav": new AudioFile({ /* init options */ }),
      "open.wav":  new AudioFile({ /* init options */ }),
    },
  },
};
```
**Step 3:** You can now `require('./audio.js')`, to access the exported objects,
using them to manually create fluid-music `tLibrary` objects.


## `transcribe-chords`

A super quick way to transcribe midi chords in JSON using a midi keyboard.

```
$ npm install -g @fluid-music/utils
$ transcribe-chords chords.js
Usage: $ transcribe-chords out.js # (Currently writing to "chords.js")
connected: "Midi Through Port-0"
connected: "MPK Mini Mk II MIDI 1"
```

Now play some chords on any connected midi device to generate a file like the one below (use `ctrl+c` to stop recording).

```javascript
const fluid = require('fluid-music')
const { MidiChord } = fluid.techniques

const chords = [
  new MidiChord({
    name: 'Gm',
    notes: [55, 58, 62],
  }),

  new MidiChord({
    name: 'Bbsus4',
    notes: [58, 60, 63, 65],
  }),

  new MidiChord({
    name: 'Cm',
    notes: [60, 63, 67],
  }),
]

module.exports = chords
```

You can create a `tLibrary` like this:

```javascript
const fluid = require('fluid-music')
const chords = require('./midi-chords')

const tLibrary = fluid.tLibrary.fromArray(techniques)

// tLibrary will look like this:
{
  a: MidiChord({ name: 'Gm',     notes: [55, 58, 62] }),
  b: MidiChord({ name: 'Bbsus4', notes: [58, 60, 63, 65] })
  c: MidiChord({ name: 'Cm',     notes: [60, 63, 67] }),
}
```
npm package: @fluid-network/msg-reader
Description: Convert common fluid.js msg to a sentence
Author: Fluid Labs
Latest version: 3.0.1

# @terra-money/msg-reader

Convert common terra.js msg to a sentence

## Installation

```
npm i @terra-money/msg-reader
```

## Example codes

```typescript
import { Coins, Coin, MsgSend } from "@terra-money/terra.js"
import { readMsg } from "@terra-money/msg-reader"

const coins = new Coins([new Coin("uluna", 1000000), new Coin("ukrw", 1000000)])

const address = "terra1x46rqay4d3cssq8gxxvqz8xt6nwlz4td20k38v"
const recipient = "terra17lmam6zguazs5q5u6z5mmx76uj63gldnse2pdp"

const msg = new MsgSend(address, recipient, [coin])

console.log(readMsg(msg))
// Send 1 Luna to terra17lmam6zguazs5q5u6z5mmx76uj63gldnse2pdp
```