open-index/open-npm huggingface dataset:
npm package: @flaper/angular
Description: Angular2 Flaper lib: services, models, etc
Latest version: 0.8.14

# Flaper Angular Lib [![npm version](https://badge.fury.io/js/%40flaper%2Fangular.svg)](https://badge.fury.io/js/%40flaper%2Fangular)
Flaper services, models, pipes, etc


## Development 
### Для использования новых версий в локальных flaper.web и flaper.admin
```
npm install typescript@2.0 -g
```
После каждого изменения:

`npm run sync`
(Ожидает, что все проекты лежат в одной общей папке (*common/web*, *common/angular*, *common/admin*)

## Usage 

## Install 
`npm install @flaper/angular`

## Example
```typescript
import {UserService, StoryService} from '@flaper/angular';
```

## Publish
```
npm patch version
npm publish
```
npm package: @flaper/consts
Description: consts for flaper
Latest version: 0.2.6

# Константы для flaper.org
[![Build Status](https://travis-ci.org/flaper/consts.svg?branch=master)](https://travis-ci.org/flaper/consts) [![npm version](https://badge.fury.io/js/%40flaper%2Fconsts.svg)](https://badge.fury.io/js/%40flaper%2Fconsts)

Установка:

`install @flaper/consts --save`
### Environment
От ENV зависят ссылки для картинок. 
По умолчанию ENV=production.

Чтобы сменить:
```js
import {ConstsApp} from '@flaper/consts';
ConstsApp.setEnv('development');
```
npm package: @flapnote/biz-component
Description: # 飞记业务组件库
Author: tangjiachen
Latest version: 1.0.24

# flapnote-biz-component

# 飞记业务组件库

## 1. 加载方式：按需，全局，外部
## 2. 代码方式：源码，es，bundle
## 3. 发布方式：npm包，cdn上传

# 打包发布

## yarn build
## yarn commit
## npm version patch
## npm publish
## git push


# 打包上传
## yarn build
## 将dist目录下的文件上传至 *-flapnote-client/lib/flapnote-biz-component下
npm package: @flapper/gatsby-source-flapper
Description: A flexible alternative to GraphQL for Gatsby
Author: Dustin Lacewell
Latest version: 0.1.8

# Flapper for Gatsby

A flexible alternative to GraphQL for Gatsby.

Check out our [documentation](http://flapper.ldlework.com/).

```javascript
const pipelines = {
    page: [
        SourceFilesRecursively("pages/", [".tsx"]),
        SetUrl("{{relativePath}}"),
        RenderTemplate("{{path}}")
    ],
    post: [
        SourceMatchedFiles("posts/{{category_name}}/{{name}}.mdx"),
        SetUrl("posts/{{name}}"),
        BindMdx("{{path}}"),
        RenderTemplate("src/templates/MDXPost.tsx")
    ]
}
```

## GraphQL is a sledgehammer

Gatsby's GraphQL is crazy powerful. You can do anything with it!

But it also takes a lot of effort to get your data into GraphQL, just to get it out again.

If you have your data on hand, Flapper just lets you use it.

## Invent your own metaphors

Most SSGs try to lock you into "pages" and "posts" with "tags" and "categories".

Flapper lets you imagine metaphors useful for your site.

Want a "project" metaphor? Or a "article series" metaphor? Just make it.

## Dead simple site generation

Use simple functions to build your data model using regular javascript data.

Map your data to URLs and Templates, get static HTML.

Templates are simply components with the full power of React.
npm package: @flaque/google-button
Description: A forked version of the login-with-google button
Author: flaque
Latest version: 1.0.5

# google-button [![License](https://img.shields.io/npm/l/google-button.svg)](https://github.com/flaque/google-button/blob/master/package.json)

## Install

```
yarn add
```

## Usage

Just a login-with-google button that acts like a regular button. Just a personal typescript-y fork of [prescottprue/react-google-button](https://github.com/prescottprue/react-google-button).

```ts
import GoogleButton from "@flaque/google-button";

// ...

<GoogleButton
  label="Login with Google"
  disabled={true}
  onClick={() => {}}
  type="light"
  style={{
    background: "blue"
  }}
/>;

// Or just
<GoogleButton onClick={() => {}}>
```
npm package: @flaque/use-toggle
Description: A simple switch hook
Author: flaque
Latest version: 1.0.2

# use-toggle [![License](https://img.shields.io/npm/l/use-toggle.svg)](https://github.com/flaque/use-toggle/blob/master/package.json)

Like `useState`, but for toggling something on/off.

## Install

```
yarn add @flaque/use-toggle
```

## Usage

```ts
import useToggle from '@flaque/use-toggle'

function MySwitch() {
    const [isOn, toggleIsOn] = useToggle(true)

    return (<>
        <p>{`I am ${isOn ? "on" : "off"}`}</p>

        <button onClick={toggleIsOn}>
    </>)
}
```
npm package: @flare-swap/core
Description: Core smart contracts of FlareSwap
Author: FlareSwap
Latest version: 1.0.0

# FlareSwap Core

In-depth documentation on FlareSwap is available at [docs.flareswap.finance](https://docs.flareswap.finance/).

# Local Development

The following assumes the use of `node@>=10`.

## Install Dependencies

`npm i`

## Compile Contracts

`npx hardhat compile`

## Run Tests

`npx hardhat test`
npm package: @flare-swap/periphery
Description: Peripheral smart contracts for interacting with FlareSwap
Author: FlareSwap
Latest version: 1.0.0

# FlareSwap Router

## Local Development

The following assumes the use of `node@>=10`.

## Install Dependencies

`npm i`

## Compile Contracts

`npx hardhat compile`

## Run Tests

`npx hardhat test`
npm package: @flareapp/flare-client
Description: Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.
Author: adriaan@spatie.be
Latest version: 3.0.5

# The JavaScript client for Flare to catch frontend errors

Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

React plugin: https://www.npmjs.com/package/@flareapp/flare-react

Vue plugin: https://www.npmjs.com/package/@flareapp/flare-vue

Webpack plugin: https://www.npmjs.com/package/@flareapp/flare-webpack-plugin-sourcemap
npm package: @flareapp/flare-react
Description: Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.
Author: adriaan@spatie.be
Latest version: 3.0.5

# The JavaScript client for Flare to catch frontend errors

Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

Flare client: https://www.npmjs.com/package/@flareapp/flare-client
npm package: @flareapp/flare-vue
Description: Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.
Author: adriaan@spatie.be
Latest version: 3.0.5

# The JavaScript client for Flare to catch frontend errors

Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

Flare client: https://www.npmjs.com/package/@flareapp/flare-client
npm package: @flareapp/flare-webpack-plugin-sourcemap
Description: The Flare Webpack plugin helps you send sourcemaps of your compiled JavaScript code to Flare. This way, reports sent using the `@flareapp/flare-client` will be formatted correctly.
Latest version: 1.3.0

# Webpack plugin for sending sourcemaps to Flare

The Flare Webpack plugin helps you send sourcemaps of your compiled JavaScript code to Flare. This way, reports sent using the `@flareapp/flare-client` will be formatted correctly.

Check JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

Flare client: https://www.npmjs.com/package/@flareapp/flare-client
npm package: @flareapp/ignition-ui
Description: UI components for Laravel's Ignition error page
Latest version: 4.11.0

# Ignition UI

UI components used in Laravel's default Ignition error page.

See [spatie/ignition](https://github.com/spatie/ignition) for more information.

## Tagging a new release

- `yarn dev`
- make required changes
- update CHANGELOG.md
- `yarn publish`
- enter the new version you decided on in CHANGELOG.md
- update `@flareapp/ignition-ui` dependency in `spatie/ignition`
- in `spatie/ignition` run `yarn bundle` (or wait for the GH action)
- publish new version of `spatie/ignition` to packagist
npm package: @flareapp/js
Description: JavaScript client for flareapp.io
Author: adriaan@spatie.be
Latest version: 1.1.0

# The JavaScript client for Flare to catch frontend errors

Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

React plugin: https://www.npmjs.com/package/@flareapp/react

Vue plugin: https://www.npmjs.com/package/@flareapp/vue

Webpack plugin: https://www.npmjs.com/package/@flareapp/flare-webpack-plugin-sourcemap
npm package: @flareapp/react
Description: React client for flareapp.io
Author: adriaan@spatie.be
Latest version: 1.0.1

# The JavaScript client for Flare to catch frontend errors

Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

Flare client: https://www.npmjs.com/package/@flareapp/js
npm package: @flareapp/vite
Description: Vite plugin for flareapp.io
Author: adriaan@spatie.be
Latest version: 1.1.0

# Vite plugin for sending sourcemaps to Flare

The Flare Vite plugin helps you send sourcemaps of your compiled JavaScript code to Flare. This way, reports sent using the `@flareapp/js` will be formatted correctly.

Additionally, it automatically passes the Flare API key to `@flareapp/js`. This way, `flare.light()` works without any additional configuration.

Check the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

## Installation

Install the plugin using NPM or Yarn:

```bash
yarn add @flareapp/vite
# or
npm install @flareapp/vite
```
Next, add the plugin to your `vite.config.js` file:

```js
import { defineConfig } from 'vite';
import flareSourcemapUploader from '@flareapp/vite';

export default defineConfig({
    plugins: [
        flareSourcemapUploader({
            key: 'YOUR API KEY HERE'
        }),
    ],
});
```

Run the `vite build` command to make sure the sourcemaps are generated. You should see the following lines in the output:

```bash
@flareapp/flare-vite-plugin-sourcemaps: Uploading 12 sourcemap files to Flare.
@flareapp/flare-vite-plugin-sourcemaps: Successfully uploaded sourcemaps to Flare.
```

## Configuration

- `key: string` **(required)**: the Flare API key 
- `base: string`: the base path of built output (defaults to Vite's base path)
- `runInDevelopment: boolean`: whether to upload sourcemaps when `NODE_ENV=development` or when running the dev server (defaults to `false`)
- `version: string`: the sourcemap version (defaults to a fresh `uuid` per build)
- `removeSourcemaps: boolean`: whether to remove the sourcemaps after uploading them (defaults to `false`). Comes in handy when you want to upload sourcemaps to Flare but don't want them published in your build.

## development

Publish a new release: 

```bash
npm version patch
npm publish
```

Tag the release:

<pre>
git tag <var>VERSION</var>
git push origin <var>VERSION</var>
</pre>

Replace <var>VERSION</var> with `v` + the version from `package.json` — for example, `v1.0.2`
npm package: @flareapp/vite-plugin-sourcemap-uploader
Description: The Flare Vite plugin helps you send sourcemaps of your compiled JavaScript code to Flare. This way, reports sent using the `@flareapp/flare-client` will be formatted correctly.
Latest version: 1.0.3

# Vite plugin for sending sourcemaps to Flare

The Flare Vite plugin helps you send sourcemaps of your compiled JavaScript code to Flare. This way, reports sent using the `@flareapp/flare-client` will be formatted correctly.

Additionally, it automatically passes the Flare API key to `@flareapp/flare-client`. This way, `flare.light()` works without any additional configuration.

Check the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

Looking for the Flare client? [Go to the @flareapp/flare-client repo](https://www.npmjs.com/package/@flareapp/flare-client).

## Installation

Install the plugin using NPM or Yarn:

```bash
yarn add @flareapp/vite-plugin-sourcemap-uploader
# or
npm install @flareapp/vite-plugin-sourcemap-uploader
```
Next, add the plugin to your `vite.config.js` file:

```js
import { defineConfig } from 'vite';
import flareSourcemapUploader from '@flareapp/vite-plugin-sourcemap-uploader';

export default defineConfig({
    plugins: [
        flareSourcemapUploader({
            key: 'YOUR API KEY HERE'
        }),
    ],
});
```

Run the `vite build` command to make sure the sourcemaps are generated. You should see the following lines in the output:

```bash
@flareapp/flare-vite-plugin-sourcemaps: Uploading 12 sourcemap files to Flare.
@flareapp/flare-vite-plugin-sourcemaps: Successfully uploaded sourcemaps to Flare.
```

## Configuration

- `key: string` **(required)**: the Flare API key 
- `base: string`: the base path of built output (defaults to Vite's base path)
- `runInDevelopment: boolean`: whether to upload sourcemaps when `NODE_ENV=development` or when running the dev server (defaults to `false`)
- `version: string`: the sourcemap version (defaults to a fresh `uuid` per build)
- `removeSourcemaps: boolean`: whether to remove the sourcemaps after uploading them (defaults to `false`). Comes in handy when you want to upload sourcemaps to Flare but don't want them published in your build.

## development

Publish a new release: 

```bash
npm version patch
npm publish
```

Tag the release:

<pre>
git tag <var>VERSION</var>
git push origin <var>VERSION</var>
</pre>

Replace <var>VERSION</var> with `v` + the version from `package.json` — for example, `v1.0.2`
npm package: @flareapp/vue
Description: Vue client for flareapp.io
Author: adriaan@spatie.be
Latest version: 1.0.1

# The JavaScript client for Flare to catch frontend errors

Read the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.

Flare client: https://www.npmjs.com/package/@flareapp/js