open-index/open-npm huggingface dataset:
npm package: @kotscan-web/icons
Description: Icon automation workflow with Figma
Latest version: 0.0.31

# Icon Automation Workflow Using Figma

It's a repository for [Figma Icon Automation Plugin](https://github.com/leadream/figma-icon-automation).

## Development
Create a `.env` in the root directory. Put your Figma file url and Figma token inside.

```
FIGMA_FILE_URL=https://www.figma.com/file/********************/juuust-react-icon
FIGMA_TOKEN=********************************
```

### fetch SVG file
Run `yarn fetch` to fetch SVG files from Figma file. This will pull your SVGs in `./src/svg/`.

### generate React components for icons
Run `yarn generate` to generate component files from SVG files. This will pull your component files in `./src/icons/`.

### Develop in local
Run `yarn dev` to develop the application in which you can see all icons.

### Develop in local
Run `yarn build` to build Pages.
npm package: @kotsutsumi/next-build-exclude
Description: Exclude the target at build time with Next.js
Author: Kazuhiro Kotsutsumi
Latest version: 1.0.1

# next-build-exclude

Exclude the target at build time with Next.js

When `npm run build`, move the excluded target to `.next-build-exclude` and build,
then run `npm run dev` to restore the target from `.next-build-exclude` in reverse order.

## Add package

```bash
npm install @kotsutsumi/next-build-exclude
```

## Usage

```ts
/** @type {import('next').NextConfig} */
import nextBuildExclude from '@kotsutsumi/next-build-exclude'
const nextConfig = {
    buildExclude: {
        // evacuationDir: '.next-build-exclude' // optional

        // exclude target directories or files
        exclude: ['src/app/exclude-page']
    }
}

export default nextBuildExclude(nextConfig)

```
npm package: @kottur/cherry
Description: App for composing web components
Latest version: 0.1.0

Cherry
-------

**Build status**

[ ![Codeship Status for K0TT/Cherry](https://app.codeship.com/projects/debf6b80-0678-0135-b2f0-66143766ee12/status?branch=master)](https://app.codeship.com/projects/213800)

**Coverage**

[![codecov](https://codecov.io/gh/K0TT/Cherry/branch/master/graph/badge.svg?token=gE2mgnepjs)](https://codecov.io/gh/K0TT/Cherry)
npm package: @kotwys/formatjs-esperanto
Description: Esperanto locale for FormatJS
Author: kotwys
Latest version: 0.2.2

# Esperanto for FormatJS

This adds Esperanto locale to the FormatJS `Intl` polyfill.

The polyfill already includes Esperanto locales but they're pulled from
Unicode's CLDR repository, which isn't fully translated and therefore includes
some dummy values.

🚨 **Work in Progress**. The current translations include:

- `Intl.PluralRules`
- `Intl.RelativeTimeFormat`
- `Intl.ListFormat`

## Usage

Simply import the corresponding file from `dist` folder as follows:

```js
// For example, locale for Intl.RelativeTimeFormat
import '@kotwys/formatjs-esperanto/dist/relativetimeformat.js';
```

## Building

This project uses [yarn](https://classic.yarnpkg.com/en/) so you need to
install it first.

Then execute the following:

```bash
git clone https://github.com/kotwys/formatjs-esperanto.git
cd formatjs-esperanto
yarn
yarn build
```

The locales will appear in the `dist/` folder.
npm package: @kotwys/formatjs-locale-generator
Description: Locale generator for FormatJS
Author: kotwys
Latest version: 0.1.2

# FormatJS locale generator

This is a tool to generate locales for FormatJS like ones from `locale-data`
folder from the polyfills.

You may need a locale that is absent or inaccurate there but it can be onerous
to write them by hand. So this uses some source files to generate locales as
the original ones are created but in a more appropriate format.

⚠️ **The currently supported `Intl` APIs are**:
- `Intl.ListFormat`
- `Intl.PluralRules`
- `Intl.RelativeTimeFormat`

## Usage

```
Usage: formatjs-localegen [options] <files...>

Create locales for FormatJS

Options:
  -m <module>    Module to create locale for. If specified, there should be
                 only one input file
  -d <dir>       Output directory (default: "locale-data")
  -l <locale>    Locale code
```

The source files are YAML files like [these ones][example-dir] (Esperanto). The
`Intl` module gets inferred by the file name (see the example folder mentioned
before). You can define it yourself by `-m` option and in this case you can
provide only one file.

## Building

The project uses [Yarn].

```bash
git clone https://github.com/kotwys/formatjs-locale-generator
cd formatjs-locale-generator
yarn
```

The executable will be named `dist/index.js`.

[Yarn]: https://classic.yarnpkg.com/en/
[example-dir]: https://github.com/kotwys/formatjs-esperanto/tree/master/data
npm package: @kougen/gdrive-sync
Description: A robust tool to sync file(s) and folder(s) to google drive.
Author: Joshua Hegedus
Latest version: 1.0.0

# Google Drive Sync Client

This is a simple Google Drive sync client that uses the Google Drive API to sync files between a local directory and a Google Drive application folder.

## Future plans

- [ ] Add support for multiple Google Drive accounts
- [ ] Add support to switch between application (unaccessible) and normal (accessible) folders
npm package: @kouhin/caniuse-support
Description: Query the caniuse offline database for feature support.
Author: Chi Vinh Le and contributors
Latest version: 1.4.0

# caniuse-support

[![Build Status](https://travis-ci.org/cssinjs/caniuse-support.svg?branch=master)](https://travis-ci.org/cssinjs/caniuse-support)
[![Coverage Status](https://coveralls.io/repos/github/cssinjs/caniuse-support/badge.svg?branch=master)](https://coveralls.io/github/cssinjs/caniuse-support?branch=master) [![Greenkeeper badge](https://badges.greenkeeper.io/cssinjs/caniuse-support.svg)](https://greenkeeper.io/)

Query the [caniuse offline database](https://github.com/Fyrd/caniuse) for feature support.

Includes browser detection using [bowser](https://github.com/ded/bowser).

## Usage

```javascript
import { getSupport, detectBrowser, getVersionIndex } from "caniuse-support";

// Get feature support of specific browser.
getSupport("flexbox", { id: "chrome", version: "6.0" }); // { level: "partial", needPrefix: true, notes: [1] }

// Get feature support of specific browser using an user agent string.
const userAgent = "Mozilla/5.0 (Mobile; rv:26.0) Gecko/26.0 Firefox/26.0";
getSupport("transforms2d", detectBrowser(userAgent)); // { level: "full", needPrefix: false, notes: [] }

// Get matching caniuse version index.
getVersionIndex(detectBrowser(userAgent)); // "26"
```

For a list of queryable features see [here](https://github.com/Fyrd/caniuse/tree/master/features-json).

## Playground

Checkout this [code pen](http://codepen.io/wikiwi/pen/QGpgKp?editors=0012).
npm package: @kouhin/history
Description: Manage browser history with JavaScript
Author: Michael Jackson
Latest version: 3.4.2

# history [![Travis][build-badge]][build] [![npm package][npm-badge]][npm]

[build-badge]: https://img.shields.io/travis/ReactTraining/history/master.svg?style=flat-square
[build]: https://travis-ci.org/ReactTraining/history

[npm-badge]: https://img.shields.io/npm/v/history.svg?style=flat-square
[npm]: https://www.npmjs.org/package/history

[`history`](https://www.npmjs.com/package/history) is a JavaScript library that lets you easily manage session history anywhere JavaScript runs. `history` abstracts away the differences in various environments and provides a minimal API that lets you manage the history stack, navigate, confirm navigation, and persist state between sessions.

## Docs & Help

- [Guides and API Docs](/docs#readme)
- [Changelog](/CHANGES.md)

## Installation

Using [npm](https://www.npmjs.com/):

    $ npm install --save history

Then with a module bundler like [webpack](https://webpack.github.io/), use as you would anything else:

```js
// using an ES6 transpiler, like babel
import { createHistory } from 'history'

// not using an ES6 transpiler
var createHistory = require('history').createHistory
```

The UMD build is also available on [unpkg](https://unpkg.com):

```html
<script src="https://unpkg.com/history/umd/history.min.js"></script>
```

You can find the library on `window.History`.

## Basic Usage

A "history" encapsulates navigation between different screens in your app, and notifies listeners when the current screen changes.

```js
import { createHistory } from 'history'

const history = createHistory()

// Get the current location
const location = history.getCurrentLocation()

// Listen for changes to the current location
const unlisten = history.listen(location => {
  console.log(location.pathname)
})

// Push a new entry onto the history stack
history.push({
  pathname: '/the/path',
  search: '?a=query',

  // Extra location-specific state may be kept in session
  // storage instead of in the URL query string!
  state: { the: 'state' }
})

// When you're finished, stop the listener
unlisten()
```

You can find many more examples [in the documentation](https://github.com/ReactTraining/history/tree/master/docs)!

## Thanks

A big thank-you to [Dan Shaw](https://www.npmjs.com/~dshaw) for letting us use the `history` npm package name! Thanks Dan!

Also, thanks to [BrowserStack](https://www.browserstack.com/) for providing the infrastructure that allows us to run our build in real browsers.
npm package: @kouhin/router
Description: Next generation Routing for React.
Author: Ryan Florence
Latest version: 1.2.1

<p align="center">
  <a href="https://reach.tech/router/">
    <img alt="Reach Router" src="./logo-horizontal.png" width="400">
  </a>
</p>

<p align="center">
  Next Generation Routing for <a href="https://facebook.github.io/react">React</a>
</p>

<p align="center">
  <a href="https://www.npmjs.com/package/@reach/router"><img src="https://img.shields.io/npm/v/@reach/router.svg?style=flat-square"></a>
  <a href="https://www.npmjs.com/package/@reach/router"><img src="https://img.shields.io/npm/dm/@reach/router.svg?style=flat-square"></a>
  <a href="https://travis-ci.org/reach/router"><img src="https://img.shields.io/travis/reach/router/master.svg?style=flat-square"></a>
</p>

## Documentation

[Documentation Site](https://reach.tech/router)

You can also find the docs in the [website directory](./website/src/markdown).

## Community

[Join us on Spectrum](https://spectrum.chat/reach)

## Legal

MIT License
Copyright (c) 2018-present, Ryan Florence
npm package: @koujiman/nestjs-s3
Description: Nest - modern, fast, powerful node.js web framework (@s3)
Author: Trung Nguyen Nguyen
Latest version: 0.2.0

<p align="center">
  <a href="http://nestjs.com/" target="blank"><img src="https://nestjs.com/img/logo-small.svg" width="200" alt="Nest Logo" /></a>
</p>

[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456
[circleci-url]: https://circleci.com/gh/nestjs/nest

  <p align="center">A progressive <a href="http://nodejs.org" target="_blank">Node.js</a> framework for building efficient and scalable server-side applications.</p>
    <p align="center">
<a href="https://www.npmjs.com/~nestjscore" target="_blank"><img src="https://img.shields.io/npm/v/@nestjs/core.svg" alt="NPM Version" /></a>
<a href="https://www.npmjs.com/~nestjscore" target="_blank"><img src="https://img.shields.io/npm/l/@nestjs/core.svg" alt="Package License" /></a>
<a href="https://www.npmjs.com/~nestjscore" target="_blank"><img src="https://img.shields.io/npm/dm/@nestjs/common.svg" alt="NPM Downloads" /></a>
<a href="https://circleci.com/gh/nestjs/nest" target="_blank"><img src="https://img.shields.io/circleci/build/github/nestjs/nest/master" alt="CircleCI" /></a>
<a href="https://coveralls.io/github/nestjs/nest?branch=master" target="_blank"><img src="https://coveralls.io/repos/github/nestjs/nest/badge.svg?branch=master#9" alt="Coverage" /></a>
<a href="https://discord.gg/G7Qnnhy" target="_blank"><img src="https://img.shields.io/badge/discord-online-brightgreen.svg" alt="Discord"/></a>
<a href="https://opencollective.com/nest#backer" target="_blank"><img src="https://opencollective.com/nest/backers/badge.svg" alt="Backers on Open Collective" /></a>
<a href="https://opencollective.com/nest#sponsor" target="_blank"><img src="https://opencollective.com/nest/sponsors/badge.svg" alt="Sponsors on Open Collective" /></a>
  <a href="https://paypal.me/kamilmysliwiec" target="_blank"><img src="https://img.shields.io/badge/Donate-PayPal-ff3f59.svg"/></a>
    <a href="https://opencollective.com/nest#sponsor"  target="_blank"><img src="https://img.shields.io/badge/Support%20us-Open%20Collective-41B883.svg" alt="Support us"></a>
  <a href="https://twitter.com/nestframework" target="_blank"><img src="https://img.shields.io/twitter/follow/nestframework.svg?style=social&label=Follow"></a>
</p>
  <!--[![Backers on Open Collective](https://opencollective.com/nest/backers/badge.svg)](https://opencollective.com/nest#backer)
  [![Sponsors on Open Collective](https://opencollective.com/nest/sponsors/badge.svg)](https://opencollective.com/nest#sponsor)-->

## Description

[S3](https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-s3) module for [Nest](https://github.com/nestjs/nest).

## Installation

```bash
$ npm install --save @koujiman/nestjs-s3 @aws-sdk/client-s3
```
npm package: @kouki-dan/next-page-to-firebase-rewrite-rule
Description: Convert Next.js's pages directory structure into Firebase Hosting rewrite rules.
Author: Kouki Saito
Latest version: 1.2.0

# next-page-to-firebase-rewrite-rule

# Run
```bash
npx @kouki-dan/next-page-to-firebase-rewrite-rule
```

# Run under development in this repository
```bash
node index.js --pagesPath pages-sample --firebaseJsonPath firebase-sample.json
```
npm package: @koukitsuko/html2pdf.js
Description: Client-side HTML-to-PDF rendering using pure JS
Author: Erik Koopmans
Latest version: 0.11.0

# @koukitsuko/html2pdf.js

A fork of [html2pdf.js](https://github.com/eKoopmans/html2pdf.js) with modern build tooling and improved HTML rendering.

## Changes from the original

This fork makes the following improvements to the original html2pdf.js:

1. Replaces `html2canvas` with `html2canvas-pro` for improved HTML rendering
2. Uses modern build tooling to provide ESM, CommonJS, and UMD builds
3. Simplified package structure for easier use in modern JavaScript environments

## Installation

```bash
# Using npm
npm install @koukitsuko/html2pdf.js

# Using pnpm
pnpm add @koukitsuko/html2pdf.js
```

## Usage Examples

### ESM Import (Recommended)

```js
import html2pdf from '@koukitsuko/html2pdf.js';

// Generate PDF from element
const element = document.getElementById('element-to-print');
html2pdf().from(element).save('my-pdf.pdf');
```

### CommonJS

```js
const html2pdf = require('@koukitsuko/html2pdf.js');

// Generate PDF from element
const element = document.getElementById('element-to-print');
html2pdf().from(element).save('my-pdf.pdf');
```

## Documentation

For detailed API documentation, options, and advanced usage, please refer to the [original html2pdf.js documentation](https://github.com/eKoopmans/html2pdf.js#usage).

## Development

### Build Commands

```bash
# Install dependencies
pnpm install

# Build development version
pnpm run dev

# Build production version
pnpm run build
```

### Building and Contributing

1. Clone the repository
2. Install dependencies with `pnpm install`
3. Make changes to files in the `src` directory
4. Build with `pnpm run build`
5. Test your changes
6. Submit a pull request

## Credits

This project is a fork of [html2pdf.js](https://github.com/eKoopmans/html2pdf.js) by [Erik Koopmans](https://github.com/eKoopmans).

## License

[The MIT License](http://opensource.org/licenses/MIT)

Copyright (c) 2017-2019 Erik Koopmans <[http://www.erik-koopmans.com/](http://www.erik-koopmans.com/)>
npm package: @koumoul/ademe-rge
Description: Generates an historical file from data from qualification organisms
Author: Koumoul
Latest version: 0.11.10

# ADEME RGE processing script

Generates an historical file from data from qualification organisms

## Running tests

Install dependencies:

```
npm install
```

Create a `config/local-test.js` file with the same structure as `config/default.js` but with filled values.
Then run the test suite:

```
npm test
```

## Release

Processing plugins are fetched from the npm registry with a filter on keyword "data-fair-processings-plugin". So publishing a plugin is as simple as publishing the npm package:

```
npm version minor
npm publish
git push && git push --tags
```

To publish a test version, use prerelease versioning with a "test" npm tag:

```
# new prerelease
npm version preminor --preid=beta
# increment prerelease
npm version prerelease --preid=beta
npm publish --tag=test
git push && git push --tags
```