open-index/open-npm huggingface dataset:
npm package: @lexbuild/mcp
Description: Model Context Protocol server for LexBuild. Exposes U.S. legal sources to AI agents.
Author: Chris Thomas
Latest version: 1.23.2

# @lexbuild/mcp

Model Context Protocol server for [LexBuild](https://lexbuild.dev). Gives AI agents direct access to U.S. legal sources: the U.S. Code, Code of Federal Regulations, and Federal Register.

## Install

```bash
npx @lexbuild/mcp
```

Or install globally:

```bash
npm install -g @lexbuild/mcp
```

## Configuration

### Claude Desktop

Add to your Claude Desktop MCP config (`~/Library/Application Support/Claude/claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "lexbuild": {
      "command": "npx",
      "args": ["-y", "@lexbuild/mcp"]
    }
  }
}
```

### Claude Code

```json
{
  "mcpServers": {
    "lexbuild": {
      "command": "npx",
      "args": ["-y", "@lexbuild/mcp"]
    }
  }
}
```

### With an API key (optional, for higher rate limits)

```json
{
  "mcpServers": {
    "lexbuild": {
      "command": "npx",
      "args": ["-y", "@lexbuild/mcp"],
      "env": {
        "LEXBUILD_API_KEY": "lxb_your_key_here"
      }
    }
  }
}
```

## Tools

| Tool | Description |
|------|-------------|
| `search_laws` | Full-text search across USC, CFR, and Federal Register |
| `get_section` | Fetch a single legal section by identifier |
| `list_titles` | List available titles (USC/CFR) or years (FR) |
| `get_title` | Get title detail with chapters, or year detail with months |
| `get_federal_register_document` | Fetch an FR document by document number |

## Resources

URI-addressable legal sections via the `lexbuild://` scheme:

- `lexbuild://us/usc/t{title}/s{section}` — U.S. Code section
- `lexbuild://us/cfr/t{title}/s{section}` — CFR section
- `lexbuild://us/fr/{document_number}` — Federal Register document

## Prompts

| Prompt | Description |
|--------|-------------|
| `cite_statute` | Generate a Bluebook citation for a USC or CFR section |
| `summarize_section` | Plain-language summary with audience targeting |

## Hosted Endpoint

A hosted MCP server is available at `mcp.lexbuild.dev` using the Streamable HTTP transport. No API key required for basic usage.

## Security

- All legal text is wrapped with injection defense markers
- Response sizes are capped at 256KB to protect model context
- SSRF protection via egress host allowlist
- Rate limiting per session (anonymous: 60 req/min)

## License

MIT
npm package: @lexey/v-calendar-fixed
Description: A clean and extendable plugin for building simple attributed calendars in Vue.js.
Author: Nathan Reyes
Latest version: 1.0.0

<p align="center">
    <a href="https://vcalendar.io/" target="_blank">
      <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557324348/v-calendar/hero.png">
    </a>
    <br>
    An elegant calendar and datepicker plugin for Vuejs.
</p>

<p align="center">
    <a href="https://www.npmjs.com/package/v-calendar"><img src="https://img.shields.io/npm/dt/v-calendar.svg" alt="Total Downloads"></a>
    <a href="https://github.com/nathanreyes/v-calendar/releases"><img src="https://img.shields.io/npm/v/v-calendar.svg" alt="Latest Release"></a>
    <a href="https://github.com/nathanreyes/v-calendar/releases"><img src="https://img.shields.io/npm/v/v-calendar/next.svg" alt="Next Release"></a>
    <a href="https://github.com/nathanreyes/v-calendar/blob/master/LICENSE"><img src="https://img.shields.io/npm/l/v-calendar.svg" alt="License"></a>
</p>

------

```bash
npm i --save v-calendar
```

## Documentation

For full documentation, visit [vcalendar.io](https://vcalendar.io/).

### Attributes

| Highlights | Dots |
| :---: | :---: |
| <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557326557/v-calendar/highlights.png"> | <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557326557/v-calendar/dots.png"> |

| Bars | Popovers |
| :---: | :---: |
| <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557326557/v-calendar/bars.png"> | <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557326557/v-calendar/popovers.png"> |

### Multi-Paned Calendars

<img width="400" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557326946/v-calendar/multi-paned.png">

### Theme Colors & Dark-Mode

| | |
| :---: | :---: |
| <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327273/v-calendar/dark-blue.png"> | <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327429/v-calendar/dark-red.png"> |
| <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327429/v-calendar/dark-teal.png"> | <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327429/v-calendar/dark-purple.png"> |

### Date Pickers

| **Single Date** | **Multiple Date** | **Date Range** |
| :---: | :---: | :---: |
| <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327864/v-calendar/single-picker.png"> | <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327864/v-calendar/multi-picker.png"> | <img width="200" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557327864/v-calendar/range-picker.png"> |

### Custom Calendars w/ Scoped Slots

<img width="400" src="https://res.cloudinary.com/dqgcfqzpk/image/upload/v1557328504/v-calendar/custom-calendars.png">
npm package: @lexia/ui
Description: Local runner that serves Lexia built frontend with API/WS proxy to your agent backend
Latest version: 1.2.1

Lexia UI Runner
===============

Serve the built Lexia frontend locally with API/WS proxy to your agent backend.

**Note:** Upload functionality should be handled by your agent backend, not this UI package.

Usage
-----

```bash
npx @lexia/ui --port=3000 --agent-port=5001
# or if installed globally
lexia-ui --port 3000 --agent-port 5001
```

Flags
-----
- --port: port to serve frontend (default 3000)
- --host: bind address (default 127.0.0.1)
- --agent-port: local agent port (default 5000)
- --agent-url: override full agent URL (e.g., http://localhost:8000)
- --api-prefix: path prefix for API proxy (default /api)
- --ws-prefix: path prefix for WS proxy (default /ws)
- --cors: enable permissive CORS (default false)
- --open: open browser on start (default false)

How It Works
------------
- Static frontend: Served from /
- Proxy: All /api/* and /ws/* requests → forwarded to your agent backend
- Your backend should handle all API logic including file uploads
npm package: @lexiang/babel-plugin-component
Description: Modular build plugin for babel.
Latest version: 0.2.7

## Introduction
lazy load component, base on [babel-plugin-component](https://www.npmjs.com/package/babel-plugin-component)

## Install

```shell
yarn add @lexiang/babel-plugin-component -D
```

## Usage
Via `.babelrc` or babel-loader.
```javascript
{
  "plugins": [
    ["@lexiang/babel-plugin-component", options]
  ]
}
```

## options
- libraryName: module name
- styleLibraryName: style module name
- styleLibrary: Import a independent theme package with more config
  ```
  styleLibrary: {
    "name": "xxx", // same with styleLibraryName
    "base": true,  // if theme package has a base.css
    "path": "[module]/index.css",  // the style path. e.g. module Alert =>  alert/index.css
    "mixin": true  // if theme-package not found css file, then use [libraryName]'s css file
  }
  ```
- style: import css from '[module]/index.css', default `false`
- libDir: dist directory, default `lib`
- root: main file dir, default `index`
- camel2Dash: whether parse name to dash mode or not, default `true`

## Example
convert
```javascript
import { button } from 'components';
```
to
```javascript
var button = require('components/lib/button');
```

## style Example
when it is set to `true`
convert
```javascript
import { button } from 'components';
```
to
```javascript
var button = require('components/lib/button/index.css');
```
npm package: @lexiang/babel-plugin-import
Description: Component modular import plugin for babel.
Latest version: 0.3.0

## Introduction
lazy load component, base on [babel-plugin-import](https://www.npmjs.com/package/babel-plugin-import)

## Example

### basic usage
```javascript
plugins: [
  [
    '@lexiang/babel-plugin-import',
    {
      libraryName: '@lexiang/venom',
      componetDirectoryPrefix: 'venom-',
    },
  ],
]
```
lazy load component
```javascript
import { venomButton } from '@lexiang/venom';

      ↓ ↓ ↓ ↓ ↓ ↓

var button = require('@lexiang/venom/lib/button');
require('@lexiang/venom/lib/button/index.csss');
```

### multi usage
```javascript
plugins: [
  [
    '@lexiang/babel-plugin-import',
    {
      libraryName: '@lexiang/venom',
      componetDirectoryPrefix: 'venom-',
    },
    '@lexiang/venom',
  ],
  [
    '@lexiang/babel-plugin-import',
    {
      libraryName: '@lexiang/nova',
      componetDirectoryPrefix: 'nova-',
    },
    '@lexiang/nova',
  ],
],
```

see more configs at [babel-plugin-import](https://www.npmjs.com/package/babel-plugin-import)
npm package: @lexiang/commitlint-config
Description: commitlint rules config
Latest version: 0.2.4

## Introduction
commitlint rules config

## Install
```shell
yarn add @lexiang/commitlint-config -D
```
.commitlintrc.js
```js
module.exports = {
  extends: ['@lexiang/commitlint-config'],
}
```

## License
MIT
npm package: @lexiang/commitlint-plugin-subject
Description: commitlint subject plugin
Latest version: 0.1.1

## Introduction
Verify git message subject contain some regexp string

## Installation

```bash
yarn add @lexiang/commitlint-plugin-subject -D
```

## Usage

```javascript
module.exports = {
  plugins: ['@lexiang/commitlint-plugin-subject'],
  rules: {
    'subject-regexp': [2, 'always', /--bug=\d+/],
  },
};
```
npm package: @lexiang/design
Description: 基于TDesign适配桌面端的组件库，适合在vue 2.6技术栈项目中使用。
Latest version: 0.1.32

# 乐享 PC 端组件库

> 基于 TDesign 适配桌面端的组件库，适合在 vue 2.6 技术栈项目中使用。

## 官网

npm：[@lexiang/design](https://www.npmjs.com/package/@lexiang/design)

测试环境：[https://lexiangla.net/design/getting-started](https://lexiangla.net/design/getting-started)

正式环境：[https://lexiangla.com/design/getting-started](https://lexiangla.com/design/getting-started)

## 快速开始

安装 npm 依赖，初始化和拉取 tdesign

```shell
yarn install
yarn sub:init
```

## 开发调试

### 使用组件文档调试

组件要求文档先行，文档中有具体的组件调用，可以在组件文档中调试组件

```shell
yarn site:dev
```

访问[http://localhost:16001/design](http://localhost:16001/design)到对应的组件页面进行调试

### 使用 yalc 调试

```shell
# 全局安装yalc
yarn global add yalc

# design项目，每次变更后构建推送
yarn serve
yalc push

# 目标项目，以swan项目举例，仅需执行一次
yalc add @lexiang/design
swan-yarn-watch
```

## 脚本

- `sub:init`: 子模块初始化和拉取
- `tdesign:update`: tdesign 子模块更新
- `wasp:update`: 更新 wasp 图标库
- `generate:usage`: 顶部组件可配置例子自动生成
- `wasp:update`: 更新 wasp 子模块和 icon manifest
- `site:dev`: 组件文档开发环境
- `site:build`: 组件文档生产环境构建产物
- `site:preview`: 组件文档本地预览生产构建产物
- `dev`: 组件开发环境
- `build`: 组件生产构建
- `pub`: 组件 npm 发布

## 组件开发

### 组件目录

```text
components
  │── cus-component // 自建组件
  │  ├── _example // 组件示例
  │  │    └── base.vue
  │  ├── _usage // 可配置的组件示例
  │  │    ├── index.vue // 跑`generate:usage`脚本自动生成
  │  │    ├── props.json // 可配置的属性
  │  ├── cus-component.md // 组件文档
  │  ├── cus-component.index // 组件
  │  └── index.ts // 组件入口
  └── ext-config-provider // tdesign组件扩展
```

### 组件规范

- 乐享自建组件前缀统一为`TCus`
- TDsign 组件扩展前缀统一为`TExt`

### 组件适配原则

以适配 tag-input 为例

1. **分析所需适配的组件组成**，例如 tag-input 由 input、tag 组成，那么组件适配的优先级，应该先考虑 input 和 tag 的适配，再考虑 tag-input 的适配
2. **针对单一组件，优先适配 token**, 例如 tag-input 中，tdesign 提供了对应的 token（style/web/components/tag-input/_var.less），此时应该优先用 token 覆盖的方式来适配
3. **降级覆盖 class**，token 不满足时，考虑通过 class 覆盖的方式适配
4. **递归组件适配到顶层**，基础组件适配完后，再重复流程适配到顶层组件
npm package: @lexiang/eslint-config-lexiang
Description: base eslint rules
Latest version: 0.3.0

## Introduction
eslint rules config，include base es6 rules and import rules

## Install
```shell
yarn add @lexiang/eslint-config-lexiang -D
```
.eslintrc.js
```js
module.exports = {
  extends: ['@lexiang/eslint-config-lexiang'],
}
```
## License
MIT
npm package: @lexiang/eslint-config-prettier
Description: eslint config for prettier
Latest version: 0.3.1

## Introduction
eslint config for prettier

## Install
```shell
yarn add @lexiang/eslint-config-prettier -D
```
.eslintrc.js
```js
module.exports = {
  extends: ['@lexiang/eslint-config-prettier'],
}
```

## License
MIT
npm package: @lexiang/eslint-config-ts-lexiang
Description: eslint rules config for ts
Latest version: 0.3.3

## Introduction
eslint rules config for typescript

## Install
```shell
yarn add @lexiang/eslint-config-ts-lexiang -D
```
.eslintrc.js
```js
module.exports = {
  extends: ['@lexiang/eslint-config-ts-lexiang'],
}
```

## License
MIT
npm package: @lexiang/eslint-config-ts-vue
Description: eslint rules config for vue with ts
Latest version: 0.1.2

## Introduction
eslint rules config for vue with ts

## Install
```shell
yarn add @lexiang/eslint-config-ts-vue -D
```
.eslintrc.js
```js
module.exports = {
  extends: ['@lexiang/eslint-config-ts-vue'],
}
```

## License
MIT
npm package: @lexiang/eslint-config-vue-lexiang
Description: eslint rules config for vue
Latest version: 0.3.0

## Introduction
eslint rules config for vue

## Install
```shell
yarn add @lexiang/eslint-config-vue-lexiang -D
```
.eslintrc.js
```js
module.exports = {
  extends: ['@lexiang/eslint-config-vue-lexiang'],
}
```

## License
MIT
npm package: @lexiang/mystique-render
Description: mystique render sdk
Latest version: 0.4.317

# @lexiang/mystique-render
> 乐搭微页面渲染sdk，与@@lexiang/mystique-playground搭配使用

## 使用方式
```
<template>
  <mystique-render :tree="tree"></mystique-render>
</template>

<script>
import mystiqueRender from '@lexiang/mystique-render';
export default {
  components: { mystiqueRender },
  setup() {
    // 需替换成由@lexiang/mystique-playground生成的json tree的内容
    const tree = getJsonTreeFunc();

    return {
      tree,
    };
  },
}
</script>
```
npm package: @lexiang/mystique-shared-assets
Description: mystique public static assets
Latest version: 0.4.9

# @lexiang/mystique-shared-assets

> 乐搭微页面组件库静态资源共享包

这里的静态资源主要包括 pigeon 和 swallow 的公用且体积较小的图片、icon 等，例如轻享中使用到的表情包集合。图片以 base64url 的方式共享，独立 esmodule 供上层导入。

## 开发注意事项

对应的文件夹下应以 index.ts 导出所有 import 的图片变量，供顶层 src/index.ts 全量导出到包外，例如：

```shell
.
├── src
│   └── assets
│   │   └── img
│   │       └── face-v2 # index.ts 导出所有表情包资源
│   │           └── index.ts # index.ts 导出所有表情包资源
└───└── index.ts # 导出所有 assets 下的资源
```
npm package: @lexiang/remote-import
Description: lexiang remote import
Latest version: 0.1.58-alpha.2

## 简介
远程加载UMD格式的组件

## 基础使用
传入`js`和`css`地址，模拟AMD加载返回组件模块
```js
const { component } = importModule({
  js: '',
  css: '',
});
```
npm package: @lexiang/remote-shared
Description: lexiang remote shared
Latest version: 0.1.58

## 远程组件共享

### 简介
远程组件共享，需要配合远程组件库一起使用，支持懒加载、调试远程组件

### NPM安装
```shell
yarn add @lexiang/remote-shared
```

### 基础使用
```js
import { lazyloadRemote } from '@lexiang/remote-shared';

const loadRemote = async () => {
  await lazyloadRemote(name, options);
  // 或者
  // await lazyloadRemote(options);
}
```

##### 参数
- `name`: 要加载的组件/工具函数名
- `options`
  - `url`: 请求组件库资源的API地址
  - `version`: 组件库版本，默认最新版
  - `debug`: 是否开启调试，默认值`false`，设置为`true`时会请求远程组件库资源
  - `target`: 要加载的组件，默认值`[]`，单options参数下默认加载远程组件库全部组件和工具函数
  - `project`: 上传至COS单独组件文件夹，默认值`remote-component`
npm package: @lexiang/rollup-plugin-svg-sprite
Description: rollup svg sprite loader
Latest version: 0.1.3

# @lexiang/rollup-plugin-svg-sprite

Import svg files into sprite，base on [rollup-svg-sprite-loader](https://www.npmjs.com/package/rollup-svg-sprite-loader)

## Installation

```bash
yarn add @lexiang/rollup-plugin-svg-sprite -D
```

## Usage

```js
// rollup.config.js
import svgSpriteLoader from '@lexiang/rollup-plugin-svg-sprite';

export default {
  plugins: [
    svgSpriteLoader(),
  ],
};
```
npm package: @lexiang/runtime-import
Description: Import remote resource(js or css) asynchronously.
Latest version: 0.1.3
Deprecated: this package is no longer supported

# runtime-import

Import remote resource(js or css) asynchronously. base on [runtime-import](https://www.npmjs.com/package/runtime-import)

## Install

```shell
yarn add @lexiang/runtime-import
```

## Usage

### importScript

Import a javascript file, if the file is in UMD format, return it's export object.

```js
import { importScript } from '@lexiang/runtime-import'

try {
  const $ = await importScript('//foobar.com/jquery.js')
} catch (err) {
  console.error(err)
}
```

### importStyle

Import a css file.

```js
import { importStyle } from '@lexiang/runtime-import'

try {
  await importStyle('//foobar.com/bootstrap.css')
} catch (err) {
  console.error(err)
}
```

### importComponent

Import a component. In umd mode, if the last javascript file is in UMD format, return it's export object.

Options:

- js: List of js files.
- css: List of css files.
- crossOrigin: value of attribute `crossorigin` of script tags created internally.
- umd: Whether UMD mode is enabled.

Note:

- The default value of the field `crossOrigin` of importComponent's options is `true`. It sets the attribute `crossorigin` of `<script>` elements created by importComponent to `"anonymous"`. If you don't want the attribute `"crossorigin"` to be setted, please make sure that the field `crossOrigin` of importComponent's options setted to `""`.

```js
import { importComponent } from '@lexiang/runtime-import'

try {
  const bootstrap = await importComponent({
    js: ['//foobar.com/bootstrap.js'],
    css: ['//foobar.com/bootstrap.css'],
    crossOrigin: '',
    umd: true
  })
} catch (err) {
  console.error(err)
}
```

### importModule

`importComponent` use to be called `importModule`, legacy projects could use `importModule` as usual.
npm package: @lexiang/skills
Description: 乐享知识库 MCP Skills — 为 AI Agent 提供乐享知识库的搜索、写入、Block 操作、文件管理能力
Latest version: 1.0.0

# @lexiang/skills

> 乐享知识库 MCP Skills — 为 AI Agent 提供乐享知识库的搜索、写入、Block 操作、文件管理能力

## 快速开始

```bash
npx @lexiang/skills install
```

自动检测已安装的 AI Agent（Claude Code、CodeBuddy、OpenCode 等），将 Skills 复制到对应目录。

安装完成后，在 AI 对话中输入 **"配置乐享"**，AI 会引导你完成 MCP 连接配置。

## Skills 列表

| Skill | 说明 | 必装 |
|-------|------|------|
| `lexiang-setup` | MCP 配置向导 — 首次配置、Token 管理、连接验证 | ✅ |
| `lexiang-core` | 核心基础 — 数据模型、URL 规则、安全规则 | ✅ |
| `lexiang-search` | 搜索与浏览 — 关键词/语义搜索、内容读取 | |
| `lexiang-writer` | 文档写入 — 创建文档、导入 Markdown/HTML | |
| `lexiang-blocks` | Block 操作 — 创建/更新/删除 Block、结构化编辑 | |
| `lexiang-files` | 文件管理 — 三步上传、文件夹同步、批量上传 | |

## 安装选项

### 预设方案

```bash
# 完整安装（默认）— 所有 6 个 Skill
npx @lexiang/skills install

# 标准安装 — 配置 + 核心 + 搜索 + 写入
npx @lexiang/skills install --preset standard

# 最小安装 — 配置 + 核心 + 搜索
npx @lexiang/skills install --preset minimal
```

### 指定 Agent

```bash
# 仅安装到 Claude Code
npx @lexiang/skills install --target claude

# 仅安装到 CodeBuddy
npx @lexiang/skills install --target codebuddy

# 仅安装到通用标准目录 (~/.agents/skills/)
npx @lexiang/skills install --target agents
```

### 自定义目录

```bash
npx @lexiang/skills install --dir ~/my-custom-skills
```

### 查看可用 Skills

```bash
npx @lexiang/skills available
```

## 安装目录

CLI 会自动将 Skills 安装到以下目录：

| 目录 | 说明 | 条件 |
|------|------|------|
| `~/.agents/skills/` | Agent Skills 通用标准 | 始终安装 |
| `~/.claude/skills/` | Claude Code 专用 | 检测到 `~/.claude/` 存在时 |
| `~/.codebuddy/skills/` | CodeBuddy 专用 | 检测到 `~/.codebuddy/` 存在时 |
| `~/.opencode/skills/` | OpenCode 专用 | 检测到 `~/.opencode/` 存在时 |

## 配置 MCP 连接

安装完成后，你需要配置乐享 MCP 服务器连接。有三种方式：

1. **AI 引导配置**（推荐）：在 AI 对话中说 "配置乐享"
2. **手动配置**：参考 [乐享 MCP 文档](https://lexiangla.com/mcp)
3. **环境变量**：设置 `LEXIANG_COMPANY_FROM` 和 `LEXIANG_ACCESS_TOKEN`

### 获取凭证

1. 访问 [lexiangla.com/mcp](https://lexiangla.com/mcp)
2. 获取你的 `company_from`（企业标识）
3. 生成 `access_token`

## License

MIT
npm package: @lexiang/stylelint-config
Description: styleint rules config
Latest version: 0.1.4

## Introduction
stylelint rules config

## Install
```shell
yarn add @lexiang/stylelint-config -D
```
.stylelintrc.js
```js
module.exports = {
  extends: ['@lexiang/stylelint-config'],
}
```

## License
MIT
npm package: @lexiang/vite-plugin-svg-sprite
Description: SVG sprite plugin for Vite
Latest version: 0.1.3

# @lexiang/vite-plugin-svg-sprite

SVG sprite plugin for [Vite](https://github.com/vitejs/vite). base on [vite-plugin-svg-sprite](hhttps://www.npmjs.com/package/vite-plugin-svg-sprite)

## install
```
npm i @lexiang/vite-plugin-svg-sprite -D
```

## Usage

Add the plugin to your `vite.config.js`:

```javascript
import createSvgSpritePlugin from 'vite-plugin-svg-sprite';

const config = {
  plugins: [
    createSvgSpritePlugin({
      symbolId: 'icon-[name]-[hash]',
    }),
  ],
}
```

Then use it like that in your app code:

```jsx
import appIcon from './path/to/icons/app.svg';

// react or vue component, as you want
export default function App() {
  return (
    <svg>
      <use
        xlinkHref={`#${appIcon.id}`}
      />
    </svg>
  );
}
```

You can also access the `width`/`height` attributes of the SVG with the `size` export:

```jsx 
import appIcon, { size } from './path/to/icons/app.svg';

// react or vue component, as you want
export default function App() {
  return (
    <svg {...size}>
      <use
        xlinkHref={`#${appIcon.id}`}
      />
    </svg>
  );
}
```

If you're using TypeScript, add the following line to your `vite-env.d.ts`:
```diff
/// <reference types="vite/client" />
+ /// <reference types="vite-plugin-svg-sprite/client" />
```

## options

```javascript
const plugin = createSvgSpritePlugin(options);
```

### `options.symbolId: string`

For generating the `id` attribute of `<symbol>` element. Defaults to `[name]`

### `options.include: string | string[]`

Match files that will be transformed. Defaults to `'**.svg'`. See [micromatch](https://github.com/micromatch/micromatch) for the syntax document.

### `options.svgo: boolean | SvgoOptions`

Enable [SVGO](https://github.com/svg/svgo) for optimizing SVG. Defaults to `true`.
npm package: @lexiang/vue-cli-plugin-qiankun
Description: vue-cli plugin to qiankun micro framework
Latest version: 0.1.0
Deprecated: ignore

## vue-cli-plugin-qiankun

> qiankun plugin for vue-cli

### 使用步骤 (Use setup)

1. 创建主应用 (Create master project)

``` sh
$ vue create master
$ cd master
$ vue add vue-cli-plugin-qiankun --type master
```

2. 创建子应用 (Create slave project)

``` sh
$ vue create foo-app
$ cd foo-app
$ vue add vue-cli-plugin-qiankun --type slave --port 8081
```

3. 配置主应用 (Config master project)

> master/src/App.vue

``` vue
<script>
export default {
  name: 'master',
  data () {
    return {
      // ...
      apps: [
        { name: 'foo-app', entry: '//localhost:8081', container: '#appContainer', activeRule: '/foo-app' }
      ]
    }
  },
  // ...
  methods: {
    // ...
    initQiankun () {
      // ...
      setDefaultMountApp('/foo-app')
      // ...
    }
  }
}
</script>
```

4. 运行各项目 (Run each project)

``` sh
$ cd master
$ yarn serve
```

``` sh
$ cd foo-app
$ yarn serve
```

### 示例 (Examples)

> [DEMO](https://f-loat.github.io/vue-cli-plugin-qiankun)

``` sh
$ cd examples
$ yarn
$ yarn install:all
$ yarn serve:all
```

### 功能 (Features)

- 修改项目文件引入 qiankun 框架

- 注入 qiankun 框架要求的构建配置

- 自动配置 `publicPath` 处理资源路径

### 致谢 (Acknowledgements)

- [vue-cli](https://github.com/vuejs/vue-cli) Standard Tooling for Vue.js Development.

- [qiankun](https://github.com/umijs/qiankun) Blazing fast, simple and completed solution for micro frontends.

- [single-spa](https://github.com/CanopyTax/single-spa) What an awesome meta-framework for micro-frontends!
npm package: @lexiang/vue-cli-plugin-qiankun-pc
Description: vue-cli plugin to qiankun micro framework
Latest version: 0.1.3

## @lexiang/vue-cli-plugin-qiankun-pc

> vue-cli plugin to qiankun micro framework

### 使用步骤 (Use setup)

``` sh
$ vue create micro-app
$ cd micro-app
$ vue add @lexiang/vue-cli-plugin-qiankun-pc --type micro --port 8081
```
npm package: @lexiang/vue-style-loader
Description: Vue.js style loader module for webpack and support web component style hot reload
Latest version: 0.2.1

This is a fork based on [vue-style-loader@4.1.3](https://www.npmjs.com/package/vue-style-loader/v/4.1.3). it is a Vue.js style loader module for webpack and support web component style hot reload.

## Options

- **manualInject** (3.1.0+):

  Type: `boolean`. When importing the style from a non-vue-file, by default the style is injected as a side effect of the import. When `manualInject` is true, the imported style object exposes a `__inject__` method, which can then be called manually at appropriate timing. If called on the server, the method expects one argument which is the `ssrContext` to attach styles to.

  ``` js
  import styles from 'styles.scss'

  export default {
    beforeCreate() { // or create a mixin for this purpose
      if(styles.__inject__) {
        styles.__inject__(this.$ssrContext)
      }
    }

    render() {
      return <div class={styles.heading}>Hello World</div>
    }
  }
  ```

  Note this behavior is enabled automatically when `@lexiang/vue-style-loader` is used on styles imported within a `*.vue` file. The option is only exposed for advanced usage.

- **ssrId** (3.1.0+):

  Type: `boolean`. Add `data-vue-ssr-id` attribute to injected `<style>` tags even when not in Node.js. This can be used with pre-rendering (instead of SSR) to avoid duplicate style injection on hydration.

## Differences from `style-loader`

### Server-Side Rendering Support

When bundling with `target: 'node'`, the styles in all rendered components are collected and exposed on the Vue render context object as `context.styles`, which you can simply inline into your markup's `<head>`. If you are building a Vue SSR app, you probably should use this loader for CSS imported from JavaScript files too.

### Misc

- Does not support url mode and reference counting mode. Also removed `singleton` and `insertAt` query options. It always automatically pick the style insertion mechanism that makes most sense. If you need these capabilities you should probably use the original `style-loader` instead.

- Fixed the issue that root-relative URLs are interpreted against chrome:// urls and make source map URLs work for injected `<style>` tags in Chrome.

## License

MIT
npm package: @lexical-devtools/react
Description: React plugin for Lexical DevTools
Latest version: 0.1.11

# `@lexical-devtools/react`

A React plugin designed to use with [Lexical DevTools Extension](https://chromewebstore.google.com/detail/lexical-devtools/dmbopeepjkdlplkjcjbnfiikajiddhnd) to inspect Lexical.js editor state within React applications.

> **Note** This plugin is intended to be used with the Lexical DevTools Extension, available on the Chrome Web Store. You can download it [here](https://chromewebstore.google.com/detail/lexical-devtools/dmbopeepjkdlplkjcjbnfiikajiddhnd).

## Usage

### Installation

```bash
npm i @lexical-devtools/react
```

### Import `DevToolsPlugin` inside your `LexicalComposer` component

```tsx
import { LexicalComposer } from "@lexical/react/LexicalComposer";
import DevToolsPlugin from "@lexical-devtools/react";

export default function Page() {
  const config = {
    // ...
  };

  return (
    <LexicalComposer initialConfig={config}>
      // ...
      <DevToolsPlugin />
    </LexicalComposer>
  );
}
```
npm package: @lexicon-community/types
Description: Complete typescript types and validation functions generated for lexicon-community lexicons
Latest version: 1.0.0

# js-lexicon-community-types
Complete typescript types and validation functions generated for the [lexicon-community lexicon schemas](https://github.com/lexicon-community/lexicon) using the [atproto lex-cli package](https://github.com/bluesky-social/atproto/tree/main/packages/lex-cli)

## Getting started
TODO

## Usage
TODO

## Generating types from the [Lexicons repo](https://github.com/lexicon-community/lexicon)

1. Setup the [ATProto repo](https://github.com/bluesky-social/atproto) locally
2. `cd path_to_atproto_repo\atproto\packages\lex-cli`
3. `npx lex gen-api path_to_this_repo\tpyes\community\lexicon\your_lexicon path_to_lexicon_repo\community\lexicon\your_lexicon\your_schema.json`
npm package: @lexiconjs/react
Description: The javascript SDK for the lexicon translator.
Author: Odin Labs, LLC
Latest version: 3.0.0

<p align="center">
  <p align="center">
    <a href="https://www.lexiconjs.com/?utm_source=github&utm_medium=logo" target="_blank">
      <img src="https://github.com/odin-labs-tech/lexicon-react/blob/main/assets/logo.svg?sanitize=true" alt="Lexicon" width="280" height="84">
    </a>
  </p>
  <p align="center">
    Effortless app translation for a world without borders.
  </p>
</p>

[![npm version](https://img.shields.io/npm/v/@lexiconjs/react.svg)](https://www.npmjs.com/package/@lexiconjs/react)

# Official Lexicon SDK for React

This is the Lexicon SDK for React: `@lexiconjs/react`

It provides a a simple and automatic way to translate all of your websites / apps by leveraging AI to translate your content (without impacting your existing workflows).

## Links

- [Documentation](https://docs.lexiconjs.com)
- [Website](https://www.lexiconjs.com)

## Supported Platforms

This integration is very unobtrusive and works on all react / react-native front-ends:

- React
- Next.js
- React Native / Expo

## 🚀 Get Started with Lexicon

1. [Sign up for an account](https://www.lexiconjs.com)
2. Create an application in your Lexicon dashboard
3. Prepare your codebase using our [Getting Started Guide](https://docs.lexiconjs.com)
npm package: @lexidum/type-and-draw
Description: Basic typewriter and drawing tool
Author: Alexandra Dumitrescu
Latest version: 1.0.1

# Text and drawing tool

An experiment working with node.js and canvas.

Try by installing:

```
npm install @lexidum/type-and-draw
```

Example usage:

```js
const textImage = require("./index").textImage;
const path = require("path");
textImage(
  path.join(__dirname, "result.png"),
  {
    startX: 20,
    startY: 40,
    letterWidth: 30,
    letterHeight: 30,
    imageWidth: 600,
    imageHeight: 600,
    bg: "black",
    textColor: "white",
  },
  "this is a sample text"
);
```
npm package: @lexifi/sdk
Description: SDK for LexiFi compliance hooks on Base — integrate KYC/AML pools with EAS attestations and ZK-proofs
Author: LexiFi
Latest version: 1.0.0

# @lexifi/sdk

**LexiFi** — Compliance-as-a-Service for DeFi on Base.

Integrate KYC/AML-gated Uniswap V4 pools using EAS attestations and zero-knowledge proofs.

## Installation

```bash
npm install @lexifi/sdk
```

## Contracts (Base Mainnet)

| Contract | Address |
|---|---|
| MultiProviderComplianceHook | `0x607c0334cb4d00CdE6fB6dfcf35E4D2a98865BFb` |
| ZKPassProvider | `0x929E5aB25B8E5F37c85dF59792FB24aDe61Cb646` |

- [Hook on BaseScan](https://basescan.org/address/0x607c0334cb4d00CdE6fB6dfcf35E4D2a98865BFb)
- [ZKPassProvider on BaseScan](https://basescan.org/address/0x929E5aB25B8E5F37c85dF59792FB24aDe61Cb646)

## Usage

### Get deployment addresses

```typescript
import { getDeployment } from "@lexifi/sdk";

const base = getDeployment(8453);
console.log(base.contracts.multiProviderComplianceHook);
// 0x607c0334cb4d00CdE6fB6dfcf35E4D2a98865BFb

console.log(base.contracts.zkPassProvider);
// 0x929E5aB25B8E5F37c85dF59792FB24aDe61Cb646
```

### Use ABIs with viem

```typescript
import { createPublicClient, http } from "viem";
import { base } from "viem/chains";
import { MultiProviderComplianceHookABI, getDeployment } from "@lexifi/sdk";

const client = createPublicClient({ chain: base, transport: http() });
const deployment = getDeployment(8453)!;

// Check a user's compliance tier
const tier = await client.readContract({
  address: deployment.contracts.multiProviderComplianceHook,
  abi: MultiProviderComplianceHookABI,
  functionName: "getComplianceTier",
  args: ["0xYourUserAddress"],
});

console.log("Compliance tier:", tier);
// 0 = NONE, 1 = BASIC, 2 = ENHANCED, 3 = INSTITUTIONAL
```

### Check ZK proof verification

```typescript
import { ZKPassProviderABI, getDeployment } from "@lexifi/sdk";

const deployment = getDeployment(8453)!;

const isVerified = await client.readContract({
  address: deployment.contracts.zkPassProvider,
  abi: ZKPassProviderABI,
  functionName: "isVerified",
  args: ["0xYourUserAddress"],
});
```

## Compliance Tiers

| Tier | Value | Description |
|---|---|---|
| `NONE` | 0 | No compliance — pool access denied |
| `BASIC` | 1 | Coinbase Account attestation (KYC lite) |
| `ENHANCED` | 2 | Coinbase Country + ZKPass proof |
| `INSTITUTIONAL` | 3 | Full institutional verification |

## Architecture

- **MultiProviderComplianceHook** — A Uniswap V4 hook that enforces compliance checks via `beforeSwap` and `beforeAddLiquidity`.
- **ZKPassProvider** — Accepts zero-knowledge proofs from zkPass TransGate, storing verified tiers on-chain without exposing raw identity data.
- **EAS Integration** — Trusts attestations from Coinbase (and other issuers) registered on Ethereum Attestation Service.

## License

MIT
npm package: @lexify/core
Description: Lexify engine abstraction — no React, no UI
Latest version: 0.0.3

# @lexify/core

> Editor engine for [Lexify](https://github.com/muhammad4dev/lexify) — no React, no UI, no Lexical types in your app code.

📖 **[Full documentation →](https://muhammad4dev.github.io/lexify)** · [GitHub](https://github.com/muhammad4dev/lexify) · [Changelog](https://github.com/muhammad4dev/lexify/releases)

## Installation

```bash
pnpm add @lexify/core
```

## Overview

`@lexify/core` is the foundation of Lexify. It provides a typed command bus, plugin registry, and the `LexifyEditor` interface that abstracts over Lexical's editor. No Lexical types leak into your application — the public API is fully self-contained.

## Usage

```typescript
import { createEditor, createCommand } from "@lexify/core";
import type { LexifyPlugin } from "@lexify/core";

// Create a typed command
const MY_COMMAND = createCommand<string>("my-plugin:my-action");

// Write a plugin
const myPlugin: LexifyPlugin = {
  name: "my-plugin",
  register(editor) {
    const unsub = editor.registerCommandHandler(MY_COMMAND, (payload) => {
      editor.update(() => {
        // use Lexical $ functions here
      });
    });
    return unsub; // cleanup
  },
};

// Create the editor
const editor = createEditor({
  namespace: "my-editor",
  plugins: [myPlugin],
});

// Dispatch a command
editor.dispatchCommand(MY_COMMAND, "hello");
```

## API

### `createEditor(config)`

| Option      | Type             | Description                    |
| ----------- | ---------------- | ------------------------------ |
| `namespace` | `string`         | Unique identifier              |
| `plugins`   | `LexifyPlugin[]` | Plugins to register at startup |
| `theme`     | `LexifyTheme`    | CSS class name map             |

### `createCommand<T>(type)`

Creates a typed command token. `type` must be globally unique — use `scope:action` format.

### `LexifyEditor` interface

```typescript
interface LexifyEditor {
  namespace: string;
  registerPlugin(plugin: LexifyPlugin): void;
  registerCommandHandler<T>(
    command: LexifyCommand<T>,
    handler: (payload: T) => void,
  ): () => void;
  dispatchCommand<T>(command: LexifyCommand<T>, payload: T): void;
  update(updater: () => void): void;
  destroy(): void;
}
```

## License

MIT © [Muhammad Mustafa](https://github.com/muhammad4dev)
npm package: @lexify/react
Description: React bindings for Lexify
Latest version: 0.0.3

# @lexify/react

> React bindings for [Lexify](https://github.com/muhammad4dev/lexify) — `LexifyComposer`, `useLexifyEditor`, controlled & uncontrolled modes.

📖 **[Full documentation →](https://muhammad4dev.github.io/lexify)** · [GitHub](https://github.com/muhammad4dev/lexify) · [Changelog](https://github.com/muhammad4dev/lexify/releases)

## Installation

```bash
pnpm add @lexify/react @lexify/core
```

## Usage

### Basic editor

```tsx
import { LexifyComposer } from "@lexify/react";
import { boldPlugin, italicPlugin } from "@lexify/plugins";

export function MyEditor() {
  return (
    <LexifyComposer
      namespace="my-editor"
      plugins={[boldPlugin, italicPlugin]}
      placeholder="Start typing…"
    />
  );
}
```

### With toolbar

```tsx
import { LexifyComposer, useLexifyEditor } from "@lexify/react";
import { boldPlugin, FORMAT_BOLD_COMMAND } from "@lexify/plugins";

function BoldButton() {
  const editor = useLexifyEditor();
  return (
    <button
      onClick={() => editor.dispatchCommand(FORMAT_BOLD_COMMAND, undefined)}
    >
      B
    </button>
  );
}

export function MyEditor() {
  return (
    <LexifyComposer namespace="my-editor" plugins={[boldPlugin]}>
      <BoldButton />
    </LexifyComposer>
  );
}
```

### Controlled mode

```tsx
const [state, setState] = useState<SerializedEditorState>(initialState);

<LexifyComposer
  namespace="my-editor"
  plugins={[boldPlugin]}
  value={state}
  onChange={setState}
/>;
```

## Props

| Prop           | Type                    | Description                               |
| -------------- | ----------------------- | ----------------------------------------- |
| `namespace`    | `string`                | **Required.** Unique editor identifier    |
| `plugins`      | `LexifyPlugin[]`        | Plugins to register at mount              |
| `theme`        | `LexifyTheme`           | CSS class name map                        |
| `className`    | `string`                | Applied to the `contenteditable` element  |
| `placeholder`  | `ReactNode`             | Shown when editor is empty                |
| `initialState` | `SerializedEditorState` | Uncontrolled initial state                |
| `value`        | `SerializedEditorState` | Controlled state                          |
| `onChange`     | `(state) => void`       | Called on every state change              |
| `children`     | `ReactNode`             | Rendered inside the composer context tree |

## License

MIT © [Muhammad Mustafa](https://github.com/muhammad4dev)
npm package: @lexify/themes
Description: Styling presets for Lexify
Latest version: 0.0.3

# @lexify/themes

> Theme presets for [Lexify](https://github.com/muhammad4dev/lexify) — `baseTheme`, `darkTheme`, and a ready-to-use CSS file.

📖 **[Full documentation →](https://muhammad4dev.github.io/lexify)** · [GitHub](https://github.com/muhammad4dev/lexify) · [Changelog](https://github.com/muhammad4dev/lexify/releases)

## Installation

```bash
pnpm add @lexify/themes @lexify/core
```

## Usage

```tsx
import { LexifyComposer } from "@lexify/react";
import { baseTheme } from "@lexify/themes";
import "@lexify/themes/css/base.css"; // optional default styles

<LexifyComposer
  namespace="my-editor"
  plugins={[...]}
  theme={baseTheme}
/>
```

### Dark theme

```tsx
import { darkTheme } from "@lexify/themes";

<LexifyComposer theme={darkTheme} ...>
```

### Custom theme

```typescript
import type { LexifyTheme } from "@lexify/core";

const myTheme: LexifyTheme = {
  paragraph: "my-paragraph",
  heading: {
    h1: "my-h1",
    h2: "my-h2",
    h3: "my-h3",
  },
  text: {
    bold: "my-bold",
    italic: "my-italic",
    underline: "my-underline",
    strikethrough: "my-strikethrough",
    code: "my-code",
  },
  link: "my-link",
  list: {
    ul: "my-ul",
    ol: "my-ol",
    listitem: "my-listitem",
  },
  // ... other node types
};
```

## Exports

| Export         | Description                                                   |
| -------------- | ------------------------------------------------------------- |
| `baseTheme`    | Full theme mapping all node types to `lexify-*` class names   |
| `darkTheme`    | Same as `baseTheme` with `-dark` suffix on all class names    |
| `css/base.css` | Default styles for all `lexify-*` classes (import separately) |

## Overriding styles

The CSS file uses plain class names — override any of them in your own stylesheet:

```css
/* override heading styles */
.lexify-h1 {
  font-size: 2rem;
  font-weight: 700;
  color: var(--my-heading-color);
}
```

## License

MIT © [Muhammad Mustafa](https://github.com/muhammad4dev)
npm package: @lexingtonthemes/astro-image-inspector
Description: Astro Dev Toolbar app to inspect images on hover: actual size, render size, and warnings
Latest version: 0.3.0

# @lexingtonthemes/astro-image-inspector

Astro Dev Toolbar app that lets you **inspect images on hover** during local development: see actual size, render size, loading mode, and common warnings (upscaled, oversized source, missing dimensions).

Only runs when `astro dev` is running; it does not appear in production builds.

## Install

```bash
npm install @lexingtonthemes/astro-image-inspector --save-dev
```

## Setup

In `astro.config.mjs`:

```js
import { defineConfig } from 'astro/config';
import imageInspector from '@lexingtonthemes/astro-image-inspector';

export default defineConfig({
  integrations: [
    imageInspector(),
  ],
});
```

## Usage

1. Run `astro dev`.
2. Hover near the bottom of the page to show the Dev Toolbar.
3. Click the **Image Inspector** icon to turn inspection on.
4. Hover over any `<img>` on the page to see:
   - **natural** – intrinsic width×height
   - **rendered** – displayed width×height
   - **loading** – `lazy` / `eager` / `auto`
   - **class** – CSS classes on the element (if any)
   - **warnings** – e.g. Upscaled, Possibly oversized source, No width/height

The inspector draws a highlight around the hovered image and shows a small info panel (bottom-left by default).

## Config

| Option            | Default            | Description                                              |
| ----------------- | ------------------ | -------------------------------------------------------- |
| `enabled`         | `true`             | Enable the Image Inspector app.                         |
| `appName`         | `"Image Inspector"`| Label in the dev toolbar.                               |
| `showWarningsOnly`| `false`            | *(Reserved)* Only show panel when there are warnings.    |
| `warnOnUpscale`   | `true`             | *(Reserved)* Warn when image is rendered larger than source. |
| `warnOnOversized` | `true`             | *(Reserved)* Warn when source is much larger than render size. |

Example:

```js
imageInspector({
  enabled: true,
  appName: 'Images',
}),
```

## Warnings

- **Upscaled** – Rendered size is larger than the image’s natural size.
- **Possibly oversized source** – Natural dimensions are more than 2× the rendered size (good candidate for resizing).
- **No width/height** – Missing `width`/`height` attributes (can affect layout and LCP).

## Publishing (maintainers)

This package is published under the [@lexingtonthemes](https://www.npmjs.com/settings/lexingtonthemes/packages) npm organization.

```bash
npm run build
npm publish
```

Ensure you are logged in (`npm login`) and have access to the `lexingtonthemes` org.

## License

MIT © [Lexington Themes](https://lexingtonthemes.com/)
npm package: @lexinzector/vue3-noty
Description: Noty plugin for Vue3
Author: Alexey
Latest version: 1.0.1

# vue3-noty

A Vue3 wrapper around [Noty](http://ned.im/noty/). Developped for Vue 3.

## Getting Started

Install using npm:

```bash
npm install @lexinzector/vue3-noty
```

Include using script tag:

```html
<script src="/dist/vue3-noty.umd.js"></script>
// or
<script type="module" src="/dist/vue3-noty.es.js"></script>
```

Import and register Vue plugin:

```js
import { createApp } from 'vue';
import App from './App.vue';
import NotyPlugin from '@lexinzector/vue3-noty';

const app = createApp(App);

// По желанию передать дефолтные опции Noty
app.use(NotyPlugin, {
  timeout: 4000,
  progressBar: true,
})

app.mount('#app');
```

### Import noty styles

Import stylesheet in your vue / js components:

```js
import '@lexinzector/vue3-noty/dist/vue3-noty.css';
```

Or, import styles in your less / scss stylesheet:

```less
@import '~@lexinzector/vue3-noty/dist/vue3-noty.css';
```

## Usage

In your Vue.js components, simply call one of these methods:

### Options API

```js
// Basic alert
this.$noty.show("Hello world!");

// Success notification
this.$noty.success("Your profile has been saved!");

// Error message
this.$noty.error("Oops, something went wrong!");

// Warning
this.$noty.warning("Please review your information.");

// Basic alert
this.$noty.info("New version of the app is available!");
```

All of these methods will return a Noty object instance, so you can use available [API methods](https://ned.im/noty/#/api). Example:

```js
this.$noty.show("Hello world!").setTimeout(4500);
```

Create your own notification with access to the [full list of options](https://ned.im/noty/#/options). Example:

```js
this.$noty.create({
  text: 'This is a custom notification!',
  type: 'warning',
  layout: 'topCenter',
  timeout: 4500,
  progressBar: false
}).show();
```

### Composition API

```js
import { inject } from 'vue';

export default {
  setup() {
    const noty = inject('noty');

    function notifyError() {
      noty.error('Ошибка!');
    }

    return { notifyError }
  }
}
```

## Configuration

### Config defaults

You can set a default configuration object when registering the plugin. Example:

```js
app.use(NotyPlugin, {
  timeout: 4000,
  progressBar: true,
  layout: 'topCenter'
});
```

### Config override

All of the alert methods can accept a config object as second parameter if you need to override the defaults. Example:

```js
this.$noty.info("Hey! Something very important here...", {
  killer: true,
  timeout: 6000,
  layout: 'topRight'
});
```

For more information about available configuration properties, please read [Noty's documentation](https://ned.im/noty/#/options).