open-index/open-npm huggingface dataset:
npm package: @plutotcool/prettier-config
Description: Base prettier configuration for plutot.cool projects.
Author: Bastien Robert
Latest version: 1.1.0

# Prettier configuration

> Base prettier configuration for plutot.cool projects.

## Installation

```bash
pnpm i -D @plutotcool/prettier-config
```

In package.json

```json
{
  "prettier": "@plutotcool/prettier-config"
}
```
npm package: @plutotcool/rollup-plugin-glsl
Description: Rollup plugin that allows imports of glsl files
Author: Julien Dargelos
Latest version: 1.2.1

# rollup-plugin-glsl

[![test](https://github.com/plutotcool/glsl-bundler/actions/workflows/test.yml/badge.svg)](https://github.com/plutotcool/glsl-bundler/actions/workflows/test.yml)
[![build](https://github.com/plutotcool/glsl-bundler/actions/workflows/build.yml/badge.svg)](https://github.com/plutotcool/glsl-bundler/actions/workflows/build.yml)
[![release](https://github.com/plutotcool/glsl-bundler/actions/workflows/release.yml/badge.svg)](https://github.com/plutotcool/glsl-bundler/actions/workflows/release.yml)
[![version](https://img.shields.io/github/package-json/v/plutotcool/glsl-bundler?filename=packages%2Frollup-plugin-glsl%2Fpackage.json)](https://npmjs.com/package/@plutotcool/rollup-plugin-glsl)
![types](https://img.shields.io/npm/types/@plutotcool/rollup-plugin-glsl)

Rollup plugin that allows imports of glsl files. Resolves `#include` directives and minifies glsl code using [@plutotcool/glsl-bundler](https://github.com/plutotcool/glsl-bundler/tree/main/packages/glsl-bundler).

[Live demo](https://glsl-bundler.vercel.app)

## Install

```bash
yarn add @plutotcool/rollup-plugin-glsl --dev
```

```javascript
// rollup.config.js

import { glsl } from '@plutotcool/rollup-plugin-glsl'

export default {
  plugins: [
    glsl({ /* options */ })
  ]
}
```

## Options

```typescript
interface GLSLParameters {
  /**
   * Patterns of files that must be transformed by the plugin.
   * 
   * Default: /\.(?:glsl|frag|vert)$/
   */
  include?: (string | RegExp)[] | string | RegExp | null

  /**
   * Patterns of files that must not be transformed by the plugin.
   * 
   * Default: null
   */
  exclude?: (string | RegExp)[] | string | RegExp | null

  /**
   * Alternative custom filter function that determines if a file should be
   * transformed by the plugin. If specified, the include and exclude parameters
   * are ignored.
   * 
   * Default: filter function created from include and exclude parameters
   */
  filter?: (id: string) => boolean
  
  /**
   * Enable #include directives
   *
   * Default: true
   */
  loader?: boolean

  /**
   * Enable minifier or specify custom minify parameters
   *
   * Default: true
   */
  minifier?: boolean | {
    renameFunctions?: boolean
    renameVariables?: boolean
    renameDefines?: boolean
    renameStructs?: boolean
    trimComments?: boolean
    trimSpaces?: boolean
    trimZeros?: boolean
  }

  /**
   * Additional transform functions to apply to glsl code
   */
  transforms?: ((source: string) => Promise<string> | string)[]
}
```

## Usage

Get more informations from [@plutotcool/glsl-bundler](https://github.com/plutotcool/glsl-bundler/tree/main/packages/glsl-bundler#readme) package.
npm package: @plutotcool/typescript-config
Description: Base typescript configuration for plutot.cool projects.
Author: Bastien Robert
Latest version: 1.0.0

# Typescript configuration

> Base typescript configuration for plutot.cool projects.

## Installation

```bash
yarn add -D @plutotcool/typescript-config
```

In tsconfig.json

```json
{
  "extends": "@plutotcool/typescript-config"
}
```
npm package: @plutoteam/sdk
Description: 🛠 An SDK for building applications on top of pluto.
Latest version: 0.0.1

# Pluto SDK

Forked from the [Uniswap SDK](https://github.com/Uniswap/uniswap-v2-sdk/commit/a88048e9c4198a5bdaea00883ca00c8c8e582605).

You can refer to the Uniswap SDK documentation [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

Move into the pluto-sdk working directory

```sh
cd pluto-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @plutoteam/uikit
Description: Set of UI components for plutoteam projects
Latest version: 0.0.8

# 🥞 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/)
npm package: @plutovr/multi-app-manager
Description: Pluto Multi App Manager
Author: Pluto VR, Inc
Latest version: 0.10.5

# Pluto Multi App Manager
> A collection of events and event handlers that allow your WebXR app to communicate with Pluto Multi App Launcher and Pluto Communications Service when running as an XRPK

## Installation

```sh
npm i pluto-mae 
```

## Running a local version of Multi App Manager 
While there are other ways of running a local version of an NPM module, such as using [NPM link](https://docs.npmjs.com/cli/v7/commands/npm-link), this is the flow that is guarenteed to work.

### Creating a local build of Multi App Manager
1. Make changes to Multi App Manager, then run `npm run archive`
    > This will build the project and create a TGZ archive file, which is what you will use to include Multi App Manager in your local project
2. Copy the path to the TGZ file that was just created (right-click on the file and select "Copy Path")

### Installing the local version of Multi App Manager in your project
1. In your own project, install the local version by running `npm i "<path-to-archive-file>"`
    > For example:
    ```sh
    npm i "C:\Users\<user>\pluto-multi-app-manager\plutovr-multi-app-manager-0.8.2.tgz"
    ```
    > If you already have a remote version of [@plutovr/multi-app-manager](https://www.npmjs.com/package/@plutovr/multi-app-manager) installed, this will replace it with the local version.

Anytime you make changes to Multi App Manager, you will have to go through these steps again (archiving and then installing). 

If you have the local version installed already, it's sufficient to run `npm update @plutovr/multi-app-manager` after archiving, as this will update to the newer archive file.

## Publishing new package and release versions
1. Checkout `main` (which should already have merged any changes for the new version)
2. Use `npm version version-number-or-semantic-level` to add a new commit and tag with the new version (e.g. `npm version v0.10.0` or `npm version patch`)
3. `npm run archive`
4. `npm publish`
5. `git push --tags`
6. Go to https://github.com/PlutoVR/pluto-multi-app-manager/tags
7. Click the tag that you just pushed
8. Click the "Create release from tag" button in the upper right
9. In the description, add relevant notes and an npm link to the just-published version (can find this at https://www.npmjs.com/package/@plutovr/multi-app-manager under the versions tab)
10. Click the "Publish release" button
npm package: @plutovr/storybook-react-intl
Description: Add react-intl support to Storybook
Author: Steven Sacks
Latest version: 1.1.2

# Storybook react-intl addon

Add react-intl support to Storybook.

Required Versions:
* storybook - `^6.4.17`
* react-intl - `^5.24.0`

This Storybook addon assumes your project is already set up with [react-intl](https://formatjs.io/docs/react-intl/), and that it is properly configured and working.

## Installation

This addon should be added as a dev dependency.

```bash
npm i -D storybook-react-intl
```

```bash
yarn add -D storybook-react-intl
```

You will need to install `react-intl` as a dependency of your project if it is not already installed.
```bash
npm i -S react-intl
```

```bash
yarn add react-intl
```

## Usage

After installing, follow these steps to enable this addon in Storybook.

### main.js
Insert this addon into your addons array:
```javascript
{
  addons: [
    // other addons...
    'storybook-react-intl',
  ]
}
```
---

### reactIntl.js
Create a file in your `.storybook` folder called `reactIntl.js` (or whatever you like). This is where you will set up your react-intl configuration.

In this file, copy and paste the below code and make whatever modifications you need.
```javascript
const locales = ['en', 'de'];

const messages = locales.reduce((acc, lang) => ({
  ...acc,
  [lang]: require(`../locale/${lang}.json`), // whatever the relative path to your messages json is
}), {});

const formats = {}; // optional, if you have any formats

export const reactIntl = {
  defaultLocale: 'en',
  locales,
  messages,
  formats,
};
```
---

### preview.js
In your `preview.js`, you need to add the `locales` and `locale` parameters, as well as the `reactIntl` that you exported from the above file.

`locales` is an object where the keys are the "ids" of the locales/languages and the values are the names you want to display in the dropdown.

`locale` is the default locale, which can be read from `reactIntl` or set manually if you choose.

```javascript
import {reactIntl} from './reactIntl.js';

export const parameters = {
  reactIntl,
  locale: reactIntl.defaultLocale,
  locales: {
    en: 'English',
    de: 'Deutsche',  
  },
};
```

You can also set locales to Storybook compatible objects as [documented in the storybook-i18n](https://github.com/stevensacks/storybook-i18n#end-users) addon (which is included as part of this addon).

```javascript
export const parameters = {
    locales: {
        en: {title: "English", left: '🇺🇸'},
        fr: {title: "Français", left: '🇫🇷'},
        ja: {title: "日本語", left: '🇯🇵'},
    },
};
```

---
Once you have finished these steps and launch storybook, you should see a globe icon in the toolbar.

Clicking this globe icon will show a dropdown with the locales you defined in `parameters`.

Switching locales will use the strings defined in your messages.