open-index/open-npm huggingface dataset:
npm package: @snowrunescape/mineflayer-utils
Description: <h1 align="center">mineflayer-utils</h1> <p align="center"><i>A lightweight package for <a href="https://github.com/PrismarineJS/mineflayer">mineflayer</a> that offers useful functions for creating bots</i></p>
Latest version: 1.0.3
Deprecated: WARNING: This project has been renamed to @snowrunescape/mineflayer-utils. Install using mineflayer-helpers instead.

<h1 align="center">mineflayer-utils</h1>
<p align="center"><i>A lightweight package for <a href="https://github.com/PrismarineJS/mineflayer">mineflayer</a> that offers useful functions for creating bots</i></p>

<p align="center">
  <img src="https://img.shields.io/npm/v/@snowrunescape/mineflayer-utils" />
  <img src="https://img.shields.io/github/repo-size/SnowRunescape/mineflayer-utils" />
  <img src="https://img.shields.io/npm/dm/@snowrunescape/mineflayer-utils" />
  <img src="https://img.shields.io/github/contributors/SnowRunescape/mineflayer-utils" />
  <img src="https://img.shields.io/github/license/SnowRunescape/mineflayer-utils" />
</p>

---

### Getting Started

This plugin is built using Node and can be [installed](https://github.com/PrismarineJS/mineflayer) using:
```bash
npm install @snowrunescape/mineflayer-utils
```

### License

This project uses the [MIT](https://github.com/SnowRunescape/mineflayer-utils/blob/master/README.md) license.

### Contributions

This project is accepting PRs and Issues. See something you think can be improved? Go for it! Any and all help is highly appreciated!

For larger changes, it is recommended to discuss these changes in the issues tab before writing any code. It's also preferred to make many smaller PRs than one large one, where applicable.
npm package: @snowshoe/stamp_listener
Description: A zero-dependency ES6 listener class for simple stamp detection.
Author: SnowShoe, Inc.
Latest version: 0.1.1

# SnowShoe Stamp Listener

A zero-dependency ES6 listener class for simple stamp detection.

## Installation

```bash
npm install @snowshoe/stamp_listener --save
```

## Usage

### Simple Stamp Detection

```js
import StampListener from '@snowshoe/stamp_listener';

const stampListener = new StampListener();

stampListener.listen((stampDataPoints, reEnableStampScreen) => {
    // "stampDataPoints" contains the array of data points,
    // it can be passed to the stamp API in this format:
    const stampApiRequestPayload = {data: stampDataPoints};

    // Renable the stamp screen when you're finished, 
    // (a good place for this is the finally() call of an HTTP client):
    reEnableStampScreen();
})
```

### Listener Configuration Options

```js
import StampListener from '@snowshoe/stamp_listener';

const stampListener = new StampListener({
    stampScreenElementId: 'stamp-screen',   // The ID of a specific element - "window" object used by default.
    preventScrolling: true,                 // Disable scrolling - useful on mobile. 
    preventZooming: true,                   // Disable zooming - useful on mobile.
});
```

### Use an HTTP Client to Authenticate Stamp Data

You can use whichever client you want, but this example uses Axios:

```js
import StampListener from '@snowshoe/stamp_listener';
import axios from 'axios';

// Setup the HTTP client with the SnowShoe API base URL and your SnoeShoe API key:
let httpClient = axios.create({
    baseURL: 'https://api.snowshoestamp.com',
    headers: {
        // You will receive a 401 response if this key isn't set...
        post: {'SnowShoe-Api-Key': 'YOUR_SNOWSHOE_API_KEY'} 
    }
});

const stampListener = new StampListener();

stampListener.listen((stampDataPoints, reEnableStampScreen) => {
    // Send the stamp data points to the API... 
    httpClient.post('/v3/stamp', {
        data: stampDataPoints,
        // If you are passing the stamp data through your server first, 
        // this is a good place to add extra data.
    })
        .then(response => {
            console.log(`Successfully verified stamp: ${response.data.stamp.serial}`);
        })
        .catch((error) => {
            const httpStatusCode = error.response?.status;
            if (httpStatusCode === 401) {
                console.log('The API key is most likely incorrect...', error.message);
            } else if (httpStatusCode === 400) {
                console.log('The stamp is most likely not registered...', error.response.data.error.message);
            } else {
                console.log('Some unlikely issue (like a network connection failure) has occurred...', error.message);
            }
        })
        .finally(() => {
            // Don't forget to make the screen stampable again...
            reEnableStampScreen();
        });
});
```
npm package: @snowstorm/core
Description: The lightning-fast and minimalist React Framework
Latest version: 0.19.0

<p align="center">
  <a href="https://github.com/explodingcamera/snowstorm">
    <img src="./logo.svg" height="128">
    <h1 align="center">Snowstorm.js</h1>
  </a>
</p>

# The lightning-fast and minimalist React Framework

## Warning

Important: Snowstorm is in beta. It's already being used in production, however there might be rough edges and unexpected issues.

## What?

Snowstorm is a framework (or Static-Site-Generator) for react, which handles the heavy lifting involved with shipping a react project so you can focus on creating awesome things!

## Why?

- **Develop faster**: with a dev server that starts up in less then 30ms and build thousands of pages in seconds
- **Open**: not VC-backed, no upsell, no cloud-platform exclusive features
- **Unbloated**: only includes features which you actually use
- **Multi-Site support**: develop for multiple domains at the same time
- **Great UX**: file system based routing, react suspense support, great TypeScript support, CSS-Modules

## How?

Getting started with snowstorm takes less than a minute and doesn't any require confusing `init` commands:

```bash
# install the required dependencies
$ npm install -S @snowstorm/core @snowstorm/cli react@18 react-dom@18 typescript

# (optional) enable scss support:
$ npm install -S sass

# this folder will contain all webpages
$ mkdir pages
$ echo 'export const Index = () => <h1>Hello World</h1>' > pages/index.tsx

# (optional) enable typescript support
$ echo '{ "extends": "@snowstorm/core/tsconfig.base.json" }' > tsconfig.json

# start the development server
$ npx snowstorm dev
```

<pre><code><b>INFO</b> starting snowstorm v0.10.0 (development mode)
<b>INFO</b> listening on <u>http://localhost:2020/</u>
<b>INFO</b> started in 19ms</code></pre>

### Visit [snowstorm.js.org/docs](https://snowstorm.js.org/docs/getting-started) for the full documentation

<br/>

> License: [MIT](LICENSE.md)
npm package: @snowstorm/router
Description: Based in part on https://github.com/molefrog/wouter (Licensed under the ISC).
Latest version: 0.19.0

# @snowstorm/router

Based in part on https://github.com/molefrog/wouter (Licensed under the ISC).

Differences to wouter:

- ported to typescript
- removed components not used by snowstorm

```ts
import { Link } from "@snowstorm/router";
```

## TODO

port rest of the tests: https://github.com/molefrog/wouter/tree/master/test
npm package: @snowsvex/snowsvex
Description: The Svexiest static site generator in town
Author: Conor Sinclair
Latest version: 0.2.4

# Snowsvex

> Build svex-y static sites with svelte

Compile Svelte and svelte-scented markdown _(aka MDSvex)_ into static pages using Snowpack.

## Installation

📦 Install with your favourite package manager

```sh
npm i -D @snowsvex/snowsvex
yarn add -D @snowsvex/snowsvex
pnpm i -D @snowsvex/snowsvex
```

❄️ And then add the scripts to your `package.json`

```json
  "scripts": {
    "start": "snowsvex dev",
    "build": "snowsvex build",
  },
```

## Configuration

By default any `.svelte` or `.svx` files in your `src/pages` directory will generate html files.

> Specific config is broken currently. Watch this space!

<strike>You can add more directories to watch by adding them to a `snowsvex.config.js` file.</strike>

> Not currently... Just put it in the snowpack config for now

```js
module.exports = {
  pagesDirs: ['pages', 'articles', 'foo', 'superfoo']
}
```

`pagesDirs` expects a `string[]` of directory names to look in for files to generate static pages from.

Snowsvex is built on top of the _great and mighty_ Snowpack! You add a `snowpack.config.js` to extend the configuration Snowsvex uses.

## Output Files

The `pages` directory is special and if present will generate html files at the root of your build directory. This is so no special routing needs to take place when your awesome new static site hits the server. All other directories will be placed in `[DIR]/[FILE_NAME]` in your build directory.

### Dev Mode

Working with multiple output files in Snowpack causes some interesting path issues when in dev mode. We circumvent this by adding a very _very_ basic router to your source code. So when you slam down that `yarn dev` command, don't freak out when the `src/dev-runtime.js` file appears. This file is generated using your `pagesDirs` configuration.

Need a new directory to watch and generate pages from? Add it to your `snowsvex.config.js` > `pagesDirs` config and rerun `yarn dev`

## TODO

- [ ] Setup Github action to autodeploy to npm
- [ ] gif showing build command
- [ ] fix config file
- [ ] get dev working tightly
npm package: @snowsvex/snowsvex-plugin
Description: > Snowpack plugin for building svex-y static sites with svelte
Author: Conor Sinclair
Latest version: 0.1.7

# Snowsvex Plugin

> Snowpack plugin for building svex-y static sites with svelte

Compile Svelte and svelte-scented markdown _(aka MDSvex)_ into static pages using Snowpack.

## Installation

📦 Install with your favourite package manager

```sh
npm i -D @snowsvex/snowsvex-plugin
yarn add -D @snowsvex/snowsvex-plugin
pnpm i -D @snowsvex/snowsvex-plugin
```

❄️ And then add it to your `snowpack.config.js` plugins

```json
  "plugins": [
    ...
    '@snowsvex/snowsvex-plugin',
  ],
  ...
```

## Configuration

By default any `.svelte` or `.svx` files in your `src/pages` directory will generate html files.

You can change this by adding to the plugin config in `snowpack.config.js`

```json
  "plugins": [
    ...
    ['@snowsvex/snowsvex-plugin', {
      pagesDirs: ['pages', 'articles', 'foo', 'superfoo']
    }],
  ],
  ...
```

`pagesDirs` expects a `string[]` of directory names to look in for files to generate static pages from.

## Output Files

Issues currently exist with file names keeping their `.svelte` / `.svx` extensions

This can be circumvented by using the `@snowsvex/snowsvex-builder` package to build or writing your own custom node script to move/rename the files as you wish!

Using `@snowsvex/snowsvex`, add the build script to your `package.json` scripts.

```json
  "scripts": {
    "build": "snowsvex build",
    ...
  },
```

The `pages` directory is special and if present will generate html files at the root of your build directory. This is so no special routing needs to take place when your awesome new static site hits the server. All other directories will be placed in `[DIR]/[FILE_NAME]` in your build directory.

### Dev Mode

Issues exist with snowpack not understanding multiple output files when in dev mode. This can be avoided

## TODO

- [ ] Setup Github action to autodeploy to npm
- [ ] gif showing output directory structure
npm package: @snowswap/sdk
Description: 🛠 An SDK for building applications on top of Snowswap.
Latest version: 2.5.0

# Snowswap 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:

```sh
git clone https://github.com/SnowSwapOrg/snowswap-sdk.git
```

Move into the pancakeswap-sdk working directory

```sh
cd pancakeswap-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: @snowswap/uikit
Description: Set of UI components for snowswap projects
Latest version: 0.60.3

# 🥞 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/)