open-index/open-npm huggingface dataset:
npm package: @fluid-svg/functions
Description: Create smoothly animated SVG assets with ease
Author: Michal Bajcar
Latest version: 0.0.5

# Fluid SVG

Create fluidly moving or animating SVG elements for modern websites with ease.

## Introduction

Fluid-Motion is an npm package that provides a set of functions and components to create smooth and seamless animations for SVG elements. While there are many options available for static SVG shapes, there are few solutions that allow you to achieve fluid and dynamic motion. This package aims to fill that gap, making it easy to bring life to your SVG graphics on any modern website.

## Features

- **Fluid Motion Functions**: The package includes a variety of functions that enable you to create smooth, fluid animations for SVG elements. These functions can be used standalone or combined to achieve complex motion effects.

- **Framework Support**: Fluid-Motion is designed to be compatible with popular frameworks such as Vanilla JS, React, Vue, and more. It provides dedicated components tailored to each framework, allowing you to seamlessly integrate fluid motion into your projects.

- **Written in TypeScript**: The entire package is written in TypeScript, ensuring strong typing and enhancing the development experience. TypeScript support enables autocompletion, type checking, and improved code documentation.

## Installation

To install Fluid-Motion, simply run the following command:

```bash
npm i @fluid-svg/functions
```

## Usage

Here's a basic example of how you can use the Fluid-Motion package in your project:

```html
<!-- Add simple HTML markup -->
<svg id="MySvg" height="500" width="500" xmlns="http://www.w3.org/2000/svg">
  <path stroke="blue" strokeWidth="0.005" />
  <path stroke="red" strokeWidth="0.005" />
  <path stroke="green" strokeWidth="0.005" />
</svg>
```

```javascript
import { animateWaves } from '@fluid-svg/functions'

// Animate an SVG element
animateWaves('#MySvg')
```

For more detailed usage instructions and examples, refer to the documentation provided in the docs directory.

## Contributing

Contributions are welcome! If you encounter any issues or have suggestions for improvements, please feel free to submit a pull request. For more information on how to contribute, check out the Contribution Guidelines.

## License

Fluid-Motion is licensed under the MIT License. See the LICENSE file for more details.
npm package: @fluidapps/csvify
Description: Thin wrapper around node-csv-stringify providing a simple callback interface, sensible defaults and a few extras.
Author: FluidApps
Latest version: 0.2.1

# csvify

Thin wrapper around [node-csv-stringify](https://github.com/wdavidw/node-csv-stringify)
providing a simple callback interface, sensible defaults and a few extras.

## Installation

```
npm install @fluidapps/csvify
```

## Basic usage

```javascript
var csvify = require('@fluidapps/csvify');

csvify(objectArray, function(err, data) {
  // data is a CSV representation of objectArray
});
```

## Options

- `excelFriendly`: prepend the resulting data with `sep=` to hint Excel into
automatically importing the CSV

- `stringifier`: options object passed directly to [node-csv-stringify options](http://csv.adaltas.com/stringify/)

### Defaults

```javascript
csvify(objectArray, {
  excelFriendly: false,
  stringifier: {
    header: true
  }
}, callback);
```
npm package: @fluidapps/superagent-defaults
Description: Create some defaults for superagent requests
Author: Cameron Bytheway
Latest version: 0.1.13

superagent-defaults [![Build Status](https://travis-ci.org/camshaft/superagent-defaults.png)](https://travis-ci.org/camshaft/superagent-defaults)
===================

Create some defaults for superagent requests

Usage
-----

```js
var defaults = require('superagent-defaults');

// Create a defaults context
var superagent = defaults();

// Setup some defaults
superagent
  .set('my-default-header', 'my-default-value')
  .auth('myUsername', 'myPassword')
  .on(function (req){
    console.log(req.url);
  });

// Use superagent like you always have; the defaults will be applied to
// each request automatically
superagent
  .get('/my-api')
  .end(function(res) {
    console.log(res.text);
  });
```

You may also pass a function that implements the superagent interface.

```js
var defaults = require('superagent-defaults');
var supertest = require('supertest');

var request = defaults(supertest(app));

request
  .get('/my-test-path')
  .end(function(err, res) {
    console.log(res.text);
  });
```

Tests
-----

```sh
$ npm test
```
npm package: @fluidchains/explorer-lookup
Description: A low level blockchain explorers lookup
Author: Julien Fraichot
Latest version: 0.0.1

# explorer-lookup

[![codecov](https://codecov.io/gh/blockchain-certificates/explorer-lookup/branch/master/graph/badge.svg?token=03DHST3VG7)](https://codecov.io/gh/blockchain-certificates/explorer-lookup)

Low level tool to make blockchain explorer(s) calls - REST and RPC
npm package: @fluidchains/ywpl-token-metadata
Description: MPL Token Metadata JavaScript API.
Author: Fluidchains
Latest version: 0.0.1

# mpl-token-metadata

This package contains the token vault contract SDK code.

## API Docs

Find the [token-metadata API docs published here](https://metaplex-foundation.github.io/metaplex-program-library/docs/token-metadata/index.html).

## Installation

```shell
npm install @fluidchains/ywpl-token-metadata --save
```

This will use the new auto-generated API. If you want to use the old deprecated API, you can use the following:

```shell
npm install @fluidchains/ywpl-token-metadata@^1.2 --save
```

Alternatively, if you'd like to start using the new API but still have access to the deprecated one, you may use the following:

```sh
npm install @fluidchains/ywpl-token-metadata@~2.0 --save
```

And use the deprecated API explicitly like so:

```ts
import { deprecated } from "@fluidchains/ywpl-token-metadata";
```

## Developing

In order to update the generated SDK when the rust contract was updated please run:

```
yarn gen:api
```

and then update the wrapper code and tests.

## LICENSE

Apache v2.0
npm package: @fluidchains/ywpl-token-vault
Description: MPL Token Vault JavaScript API.
Author: Fludichains
Latest version: 0.0.3

# ywpl-token-vault

This package contains the token vault contract SDK code.

## API Docs


Find the [token-vault API docs published
here](https://metaplex-foundation.github.io/metaplex-program-library/docs/token-vault/index.html).

Addiontally the [`./examples`](./examples) do a good job at documenting the SDK API as well as the
[`./tests'`](./tests).

## Developing

In order to update the generated SDK when the rust contract was updated please run:

```
yarn gen:api
```

and then update the wrapper code and tests.

## LICENSE

Apache v2.0
npm package: @fluidcoins/react-native-mono
Description: Connect your React native app with Mono. No Native linking. Works out of the box :)
Author: Lanre Adelowo
Latest version: 0.2.0

# react-native-mono

This package allows you implement the Mono widget in your React Native application.

> Demo can be found at https://recordit.co/zJGP7SKbee

### Installation

- NPM
```
$ npm install react-native-webview @fluidcoins/react-native-mono
```

- Yarn

```
$ yarn add react-native-webview @fluidcoins/react-native-mono
```

> This library only requires `react-native-webview` as a peer dependency. This is to prevent having to deal
with npm's multiple multiple versions issues. If you have it installed already in your project, you can install this
library only

### Linking

None :)

Although, if you installed `react-native-webview`, you will need to run `npx pod-install`


### Usage

```

import Mono from '@fluidcoins/react-native-mono';
import {View} from 'react-native';
import React, {useEffect} from 'react';
import {useDispatch} from 'react-redux';

const ConnectMono = ({navigation}) => {
  const dispatch = useDispatch();

  return (
    <View style={{flex: 1}}>
      <Mono
        publicKey={'test_pk_XYZ'}
        onClose={(e) => {
          navigation.pop();
        }}
        onSuccess={(code) => {
          console.log('Code from Mono', code);
          // Connect to backend here
          // dispatch(authenticateMonocode(code))
          navigation.pop();
        }}
      />
    </View>
  );
};

export default ConnectMono;

```

### Props

These props are currently available

- `publicKey` : This is your mono public key. Please don't make use of your secret key.
- `onClose`: This is called when the Mono widget is closed
- `onSuccess(code)`: This is called when the user successfully authenticate with Mono. The code should be sent to the backend for
  authorization and account retrieval.
- `loaderColor` : Before Mono is loaded, an `ActivityIndicator` is shown, this
  prop configures the color. If not provided, it defaults to `#035AA6`
npm package: @fluidcoins/sdk
Description: FluidCoins NodeJS SDK
Author: Faithful Ojebiyi
Latest version: 0.2.0


# FluidCoins NodeJS SDK

The Official Node.js library for the Fluidcoins API.

## Installation

Install node-client with npm

```bash
  npm i @fluidcoins/sdk
```

## Usage/Examples

#### create a new crypto deposit address

```javascript
const Fluidcoins = require('@fluidcoins/sdk')

fluidcoins = new Fluidcoins(secretKey)

// code can be any supported currency
// network can be any supported currency. If no network is provided, the default
// network is used
const addresses = fluidcoins.createNewAddress({ code: 'USDT', network: 'POLYGON' })

```


#### create a payment link


```javascript
const Fluidcoins = require('@fluidcoins/sdk')

fluidcoins = new Fluidcoins(secretKey)

const paymentData = {
  amount: 100000,
  description: "Test payment description",
  title: "Test Payment",
};

const link = fluidcoins.createNewPaymentLink(paymentData);

```


#### fetch supported currencies ( crypto and fiat currencies )

```javascript
const Fluidcoins = require('@fluidcoins/sdk')

fluidcoins = new Fluidcoins(secretKey)

const supportedCurrencies = fluidcoins.getCurrencies()

```


#### fetch balances

```javascript
const Fluidcoins = require('@fluidcoins/sdk')

fluidcoins = new Fluidcoins(secretKey)

const balances = fluidcoins.getBalance()

```

## Documentation/API reference

[Documentation](https://developers.fluidcoins.com)
npm package: @fluidcoins/vue-fluidcoins
Description: A Vue Plugin for Fluidcoins payment button.
Author: Fluidcoins Inc.
Latest version: 0.1.0

# Fluidcoins Component for Vue
A Vue Plugin for Fluidcoins payment button.

## Installation
``` 
    npm install @fluidcoins/vue-fluidcoins --save 

    # OR
    
    yarn add @fluidcoins/vue-fluidcoins 

```

### Usage
```
import Fluidcoins from '@fluidcoins/vue-fluidcoins'

```
```
    <fluidcoins 
        type="secondary"
        rounded
        publicKey="PUBLIC_KEY"
        :amount="90000"
        email="myemail.com"
        :on-success="onSuccess"
    />
```

### API


| Prop  | Required | Type | Default |
| ------------- | ------------- | ------------- | ------------- |
|  publicKey | true  | string   | `undefined    `. Public key from [Fluidcoins' Dashboard](https://dashboard.fluidcoins.com ).   |
|  amount | true  |  number  | `undefined`  |
|  email | true  |  string  |  `undefined` |
|  on-success | true   | function    | `undefined`  |
|  type | false  |   string | 'primary'   |
|  rounded | false  | boolean   | `true`  |
|  on-load | false  |  function  | `() => {}`  |
|  on-close | false  | function   | `() => {}`  |
|  on-error | false  |  function  | `() => {}`  |
|  name |  false |  string |  `undefined` |
|  phone  |  false |  string  |  `undefined` |
|  metadata | false  | Object   |  `{}` |
|  callback_url | false  | string   |  `undefined` |
|  currency | false  | string   | Defaults to default currency set on [Fluidcoins' Dashboard](https://dashboard.fluidcoins.com ) |



Please checkout [Fluidcoins' Documentation](https://developers.fluidcoins.com/docs/overview) for other options to help you accept crypto payments online easily.
npm package: @fluidframework/iframe-driver
Description: Connection Fluid service API that crosses iframe boundary
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluidframework/iframe-driver

This is an implementation of a driver which provides a DocumentService which consumes another socket storage
and then proxies that document storage across the iframe boundary. The inner frame can interact
with the existing endpoints like Document Storage, Delta Storage and Delta stream.
It provides implementation of Document Storage, Delta Storage and Delta stream.
npm package: @fluidframework/local-web-host
Description: Fluid local in-memory server for running in a webpage
Author: Microsoft
Latest version: 0.26.10

# @fluidframework/local-web-host

This package allows hosting a container, or Fluid object on a webpage running against a local in-memory server.

The primary use cases for this package for displaying Fluid object demos in documentation, which illustrate their behavior, without connecting to a server.

See the example.html for an example of how this is done.

See [GitHub](https://github.com/microsoft/FluidFramework) for more details on the Fluid Framework and packages within.
npm package: @fluidframework/protocol-definitions
Description: Fluid protocol definitions
Author: Microsoft and contributors
Latest version: 4.0.0

# @fluidframework/protocol-definitions

Core set of Fluid protocol interfaces shared between services and clients.
These interfaces should always be back and forward compatible.

**Topics covered below:**

-   [NoOps](#NoOps)

## NoOps

Definition: NoOps are empty operation message, with the type of `MessageType.NoOp`. They are used to send an updated referenceSequenceNumber to service. Relay service is free to coalesce these messages, or fully drop them if another op was used to update Minimum Sequence Number, to a number equal to or higher than the referenceSequenceNumber in Noop. Client will send NoOps periodically, see `NoopHeuristic`.

Expectations: NoOps can be coalesced by service, which means:

1. NoOp can be dropped by service. In such case, we observe a gap in clientSequenceNumber (otherwise all ops for a given clientId have sequential clientSequenceNumber values).
2. NoOp can be delayed by service (sequenced later in time) and be reordered relative to ops that naturally follow it. That said, reordering can only happen across ops from different clients (if more ops are sent and sequenced by given client, then noop is simply dropped in such case).

See [GitHub](https://github.com/microsoft/FluidFramework) for more details on the Fluid Framework and packages within.
npm package: @fluidframework/test-end-to-end-tests
Description: End to end tests
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluidframework/test-end-to-end-tests

These tests can be written by using the [test-utils](../test-utils/src).

Check out the test-utils [README](../test-utils/README.md) that outlines how to write a test.

## Example

Take a look at the [SharedStringEndToEndTest](src/test/sharedStringEndToEndTests.spec.ts) for a basic example
of how to write an end-to-end test.

That same [directory](src/test) contains more complex examples too.

## "Real Service" Tests

The tests under the `real-service-tests` dir target a live production service like r11s or ODSP's Fluid server.
These are run via `npm run test:realsvc:mocha`, and are included in the CI such that a test failure doesn't
fail the pipeline - since a service outage or network hiccup could cause a failure when no code defect is present.
npm package: @fluidframework/test-pairwise-generator
Description: End to end tests
Author: Microsoft and contributors
Latest version: 1.4.0

# @fluidframework/test-pairwise-generator

See [examples.spec.ts](./src/test/examples.spec.ts) for usage examples

## 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: @fluidframework/tree-agent-langchain
Description: LangChain integration helpers for @fluidframework/tree-agent
Author: Microsoft and contributors
Latest version: 2.92.0

# @fluidframework/tree-agent-langchain

Utilities for connecting LangChain chat models to the Fluid Framework `@fluidframework/tree-agent` package.

## Installation

```bash
npm install @fluidframework/tree-agent-langchain
```

## Usage

```typescript
import { createLangchainChatModel } from "@fluidframework/tree-agent-langchain";
import { ChatOpenAI } from "@langchain/openai";

const chatModel = new ChatOpenAI({ model: "gpt-4.1" });
const sharedTreeChatModel = createLangchainChatModel(chatModel);
```

The returned `SharedTreeChatModel` can be provided to `SharedTreeSemanticAgent` from `@fluidframework/tree-agent`.

## Licensing

This project is licensed under the [MIT License](./LICENSE).
npm package: @fluidframework/tree-agent-ses
Description: SES integration helpers for @fluidframework/tree-agent
Author: Microsoft and contributors
Latest version: 2.92.0

# @fluidframework/tree-agent-ses

Secure edit execution helpers for the `@fluidframework/tree-agent` package backed by the SES runtime.

## Installation

```bash
npm install @fluidframework/tree-agent-ses
```

## Usage

```typescript
import { createSesEditExecutor } from "@fluidframework/tree-agent-ses";

const executeEdit = createSesEditExecutor();
```

The returned callback can be provided as the `executeEdit` option when constructing a `SharedTreeSemanticAgent` from `@fluidframework/tree-agent`.

## Licensing

This project is licensed under the [MIT License](./LICENSE).