open-index/open-npm huggingface dataset:
npm package: @fyrn/cli
Description: CLI for Fyrn — AI-first integration platform
Author: Fyrn
Latest version: 0.2.0

# @fyrn/cli

CLI for [Fyrn](https://fyrn.ai) — AI-first integration platform.

## Install

```bash
npm install -g @fyrn/cli
```

Or use without installing:

```bash
npx @fyrn/cli --help
```

## Quick Start

```bash
# Login to your Fyrn account
fyrn login

# List your flows
fyrn flow list

# Create a flow with AI
fyrn flow create --ai "Send Shopify orders to Slack"

# Check flow status
fyrn flow status order-to-slack

# Build a connector from an API spec
fyrn connectors build --from-url https://api.example.com/openapi.json
```

## Commands

| Command | Description |
|---------|-------------|
| `fyrn login` | Authenticate with your Fyrn account |
| `fyrn flow` | Manage integration flows |
| `fyrn connectors` | Manage connector catalog and instances |
| `fyrn env` | Manage environments (dev, staging, prod) |
| `fyrn healing` | View and approve self-healing events |
| `fyrn governance` | Audit logs and compliance |
| `fyrn agents` | Manage AI agent keys |
| `fyrn billing` | Subscription and usage billing |
| `fyrn usage` | View platform usage metrics |
| `fyrn apis` | Manage published API endpoints |

Run `fyrn --help` for the full list, or `fyrn <command> --help` for details on any command.

## Interactive Mode

Run `fyrn` with no arguments to enter interactive mode — a conversational interface powered by AI that can execute commands on your behalf.

```bash
fyrn
```

## Authentication

`fyrn login` opens your browser for Auth0 authentication. Credentials are stored in `~/.fyrn/credentials.json`.

For CI/CD environments, set the `FYRN_API_KEY` environment variable with an agent API key.

## Configuration

The CLI reads configuration from (highest priority first):

1. Environment variables (`FYRN_API_URL`, `FYRN_API_KEY`)
2. `~/.fyrn/config.json`
3. Built-in defaults

## Documentation

Full docs at [docs.fyrn.ai](https://docs.fyrn.ai)
npm package: @fyrn/mcp-server
Description: MCP server for Fyrn — connect AI agents to your integration platform
Author: Fyrn
Latest version: 0.1.2

# @fyrn/mcp-server

MCP server for [Fyrn](https://fyrn.ai) — connect AI agents to your integration platform.

Implements the [Model Context Protocol](https://modelcontextprotocol.io/) so AI assistants like Claude can manage your integrations, flows, connectors, and more.

## Claude Desktop Setup

Add to your Claude Desktop configuration (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):

```json
{
  "mcpServers": {
    "fyrn": {
      "command": "npx",
      "args": ["@fyrn/mcp-server"],
      "env": {
        "FYRN_AGENT_KEY": "<your-agent-key>",
        "FYRN_API_URL": "https://api.fyrn.ai"
      }
    }
  }
}
```

Get your agent key from the Fyrn dashboard under **Settings > Agent Keys**.

## Environment Variables

| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `FYRN_AGENT_KEY` | Yes | — | Agent API key for authentication |
| `FYRN_API_URL` | No | `https://api.fyrn.ai` | Fyrn API base URL |
| `MCP_PORT` | No | `3100` | Port for SSE transport mode |

## Transport Modes

**stdio** (default) — communicates over stdin/stdout, used by Claude Desktop and most MCP clients:

```bash
fyrn-mcp --transport stdio
```

**SSE** — HTTP-based Server-Sent Events for web integrations:

```bash
fyrn-mcp --transport sse
```

## Available Tools

The MCP server exposes tools in three permission tiers:

- **Tier 1 (Read):** List flows, get metrics, search, view messages, call published APIs
- **Tier 2 (Build):** Create flows, deploy, generate connectors, manage adapters
- **Tier 3 (Manage):** Retry messages, approve healing events, manage schedules, batch operations

Tool access is controlled by your agent key's permission tier.

## Security

- Rate limiting (per-minute and daily quotas)
- Infinite loop detection
- PII filtering on message data
- Approval gates for destructive operations
- Full audit logging

## Documentation

Full docs at [docs.fyrn.ai](https://docs.fyrn.ai)
npm package: @fysh/vcl-react-native
Description: Velocity Career Labs React Native SDK
Author: Michael Avoyan
Latest version: 1.21.5

# @velocitycareerlabs/vcl-react-native

Velocity Career Labs React Native SDK


Android:

kotlin version: 1.7.21

minSdkVersion 24

targetSdkVersion 33


iOS:

swift version: 5

deployment target: 13


React Native:

react version 18.2.0

react native version 0.72.4

# React Native SDK

The React Native SDK is a wrapper of iOS and Android SDKs.
The minimum supported Android API is 21.
The iOS target deployment API is 12.0.

## Installation
- Add the path to the Velocity specs to the head of the Pod file in the iOS folder
`source 'https://github.com/velocitycareerlabs/Specs.git'`
- SDK installation:
```js 
yarn add @velocitycareerlabs/vcl-react-native --save
```
  or
```js 
npm install @velocitycareerlabs/vcl-react-native --save
```

### Usage
To start using the VCL SDK, you’ll need to create its object and initialize it in Velocity Network&trade;:
```js
import vcl from '@velocitycareerlabs/vcl-react-native';
```
```js
const initializationDescriptor: VCLInitializationDescriptor = {
  environment: environment,
};
vcl.initialize(initializationDescriptor).then(
  () => {
    // Do your magic
  },
  (err: VCLError) => {
    // Handle initialization failure 
  }
);
```
npm package: @fysikrevy/av-helpers
Description: Automation scripts for Fysikrevyen's AV
Author: Kristoffer Levin Hansen
Latest version: 1.1.1

Hjælpescriptsne indeholder for tiden kun scripts til emacs:

- event-catch.el

    Lytter til kommandokanalen via emacs' http faciliteter, og flytter
    cursoren i revy-dokumentet, så den følger præsentationen.
  
    Er ustabilt, har det med at låse emacs, eller time ud. Men når det
    virker er det super til at holde styr på markerede linjer.
  
- sange-til-html.el

    Funktioner, der hjælper med at konvertere tex-filer til manuskriptet
    til revy-html. Der er et udkast til en alternativ sed-kommando i
    kommentarerne.
    
    Hvis du vil have oversatte tekster med, så har flere af
    funktionerne optionelle argumenter, til at facilitere
    det. Headlineren er nok at give noget non-`nil` som andet argument
    til `insert-songs-in-plan-file`. Hvis den får et argument nr. 2
    vil der først, for hver tex-fil, kigge efter en fil med samme navn
    med `-ex` tilføjet (før `.tex`) med en oversat udgave af
    sangen. Hvis den ikke finder sådan en fil, gå den ud fra, at
    oversættelsen ligger som kommenterede linjer i samme fil som de
    originale sangtekster. Altså fx:
    
        \sings{S2} Yo, alle typer stråling er synlig herinde
        % Yo, all types of radiation are visible in here
        Sværger, det er så sandsynligt herinde
        % I swear, it's so high probability in here
        
    Hver oversat linje bliver indsat i slutningen af det
    `<p>`-element, som de originale sang-linjer bor i, som et 
    `<span class="translatoin">`-element.


Versioner
---------

###### v 1.1.1 ######

Husk at rydde op i de midlertidige buffere.

###### v 1.1.0 ######

Automatisk indsættelse af oversatte tekster (lavet eksternt,
formodentlig af de TeX-ansvarlige).

Lidt rettelser omkring tuborg-klammer og citationstegn.

###### v 1.0.1 ######
Kan nu hådtere flere `songs`-miljøer.  
`nej` udkommenteret i event-catch
npm package: @fysikrevy/sse-server
Description: Small node webserver with sse capability
Author: Kristoffer Levin Hansen
Latest version: 1.3.1
Deprecated: false


Det her er server-delen til Fysikrevyen™s AV-system. Det leverer filer
i en mappe via HTTP, det kan konvertere undertekstfiler i ass og svt
til vtt, og det sender kommandoer frem og tilbage mellem vinduer med
instanser af AV-websiden.

For at starte, skriv (efter scriptet er installeret med npm):

    sse-server
  
i den mappe, hvor av-filerne bor.
  
Serveren lytter som standard på port 80. Et numerisk argument vælger
en anden port. Fx:

    sse-server 88
  
Husk, at npm kan gøre kommandoer tilgængeligt globalt, hvis de
installeres med -g flaget.

### Søgestier

Hvis serveren ikke finder en fil, som den får forespurgt, kigger den
først efter den samme fil i mappen
`./node_modules/@fysikrevy/av-main`, derefter i mappen
`./node_modules/@fysikrevy/backstage-ticker`, og efter det i mapper,
som er angivet i miljøvariablen `NODE_MODULES_PATH`.

## Versioner

###### 1.3.1 ######
> Fix forkert message-id

###### 1.3.0 ######
> Klargjort til `backstage-ticker`. Udvidet søgesti, og en ny kanal
> til SSE'er: kommandoer sendes på `/stream-bck`, og modtages på
> `/set-bck`.

###### 1.2.6 ######
> Fallback-søgestier er nu en rigtig feature, med en nogenlunde
> fornuftig implementering.

###### 1.2.5 ######
> Den mest irriterende bugfix i verden.

###### 1.2.4 ######
> Bugfix

###### 1.2.3 ######
> Bugfix

###### 1.2.2 ######
> Beskyttelse mod crashes på grund af dårlig html-kode, når vi
> reagerer på en "n"-kommando.
>
> Kigger også i mapper givet af miljøvariablen NODE_MODULES_PATH

###### 1.2.1 ######
> "nej"--kommandoen opdaterer nu kildefilen direkte. Laver også en backup af kildefilen (max hver 5. minut).

###### 1.1.0
> Kig også efter filer i `node_modules/@fysikrevy/av-main`.

###### 1.0.7
> Introduktion af Cache-Control header-e, i første omgang på mapper
> med skrifttypefiler.

###### 1.0.6
> Kan nu afkode procent-kodede URI'er

###### 1.0.5
> Bugfix

###### 1.0.4
> Readme tilføjet (denne fil)

###### 1.0.3
> Første version, som kom ordentligt på npm
npm package: @fyuzh/koishi-plugin-bilibili-notify
Description: [![npm](https://img.shields.io/npm/v/@fyuzh/koishi-plugin-bilibili-notify?style=flat-square)](https://www.npmjs.com/package/@fyuzh/koishi-plugin-bilibili-notify)
Latest version: 0.0.1

# @fyuzh/koishi-plugin-bilibili-notify

[![npm](https://img.shields.io/npm/v/@fyuzh/koishi-plugin-bilibili-notify?style=flat-square)](https://www.npmjs.com/package/@fyuzh/koishi-plugin-bilibili-notify)
npm package: @fyxgaming/run
Description: Run Javascript library
Latest version: 1.0.1

# Run

[![tests](https://github.com/runonbitcoin/run/workflows/tests/badge.svg)](https://github.com/runonbitcoin/run/actions) [![codecov](https://codecov.io/gh/runonbitcoin/run/branch/master/graph/badge.svg?token=VPXTBV9CQP)](https://codecov.io/gh/runonbitcoin/run)

## Commands

- `npm run lint` - Lint and automatically fix errors
- `npm run build` - Build outputs
- `npm run test` - Test library quickly
- `npm run test:node` - Test the minified node build
- `npm run test:browser` - Test the minified browser build (Chrome default)
- `npm run test:cover` - Collect code coverage
- `npm run deploy` - Redeploy extras to the blockchain
- `npm run bump` - Create a new patch release
- `npm run test test/plugins/local-purse.js` - Run just the purse tests

## Configuring the tests

Various environment variables may be used to configure the tests:

| Name              | Description                                     | Possible Values                                | Default     |
|-------------------|-------------------------------------------------|------------------------------------------------|-------------|
| `NETWORK`         | Network to test on                              | `mock`, `main`, `test`, `stn`                  | `mock`      |
| `BROWSER`         | Browser used for testing                        | `chrome`, `firefox`, `safari`, `MicrosoftEdge` | `chrome`    |
| `STRESS`          | Whether to run the stress tests                 | `true`, `false`                                | `false`     |
| `PURSE_[network]` | Purse key used on a specific network            | your string privkey                            | `undefined` |
| `API`             | Blockchain API when not using the mock network  | `run`, `whatsonchain`                          | `undefined` |
| `APIKEY_[api]`    | API key used with a specific blockchain API     | your string api key                            | `undefined` |
| `LOGGER`          | Whether to log internal messages to the console | `true`, `false`                                | `false`     |

### Examples

- `env BROWSER=safari npm run test:browser` - Test the browser build on Safari
- `env STRESS=1 npm run test` - Test library with stress tests
- `env NETWORK=test env PURSE=<funded_private_key> npm run test` - Run all tests on testnet

### .env file

For ease of use, you may also store these variables in a `.env` file where the tests are run. Here's a sample:

```
BROWSER=safari
PURSE_MAIN=<your priate key>
PURSE_TEST=<your private key>
APIKEY_MATTERCLOUD=<your api key>
```
npm package: @fyxt/hds-react
Description: React components for the Helsinki Design System (FYXT fork)
Latest version: 4.2.0-custom.2

# hds-react [![npm](https://img.shields.io/npm/v/hds-react?style=flat-square)](https://www.npmjs.com/package/hds-react) [![npm bundle size](https://img.shields.io/bundlephobia/minzip/hds-react?label=gzipped%20size&style=flat-square)](https://bundlephobia.com/result?p=hds-react)

A library of Helsinki Design System components implemented using React.

:books: [See the components in Storybook](https://hds.hel.fi/storybook/react)

## Getting started

Install the package.

```bash
yarn add hds-react
```

### Using the components

JS
```js
import { TextInput } from "hds-react";

// you can also import components individually instead of importing the whole package
import { TextInput } from "hds-react/components/TextInput";
```

### Helsinki fonts

The Helsinki fonts are not included in the package due to copyright reasons.

## Development

Read more [here](DEVELOPMENT.md).

## Built with

- React with [TypeScript](https://www.typescriptlang.org/) support
- Bundled with [Rollup](https://github.com/rollup/rollup), compiled with [Babel](https://github.com/babel/babel)
- [CSS Modules](https://github.com/css-modules/css-modules) with [typed-css-modules](https://github.com/Quramy/typed-css-modules) for styles
- [ESLint](https://github.com/eslint/eslint) for code analysis
- [Prettier](https://github.com/prettier/prettier) for code formatting
- [Jest](https://github.com/facebook/jest) with [React Testing Library](https://github.com/testing-library/react-testing-library) for testing
- [Loki](https://loki.js.org/) for visual regression testing

## Supported browsers

Helsinki Design System uses the react-scripts library's default browserslist config to target a broad range of browsers.
This means that the following browsers are supported:

- Chrome
- Chrome for Android
- Chrome for iOS ([uses same engine as Safari iOS](https://github.com/browserslist/browserslist#browsers))
- Edge
- Edge for Android ([uses same engine as Chrome for Android](https://github.com/browserslist/browserslist#browsers))
- Edge for iOS ([uses same engine as Safari iOS](https://github.com/browserslist/browserslist#browsers))
- Firefox
- Firefox for Android
- Firefox for iOS ([uses same engine as Safari iOS](https://github.com/browserslist/browserslist#browsers))
- Safari
- Safari iOS

The supported browser versions are listed in [browserslists test page](https://browsersl.ist/#q=%3E+0.2%25%2C+not+dead%2C+not+op_mini+all&region=FI)

More info about browser support:

- [Create React App - Configuring Supported Browsers](https://create-react-app.dev/docs/supported-browsers-features/#configuring-supported-browsers)
- [HDS documentation general FAQ - What browser and browser versions are supported?](https://hds.hel.fi/getting-started/faq#general)
npm package: @fyzhu/elegant-ui
Description: A high quality UI components Library with Vue.js
Author: Aresn
Latest version: 4.2.1

更改两个地方

node.vue 增加
@contextmenu="handleSelect"
tree.vue 修改
this.$set(node, 'selected', !node.selected); 为
this.$set(node, 'selected', true);

修改后使用 yarn dist:prod 打包
npm package: @fyzhu/vite-plugin-qiankun
Description: vite for qiankun
Author: markteng
Latest version: 1.0.15

#### 简介

> vite-plugin-qiankun: 帮助应用快速接入乾坤的vite插件

- 保留vite构建es模块的优势
- 一键配置，不影响已有的vite配置
- 支持vite开发环境

#### 快速开始

###### 1、在 `vite.config.ts` 中安装插件
```typescript
// vite.config.ts

import qiankun from 'vite-plugin-qiankun';

export default {
  // 这里的 'myMicroAppName' 是子应用名，主应用注册时AppName需保持一致
  plugins: [qiankun('myMicroAppName')],
  // 生产环境需要指定运行域名作为base
  base: 'http://xxx.com/'
}
```
###### 2、在入口文件里面写入乾坤的生命周期配置

```typescript
// main.ts
import { renderWithQiankun, qiankunWindow } from 'vite-plugin-qiankun/dist/helper';

// some code
renderWithQiankun({
  mount(props) {
    console.log('mount');
    render(props);
  },
  bootstrap() {
    console.log('bootstrap');
  },
  unmount(props: any) {
    console.log('unmount');
    const { container } = props;
    const mountRoot = container?.querySelector('#root');
    ReactDOM.unmountComponentAtNode(
      mountRoot || document.querySelector('#root'),
    );
  },
});

if (!qiankunWindow.__POWERED_BY_QIANKUN__) {
  render({});
}
```

###### 3、dev下作为子应用调试

> 因为开发环境作为子应用时与热更新插件（可能与其他修改html的插件也会存在冲突）有冲突，所以需要额外的调试配置

```typescript
// useDevMode 开启时与热更新插件冲突,使用变量切换
const useDevMode = true

const baseConfig: UserConfig = {
  plugins: [
    ...(
      useDevMode ? [] : [
        reactRefresh()
      ]
    ),
    qiankun('viteapp', {
      useDevMode
    })
  ],
}
```
上面例子中 `useDevMode = true` 则不使用热更新插件，`useDevMode = false` 则能使用热更新，但无法作为子应用加载。

###### 4、其它使用注意点 `qiankunWindow`

因为es模块加载与`qiankun`的实现方式有些冲突，所以使用本插件实现的`qiankun`微应用里面没有运行在js沙盒中。所以在不可避免需要设置window上的属性时，尽量显示的操作js沙盒，否则可能会对其它子应用产生副作用。qiankun沙盒使用方式
```typescript
import { qiankunWindow } from 'vite-plugin-qiankun/dist/helper';

qiankunWindow.customxxx = 'ssss'

if (qiankunWindow.__POWERED_BY_QIANKUN__) {
  console.log('我正在作为子应用运行')
}

```

#### 例子

详细的信息可以参考例子里面的使用方式
 ```
git clone xx
npm install
npm run example:install
# 生产环境调试demo
npm run example:start
# vite开发环境demo, demo中热更新已经关闭
npm run example:start-vite-dev
```
npm package: @fyzhu/vue-context-menu
Description: Vue 2.0 右键菜单组件，菜单内容可以随意自定义
Author: fyzhu
Latest version: 1.0.6

# vue-context-menu

> Vue 2.0 右键菜单组件，菜单内容可以随意自定义

![Preview](https://github.com/binggg/vue-context-menu/blob/master/demo/assets/demo.jpeg?raw=true)

## 安装
```
npm install @xunlei/vue-context-menu
```

## 在线Demo

https://xunleif2e.github.io/vue-context-menu/demo/dist

## 使用

### 1. 注册组件

#### 方式1 利用插件方式全局注册

```javascript
import VueContextMenu from '@xunlei/vue-context-menu'
import Vue from 'vue'

Vue.use(VueContextMenu)
```
#### 方式2 局部注册

```javascript
import { component as VueContextMenu } from '@xunlei/vue-context-menu'

export default {
  // ...
  components: {
    'vue-context-menu': VueContextMenu
  }
}
```

#### 方式3 独立版本引入，自动全局注册
> 前提是 vue 也是独立版本通过script标签引入

```html
<script src="./node_modules/dist/vue-context-menu.js"></script>
```

### 2. 模版语法
```html
 <context-menu class="right-menu" 
    :target="contextMenuTarget" 
    :show="contextMenuVisible" 
    @update:show="(show) => contextMenuVisible = show">
    <a href="javascript:;" @click="copyMsg">复制</a>
    <a href="javascript:;" @click="quoteMsg">引用</a>
    <a href="javascript:;" @click="deleteMsg">删除</a>
</context-menu>
```

## Props

| 参数                    | 说明  | 类型 | 可选值 | 默认值 |
|-------------------------|-------|------|--------|--------|
| target | 触发右键事件的元素  | Element | -      | -      |
| show | 是否显示右键菜单  | Boolean | -      | false      |
| width | 右键菜单宽度  | Number | -      | 81      |
| height | 右键菜单高度  | Number | -      | 98      |


## Events

| 事件名                    | 说明  | 事件参数
|-------------------------|-------|------|
| update:show | 右键菜单显示/隐藏时触发  | 是否显示 |


## 注意

如果target是某个兄弟元素，可以使用 `$refs`来访问，但是注意请在父组件mounted 之后获取。

参考 https://cn.vuejs.org/v2/guide/components.html#子组件索引


## ChangeLog
- [1.0.3] 2020-06-24
  - 增加边界检测，在最右侧点击显示在左侧，在最底部点击显示在上侧
  - 
- [1.0.1] 2017-07-10
  - 修复 target 为空时可能出错的bug

- [1.0.0] 2017-06-23
  - 实现右键菜单基本功能

## Development Setup

``` bash
# install deps
npm install

# serve demo at localhost:8080
npm run dev

# build library and demo
npm run build

# build library
npm run build:library

# build demo
npm run build:demo
```

## License

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

Copyright (c) 2017 赵兵
npm package: @fyzhu/wheel
Description: a BetterScroll plugin to imitate IOS Picker
Author: fyzhu
Latest version: 2.5.2

# @better-scroll/wheel

[中文文档](https://github.com/ustbhuangyi/better-scroll/blob/master/packages/wheel/README_zh-CN.md)

Implement a plugin similar to the effects of the IOS Picker component.

## Usage

```js
import BScroll from '@better-scroll/core'
import Wheel from '@better-scroll/wheel'
BScroll.use(Wheel)

const bs = new BScroll('.wheel-wrapper', {
  wheel: {
    selectedIndex: 0,
    wheelWrapperClass: 'wheel-scroll',
    wheelItemClass: 'wheel-item',
    wheelDisabledItemClass: 'wheel-disabled-item'
  },
  probeType: 3
})
```
npm package: @fyzhu/wooo
Description: FE Build tool with easy cli.
Author: keelii
Latest version: 1.1.4

# Wooo

[![Wooo Version](https://img.shields.io/npm/v/wooo.svg)](https://www.npmjs.com/package/wooo)
[![Build Status](https://travis-ci.org/keelii/wo.svg?branch=master)](https://travis-ci.org/keelii/wo)
[![codecov.io](https://codecov.io/github/keelii/wo/coverage.svg?branch=master)](https://codecov.io/github/keelii/wo?branch=master)
[![dependencies up to date](https://david-dm.org/keelii/wo.svg)](https://david-dm.org/keelii/wo)
[![License](https://img.shields.io/npm/l/wooo.svg)](https://www.npmjs.com/package/wooo)

A FE Build tool with easy cli.

```
┬ ┬╔═╗╔═╗╔═╗
│││║ ║║ ║║ ║
└┴┘╚═╝╚═╝╚═╝
```

## Requirement

> "node" : ">=8.0.0"

## Install globally

> npm install wooo -g

```
Usage: wo <command> <input> <options>

command:
  build     - clear && build all source files to dest
  deploy    - build && upload to ftp server
  release   - build && taged git source - (Experimental)
  start     - build && start a local server with default root [.www]
  clear     - by default, rm -rf build .www
  gen       - generate a new demo project

input:
  path/to/dir
  glob/pattern/**
  path/to/file.ext
  component_name
  component_name1,component_name2
  gen_project_name

options:
  --sprite      - concat sprites to one image and generate a style file
  --nunjucks    - compile nunjucks to html
  --uglify      - compress scripts
  --imagemin    - optimize images
  --sass        - compile sass to css
  --debug       - build uncompressed js file
  --force       - deploy file with no cache
  --currdir     - generate demo project file to current directory
  --config      - specified config file path
```

## Bundled with npm scripts

> npm install wooo --save-dev

```
"scripts": {
    "start": "node ./node_modules/wooo start",
    "build": "node ./node_modules/wooo build",
    "build:sprite": "node ./node_modules/wooo build --sprite",
    "deploy": "node ./node_modules/wooo deploy",
    "release": "node ./node_modules/wooo release",
    "clear": "node ./node_modules/wooo clear",
    "gen": "node ./node_modules/wooo gen"
}
```

## Documention

[wiki](https://github.com/keelii/wo/wiki)
npm package: @fyzu/logger
Description: A common logger for my ecosystem
Author: Dmitry Petrov
Latest version: 1.0.1

[![deps][deps]][deps-url]

## Install

```bash
npm i -D @fyzu/logger
```

> ⚠️ We do not recommend installing this module globally

## Usage

```js
const createLogger = require('@fyzu/logger')
const logger = createLogger({ name: 'wds' })

logger.info('Server Starting')
```

## Options

|Name|Type|Default|Description|
|:--:|:--:|:-----:|:----------|
|[**`name`**](#name)|`{String}`|`''<unknown>'`|Log Name (**Required**)|
|[**`level`**](#level)|`{String}`|`'info'`|Log Level|
|[**`unique`**](#unique)|`{String}`|`true`|Log Uniqueness|
|[**`timestamp`**](#timestamp)|`{Boolean}`|`false`|Log Timestamps|

### `name`  

Specifies the name of the log to create. **This option is required**, and used to differentiate between loggers when `webpack-log` is used in multiple projects
executing in the same process

```js
const logger = createLogger({ name: 'wds' })
```

### `level`   

Specifies the level the logger should use. A logger will not produce output for
any log level _beneath_ the specified level. Available levels and order are:

```js
[
  'info',
  'warn',
  'error',
  'trace',
  'debug',
  'silent'
]
```

```js
const logger = createLogger({ level: 'error' })

logger.error(err)
```

> ℹ️ The level names shown above correspond to the available logging methods,
with the notable exception of the `silent` level

### `timestamp`

If `true`, instructs the logger to display a timestamp for log output, preceding
all other data

```js
const logger = createLogger({ timestamp: true })
```

[deps]: https://david-dm.org/fyzu/logger.svg
[deps-url]: https://david-dm.org/fyzu/logger