open-index/open-npm huggingface dataset:
npm package: @fujiechen/vue3-tags-input
Description: A tags input component for Vue 3 with autocompletion, custom validation, templating and much more
Author: Fujie Chen
Latest version: 1.0.2

# vue-tags-input

A tags input component for Vue 3 with autocompletion, custom validation, templating and much more

Forked from [@johmun/vue-tags-input](https://www.npmjs.com/package/@johmun/vue-tags-input), which you should use instead if your project is on Vue 2. 

[Demo & Docs](http://www.vue-tags-input.com) (for the original version)

## Features

* No dependencies
* Custom validation rules
* Hooks: Before adding, Before deleting ...
* Edit tags after creation
* Fast setup
* Works with Vuex
* Small size: 34kb minified (css included) | gzipped 9kb
* Autocompletion
* Many customization options
* Own templates
* Delete tags on backspace
* Add tags on paste
* Examples & Docs

## Install

NPM
```
npm install @fujiechen/vue3-tags-input
```

CDN
```
<script src="https://unpkg.com/@fujiechen/vue3-tags-input/dist/vue-tags-input.js"></script>
```

## Usage

```html
<template>
  <div>
    <vue-tags-input
      v-model="tag"
      :tags="tags"
      @tags-changed="newTags => tags = newTags"
    />
  </div>
</template>
```

```javascript
<script>
import VueTagsInput from "@fujiechen/vue3-tags-input";

export default {
  components: {
    VueTagsInput,
  },
  data() {
    return {
      tag: '',
      tags: [],
    };
  },
};
</script>
```

## Migration From Vue 2

This version is faithful to the original spec. The only thing you'll have to change is replacing any usages of `tags.sync` with `vmodel:tags` in the props

## License

[MIT](https://opensource.org/licenses/MIT)

Copyright (c) 2023 Fujie Chen
npm package: @fujimi/ui-core
Description: `@fujimi/ui-core` will be the basic implementation of the design system.
Author: konojunya
Latest version: 0.5.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @fujimi/ui-core

`@fujimi/ui-core` will be the basic implementation of the design system.
npm package: @fujimi/ui-icons
Description: `@fujimi/ui-icons` is a list of svg icons converted to jsx.
Author: konojunya
Latest version: 0.12.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @fujimi/ui-icons

`@fujimi/ui-icons` is a list of svg icons converted to jsx.
npm package: @fujimi/ui-next
Description: `@fujimi/ui-next` is fujimi-ui with a dependency on Next.js.
Author: konojunya
Latest version: 0.10.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @fujimi/ui-next

`@fujimi/ui-next` is fujimi-ui with a dependency on Next.js.
npm package: @fujimi/ui-react
Description: `@fujimi/ui-react` is fujimi-ui with a dependency on React.
Author: konojunya
Latest version: 0.9.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @fujimi/ui-react

`@fujimi/ui-react` is fujimi-ui with a dependency on React.
npm package: @fujio0000/muppet
Description: muppet
Author: fujioi0000
Latest version: 1.1.8

# muppet

[![npm version](https://badge.fury.io/js/%40fujio0000%2Fmuppet.svg)](https://badge.fury.io/js/%40fujio0000%2Fmuppet)

Get screenshot

# installation

```
$ npm i @fujio0000/muppet
```

# usage

```
$ muppet WIDTH PATH URL
```
npm package: @fujitsusweden/eslint-config-standard
Description: Shareable ESLint config
Author: Axel Svensson
Latest version: 0.4.0

# eslint-config-standard

## What is it

A shareable ESLint config.

## How to use it

* To install it into your project:
  * Run `npm install --save-dev eslint @fujitsusweden/eslint-config-standard`
  * Run `npx eslint --init`
    * On the question `How would you like to use ESLint?`, answer `To check syntax and find problems`.
    * Answer other questions as appropriate.
  * In your generated `.eslintrc.js` file, change `extends: "eslint:recommended"` to `extends: "@fujitsusweden/standard"`
* To check for problems, run `npx eslint .` (and if you use Vue, add ` --ext .js,.vue`.)
* To check for problems and also let ESLint fix everything it can, run `npx eslint . --fix` (and if you use Vue, add ` --ext .js,.vue`.)

## Development

Run `./script` without arguments for help
npm package: @fujix/cli
Description: [👾 Usage examples](https://github.com/fujix-io/fujix-examples)
Author: Alexey Maligon
Latest version: 0.1.54

# FujiX CLI

[👾 Usage examples](https://github.com/fujix-io/fujix-examples)

## How to use

### Install CLI
```
npm install -g @fujix/cli
```

## Commands:

### `generate`
Used for generating bindings code by credentials

### flags:
  - `-o/--out` - used for specifying generated folder name
  - `-u/--url` - used for providing endpoint url
  - `-t/--token` - used for providing endpoint token 
  - `-v/--version` - used for displaying package version
  - `-h/--help` - used for displaying list of commands
  - `--raw` - used for CI/CD command lines. Diplay output with native output-streams. Can be used only with `--token` and `--url` flags
  - `--silent` - turn off all cli-outputs. Can be used only with `--token` and `--url` flags
npm package: @fujiy/wccp
Description: WASA Common Command&Telemetry Protocol
Author: Yuki Fujihara
Latest version: 0.1.0

# WASA Common Command&Telemetry Protocol

コマンドおよびテレメトリに用いる，統一されたシリアライズフォーマット．


# 目的
コマンドやテレメトリのフォーマットを規定する．
バイナリ形式でデータを表現することで，テキストフォーマットと比べてデータサイズを削減する．

パケットの内容についてはスキーマレス，すなわちパケットの定義を知らなくてもある程度はデコード可能とする．これにより各所でスキーマ定義を共有する手間を削減し，迅速な開発を可能にする．

CANやUARTを用いた有線通信，LoRa等による無線通信，SDカードへの記録等に用いる．
バスによって接続された同一システム内におけるのローカルな情報のやり取りに加えて，
無線等により連携した複数の独立したシステム間の通信にも用いる．


# パケットフォーマット

パケットを情報の単位とする．パケットはヘッダ部と，0以上32未満のエントリからなる．
エントリの順序は保持されなければならない．

| 項目   | サイズ |
| ----   | ------ |
| ヘッダ | 4 byte |
| エントリ*N | 1N ~ 5N byte |
| CRC8 | 1 byte |

## ヘッダ

| 項目                 | サイズ | 備考 |
| ----                 | ------ | ----- |
| 種別             | 1 bit  | `0`：コマンド，`1`：テレメトリ |
| パケット種別ID    | 7 bit  | `0x7F`以外の値．基本的にASCIIコードにおける英数字 |
| 送信元システムID | 3 bit   | `0`: ローカル                     |
| 送信元ノードID   | 5 bit  | バス内におけるノードID（後述） |
| 送信先システムID | 3 bit   | `0`：リモートに送信しない，`0b111`：ブロードキャスト |
| エントリ数       | 5 bit  | エントリの数．パケットのバイト数ではない |
| シーケンス番号   | 8 bit | 送信元ノード毎にインクリメントされる値 |

## エントリ

エントリはデータの種類を表すタイプと，データ自体であるペイロード部からなる．
一つのパケットの中に同じタイプのエントリが含まれていてもよく，
その場合は配列のように解釈すると便利である．

| 項目       | サイズ |
| ----       | ------ |
| タイプ     | 1 byte |
| ペイロード | 0~4 byte |

### タイプ

ユーザーが指定するタイプは`64~127`の範囲の値，ASCIIコードで`A~Z, a~z`を基本とし，
その下位6bitを用いる．上位2bitはペイロードのサイズ（バイト数）を表す．

上位2bitとペイロードのサイズの対応は

- 11: 4 byte
- 10: 2 byte
- 01: 1 byte
- 00: 0 byte

である．

### ペイロード

ペイロードは0~4byteのリトルエンディアンのバイト列である．
バイト列をどのデータ型として解釈するかは自由である．
言い換えると，パケットのデータのみを見てデータ型を判別することはできず，
別途スキーマを知っている必要がある．

データ型が何であるかにかかわらず，ペイロードの上位2あるいは3あるいは4 byteが`0x00`である場合には，
そのバイトを省略してサイズを決定する．

### データ型

標準でサポートする，ペイロードのデータ型を解釈する方法を以下に示す．

| データ型 | サイズ (byte) |
| ----     |        ------ |
| bytes    |             4 |
| uint32   |             4 |
| uint16   |             2 |
| uint8    |             1 |
| int32    |             4 |
| int16    |             2 |
| int8     |             1 |
| float32  |             4 |
| float16  |             2 |
| void     |             0 |

符号付き整数は２の補数，浮動小数点数はIEEE 754で定められた表現である．
float16は半精度浮動小数点数（10進で約3桁の精度）である．


# バス

上述のパケットプロトコルを用いたバスについて規定する．

## 共通規定

### ノードID

### ハートビート

## CAN バス

### 拡張ID (29 bit)

| 項目             | サイズ |
| ----            | ------ |
| 種別             | 1 bit  |
| パケット種別ID    | 7 bit  |
| 送信元システムID | 3 bit   |
| 送信元ノードID   | 5 bit  |
| IDフィールド     | 8 bit  |
| フレーム番号     | 5 bit  |


## UART バス

モジュール間をUARTでデイジーチェーン接続する．
モジュールあたり2つのUARTを使用する．
両端同士を接続してリング状にすることで信頼性を向上させる．

### Node ID

### フォーマット

| 項目       | サイズ |
| ----       | ------ |
| Node ID    | 1 byte |
| シーケンス番号 | 1 byte |
| パケット | 3~ byte |


# 上位レイヤー

## 共有変数
npm package: @fujocoded/astro-dev-only
Description: An Astro integration for development-only pages
Author: FujoCoded LLC
Latest version: 0.0.4

# @fujocoded/astro-dev-only

An Astro integration to remove files from your final static production build.
Useful for drafts or other dev-only pages.

> [!WARNING]
> This is an experimental library with basic functionality. Expect
> rough edges.

## Installation

```sh
npm install @fujocoded/astro-dev-only
```

## Usage

Add the integration to your `astro.config.mjs` file (or similar) and list the
routes you want to remove from the final build via `routePatterns`. Accepts both
strings (full match, with optional `index.html`) and RegExp.

```ts
// astro.config.mjs
import { defineConfig } from "astro/config";
import devOnlyRoutes from "@fujocoded/astro-dev-only";

export default defineConfig({
  integrations: [
    devOnlyRoutes({
      routePatterns: [
        // For static routes, this will remove the page generated from either
        // - src/pages/your-eyes-only.astro
        // - src/pages/your-eyes-only.html
        "/your-eyes-only",
        // For static routes, this will remove any route generated from within src/pages/drafts
        /^\/drafts\//,
        // Dynamic routes are also supported, in both modes
        // NOTE: it's currently not possible to remove only SOME generated paths from a route. PR welcome!
        "/dynamic/[...pages]",
      ],
    }),
  ],
});
```

The integration works by literally deleting files from the resulting builds.
It's not pretty, but it works. See notes and limitations.

> [!IMPORTANT]
> Want to be safe? This integration supports a `dryRun` flag. Set
> it and the integration will just print the path of the files to delete! The
> actual files will remain!
>
> ```ts
> devOnlyRoutes({
>   dryRun: true,
>   // ...
> });
> ```

## Notes and limitations

Given the crude implementation, a few words of caution:

- This integration only removes the generated page files. It does not
  automatically remove references to those pages (e.g., sitemap entries, nav
  links, RSS).
- Assets are also not removed
- All dev-only pages are still built for production, which means any slowness
  caused by them won't be helped by this plugin
npm package: @fujocoded/astro-rehype-html-headings
Description: Adds a list of headings to Astro's frontmatter that include rendered HTML code
Author: FujoCoded LLC
Latest version: 0.0.2

# @fujocoded/astro-rehype-html-headings

Collects headings from a MD(X) file in an Astro environment, similar to how
Astro itself does with its [getHeadings() function](https://docs.astro.build/en/guides/markdown-content/#heading-ids-and-plugins). The headings returned by this plugin, however, also include a `html` properties
that includes the heading rendered to HTML.

> [!IMPORTANT]  
> This `rehype` plugin can only be used in Astro since it relies on the existence of the Astro frontmatter property

### Sample usage

In `astro.config.js`:

```ts
import { astroRehypeHtmlHeadings } from "@fujocoded/astro-rehype-html-headings";

export default defineConfig({
  // ...
  integrations: [
    mdx({
      rehypePlugins: [astroRehypeHtmlHeadings],
    }),
  ],
});
```

In an astro file:

```ts
const chapters = await getCollection("chapters");
chapters.map(async (a) => {
  const rendered = await a.render();
  // The logged result will look like the result of the "getHeadings" Astro function,
  // but will also contain the rendered HTML
  console.log(rendered.remarkPluginFrontmatter.headings);
});
```
npm package: @fujocoded/astro-remark-collect-components
Description: Allows adding a list of components and attributes in an MDX file to Astro's frontmatter
Author: FujoCoded LLC
Latest version: 0.0.6

# @fujocoded/astro-remark-collect-components

Collects a series of attributes from Astro components used in `.md` or `.mdx`
files and adds a list of them to the Astro `remarkFrontmatter` property for
later usage.

> [!IMPORTANT]  
> This `remark` plugin can only be used in Astro since it relies on the existence of the Astro frontmatter property

### Sample usage

In `astro.config.js`:

```ts
import { astroRemarkCollectComponents } from "@fujocoded/astro-remark-collect-components";

export default defineConfig({
  // ...
  integrations: [
    mdx({
      remarkPlugins: [
        [
          astroRemarkCollectComponents,
          {
            components: [
              {
                // Name of the component
                name: "Callout",
                // Attributes to collect
                attributes: ["title", "slug", "type"],
                // Name of property in remarkPluginFrontmatter where the list of attributes will be stored
                frontmatterName: "callouts",
              },
              {
                name: "ScenarioCallout",
                attributes: ["title", "slug"],
                frontmatterName: "scenarios",
              },
            ],
          },
        ],
      ],
    }),
  ],
});
```

In an astro file:

```ts
const chapters = await getCollection("chapters");
chapters.map(async (a) => {
  const rendered = await a.render();
  console.log(rendered.remarkPluginFrontmatter.callouts);
});
```
npm package: @fujocoded/expressive-code-caption
Description: Allow adding caption at the end of expressive code blocks.
Author: FujoCoded LLC
Latest version: 0.0.3

# @fujocoded/expressive-code-caption

Allows adding a caption for a code block that uses expressive code, delineated by `---` block fences.

Simple markdown formatting is supported within the caption.

> [!IMPORTANT]
>
> 1. The code fence must end at the last line before the code block is closed.
> 2. You should put this plugin as early as possible in the list of plugins to minimize the chance that other plugins will interfere with it and viceversa.

### Sample usage

In `astro.config.js`:

```ts
import { pluginCodeCaption } from "@fujocoded/expressive-code-caption";

export default defineConfig({
  // ...
  integrations: [
    starlight({
      expressiveCode: {
        plugins: [pluginCodeCaption()],
      },
    }),
  ],
});
```

In a markdown file:

````md
Here is a code sample:

```bash
pwd

---
After pressing enter, the `pwd` command will output the current directory
your terminal is in.
---
```
````

This will add a `figcaption` element as last child of the rendered terminal with the sentence between the `---` fences.
npm package: @fujocoded/expressive-code-output
Description: Allow adding output for expressive code blocks.
Author: FujoCoded LLC
Latest version: 0.1.0

# @fujocoded/expressive-code-output

Allows separating code in an expressive code block from its output.

When this plugin is installed adding the `withOutput` attribute to a block will enable "output mode". In this mode, actual code must be preceded by the `> ` string. The first line that does not start with `> ` is where the output will start.

### Sample usage

In `astro.config.js`:

```ts
import { pluginCodeOutput } from "@fujocoded/expressive-code-output";

export default defineConfig({
  // ...
  integrations: [
    starlight({
      expressiveCode: {
        plugins: [pluginCodeOutput()],
      },
    }),
  ],
});
```

In a markdown file:

````md
Here is a code sample:

```bash withOutput
> pwd

/usr/home/boba-tan/programming
```
````

This will create a code block with only the `pwd` command in it (without `> `) followed by another block containing the output.
npm package: @fujocoded/rehype-code-params
Description: Make params stylable in code commands
Author: FujoCoded LLC
Latest version: 0.0.5

# @fujocoded/rehype-code-params

Rehype plugin to style param vaues in inline code blocks. It does so by wrapping
any value between `[]` brackets within inline code blocks in a `<span>`.

## Sample usage

In `astro.config.js`:

```ts
import { rehypeCodeParams } from "@fujocoded/rehype-code-params";

export default defineConfig({
  // ...
  integrations: [
    mdx({
      rehypePlugins: [rehypeCodeParams],
    }),
  ],
});
```

In an `.md(x)` file:

```md
This code has a param: `git commit -m "[commit_message]"`
```

This will output the following HTML for the code block:

```html
<code>git commit -m "<span class="rehype-param">[commit_message]</span>"</code>
```
npm package: @fujocoded/remark-alt-text-files
Description: Add alt text to your images directly from your filesystem
Author: FujoCoded LLC
Latest version: 0.0.2

# @fujocoded/remark-alt-text-files

A remark plugin that allows loading alt text from a file, rather than hardocding it in markdown

## Sample usage

In `astro.config.js`:

```ts
import remarkAltTextFiles from "@fujocoded/remark-alt-text-files";

export default defineConfig({
  // ...
  integrations: [
    mdx({
      remarkPlugins: [remarkAltTextFiles],
    }),
  ],
});
```

In markdown files:

```md
![regular alt text](./image.png)

![file:path/to/alt/text.alt.txt](./image.png)

# This will load alt text from "./image.alt.txt"

![file:](./image.png)
```

You can change the following options:

- `root`: where the alt text file will be searched from (default: the loaded path of the markdown file or `process.cwd()`)
- `pathPrefix`: the prefix to indicate alt text should be loaded from a file (default: `file:`)
npm package: @fujocoded/remark-capitalize-titles
Description: Make titles consistent with remark
Author: FujoCoded LLC
Latest version: 0.0.13

# @fujocoded/remark-capitalize-titles

A version of [this Vercel plugin](https://github.com/vercel/remark-capitalize) that transforms all markdown titles with [title.sh](https://github.com/zeit/title)and also accepts options.

It also allows capitalizing the `title` prop of a given list of Astro components.

By default it uses FujoCoded's own list of capitalization exceptions.

## Sample usage

In `astro.config.js`:

```ts
import remarkCapitalizeTitles from "@fujocoded/remark-capitalize-titles";

export default defineConfig({
  // ...
  integrations: [
    mdx({
      remarkPlugins: [
        [
          remarkCapitalizeTitles,
          {
            // Any component whose title prop should be capitalized
            componentNames: ["Callout", "ScenarioCallout"],
          },
        ],
      ],
    }),
  ],
});
```

### TODOs:

- [ ] Fix issue where a title in a heading that has a previous sibling will be capitalized as if the first
      word was the beginning of the sentence
- [ ] Something like "`head`ing" in titles where the word is compounded with a code thing will capitalize "ing".
npm package: @fujocoded/remark-excalidraw
Description: Load excalidraw diagrams via remark
Author: FujoCoded, LLC
Latest version: 0.0.2

# @fujocoded/remark-excalidraw

A remark plugin that allows loading excalidraw files in markdown

## TODO:

- [x] Get component to load excalidraw library
- [x] Get component to render excalidraw
- [ ] Remove need to manually import component
- [ ] Make astro client load hack configurable

## Sample usage

In `astro.config.js`:

```ts
import remarkExcalidraw from "@fujocoded/remark-excalidraw";

export default defineConfig({
  // ...
  integrations: [
    mdx({
      remarkPlugins: [remarkExcalidraw],
    }),
  ],
});
```

In markdown files:

```md
import { ExcalidrawComponent } from "@fujocoded/remark-excalidraw/component";

![alt text](./image-file.excalidraw)
```
npm package: @fujocoded/zod-transform-socials
Description: A Zod schema + transformer for social URLs
Author: FujoCoded LLC
Latest version: 0.0.13

# @fujocoded/zod-transform-socials

Applies a zod transformation to a list of social contacts. Automatically
surfaces website and username, as well as an icon name for usage with `AstroIcon`.

## Sample usage

In content collection (or other Zod bit):

```ts
import { SocialLinks } from "@fujocoded/zod-transform-socials";
// ...

export const teamCollection = defineCollection({
  type: "data",
  schema: (tools) =>
    z.object({
      // ...
      contacts: SocialLinks,
    });
});
```

Yaml file:

```yaml
name: essential-randomness
contacts:
  - https://essentialrandomness.com
  - https://essential-randomness.tumblr.com
  - https://twitter.com/essentialrandom
  - url: https://indiepocalypse.social/@essentialrandom
    platform: mastodon
  - https://github.com/essential-randomness
  - https://patreon.com/essentialrandomness
  - https://ko-fi.com/essentialrandomness
```

Usage (look at output for understading):

```ts
const team = await getCollection("team");
team.map((member) => console.log(member.data.contacts));
```

Usage as props:

```ts
import type { SocialLinksData } from "@fujocoded/zod-transform-socials";

interface Props {
  name: string;
  avatar: string;
  contacts: SocialLinksData;
}
```
npm package: @fuka-g/hasslium
Description: This project is still in development, but is ready to be used in real projects. Feel free to check it out !
Author: fuka-g
Latest version: 0.0.8

# hasslium: A TS/JS preprocessor based on C's

This project is still in development, but is ready to be used in real projects. Feel free to check it out !

The documentation is under construction, but should be informative enough for now.

## Why ?

This preprocessor is mostly useful for:
 - Front-end apps
 - Commercial apps
 - Demo products

It allows you to include or exclude certain regions of your code (development & debug statements, etc), and to define macros to replace constants you would use all over your project.

It is built around of the C preprocessor's syntax to be easy to understand and to provide a steep learning curve.

## Installation

`$ npm install -D @fuka-g/hasslium`

## Usage

For now, no CLI support has been added yet. The only way to run it is through a js script file.

```ts
// hasslim.process(input: string[], options: processOptions, callback: (error: string, output: string[]))

import * as hasslium from "@fuka-g/hasslium";
import * as fs from "fs";

hasslium.process(fs.readFileSync("yourFilePath.js").toString().split("\n"), {}, (error, output) => {
	if (error) {
		console.error(error);
	} else {
		console.log("Output:", output);
	}
});
```

## Features

 - Almost all of the C preprocessor's directives
 - Fast
 - Typed

## GCC's features

[See the original preprocessor's features.](https://gcc.gnu.org/onlinedocs/cpp/index.html)

## Syntax

All directives must start with `//#` .

 - Example: `//# define MACRO token`

You can either use `//# directive` or `//#directive` .

## Directives

### Defining macros

```ts
//# define macro token

//# undef macro
```

### Conditions

Conditional

```ts
//# if macro condition

//# elif macro condition

//# else

//# endif
```

If a macro is defined / undefined

```ts
//# ifdef macro

//# ifndef macro
```

### Diagnostics

```ts
//# warning message

//# error message
```

## Known bugs

😀

## Contributing

Contributions are welcome !