open-index/open-npm huggingface dataset:
npm package: @michael-klein/funcy.js
Description: A functional web-components wrapper
Author: Michael Klein
Latest version: 0.3.7-alpha

<h1 align="center">
  funcy.js: A functional web-components wrapper
</h1>
<p align="center">
  <img src="https://i.imgur.com/1nJ9kJd.png" width="572" alt="example of code">
</p>

### Why 'funcy.js'?

Naming things is hard and 'funcy.js' (pronounced like funky.js) seemed like a [fun](http://www.badum-tish.com/), recognizable name.

### What is it?

funcy.js seeks to provide a functional way of defining web components, very much akin to [react](https://reactjs.org/)  [functional components](https://reactjs.org/docs/components-and-props.html#function-and-class-components) with [hooks](https://reactjs.org/docs/hooks-intro.html). This is as of right now *purely experimental*.

Proper documentation will follow soon. For now you may look at todo example in the examples folder or the following codepen:

https://codepen.io/michael-klein/pen/xmQZBx

#### currently implemented hooks:

* __useReducer__
* __useState__
* __useEffect__
* useRenderer 
* usePreactHtm
* useAttribute
* useCSS
* useExposeMethod
npm package: @michael-lefebvre/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.1.0

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebook/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebook/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.
npm package: @michael-spengler/tslint
Description: .
Author: Michael Spengler
Latest version: 1.0.0

# My Favorites
A reasonable set of rules + rule configurations


## Usage Example
Enter the following data in your tslint.json file:

    {
        "extends": [
            "./node_modules/@michael-spengler/tslint/tslint.json"
        ]
    }



## Feedback
Feel free to open an issue or a pull request [here](https://github.com/michael-spengler/tslint.git).
npm package: @michael-template/template-typescript-library
Description: template-typescript-library
Author: Michael
Latest version: 1.0.3

# Commit Rule

https://www.npmjs.com/package/@commitlint/config-conventional?activeTab=readme

# Docs

https://github.com/conventional-changelog/commitlint

# Configs github CI/CD NPM_TOKEN

https://github.com/dmcong/template-typescript-library/settings/secrets/actions
npm package: @michael-yakovlev/biome-config
Description: My personal Biome config
Author: Michael Yakovlev
Latest version: 0.2.1

# Biome config

Личная конфигурация в npm-пакете.

## Установка

```sh
npm install --save-dev @michael-yakovlev/biome-config
```

## Настройка VSCode

Чтобы использовать "Biome" в VSCode нужно установить плагин [Biome Extension for VS Code](https://marketplace.visualstudio.com/items?itemName=biomejs.biome):

Откройте файл .vscode/settings.json и добавьте настройки:

```json
{
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  },
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true
}
```
npm package: @michael-yakovlev/eslint-plugin-fsd
Description: FSD eslint rules
Author: Michael Yakovlev
Latest version: 0.2.2

# @michael-yakovlev/eslint-plugin-fsd

Этот плагин для ESLint содержит правила Feature-Sliced Design.

## Установка

Установите плагин выполнив команду в терминале:

```sh
npm install @michael-yakovlev/eslint-plugin-fsd --save-dev
```

## Использование

Добавьте плагин в файл конфигурации `eslint.config.ts`:

```ts
import { defineConfig } from 'eslint/config'
import pluginFsd from '@michael-yakovlev/eslint-plugin-fsd'

export default defineConfig([pluginFsd.configs.recommended])
```

Использование алиасов:

```ts
import { defineConfig } from 'eslint/config'
import pluginFsd from '@michael-yakovlev/eslint-plugin-fsd'

export default defineConfig([
    {
        ...pluginFsd.configs.recommended,
        rules: {
            'eslint-plugin-fsd/path-checker': ['error', { alias: '~' }],
            'eslint-plugin-fsd/layer-imports': ['error', { alias: '~' }],
            'eslint-plugin-fsd/public-api-imports': ['error', { alias: '~' }],
        },
    },
])
```

Добавление файлов Vue для проверки:

```ts
import { defineConfig } from 'eslint/config'
import pluginFsd from '@michael-yakovlev/eslint-plugin-fsd'

export default defineConfig([
    {
        ...pluginFsd.configs.recommended,
        files: ['**/*.?([cm])[jt]s?(x)', '**/*.vue'],
    },
])
```
npm package: @michael-yakovlev/prettier-config
Description: My personal Prettier config
Author: Michael Yakovlev
Latest version: 1.0.7

# prettier-config

Простая конфигурация в npm-пакете.

## Быстрый старт

Если у вас уже настроен "Prettier", просто установите и используйте:

```sh
npm install --save-dev @michael-yakovlev/prettier-config
```

Добавьте ключ `prettier` в `package.json`, чтобы использовать конфигурацию в вашем проекте:

```json
"prettier": "@michael-yakovlev/prettier-config",
```

## Детали конфигурации

```js
{
    printWidth: 120,
    tabWidth: 4,
    useTabs: false,
    semi: false,
    singleQuote: true,
    quoteProps: 'as-needed',
    trailingComma: 'all',
    bracketSpacing: true,
    objectWrap: 'preserve',
    bracketSameLine: false,
    arrowParens: 'always',
    endOfLine: 'lf',
}
```

[Ознакомьтесь с документацией "Prettier" для получения дополнительной информации о конфигурациях общего доступа](https://prettier.io/docs/sharing-configurations).

## Настройка в 3 этапа

Инструкции, если вы никогда раньше не пользовались "Prettier".

### 1. Установите Prettier

"Prettier" должен быть установлен как dev-зависимость

```sh
npm install --save-dev --save-exact prettier
```

### 2. Установите пакет и обновите файл package.json

Установите пакет с помощью `npm` (или `yarn`, или `pnpm`)

```sh
npm install --save-dev @michael-yakovlev/prettier-config
```

Добавьте ключ `prettier` в `package.json`

```diff
diff --git a/package.json b/package.json
index 2ecef3d..260838f 100644
--- a/package.json
+++ b/package.json
@@ -5,6 +5,7 @@
   "keywords": [
     "prettier"
   ],
+  "prettier": "@michael-yakovlev/prettier-config",
   "license": "MIT",
   "main": "index.js"
```

### 3. Настройка VSCode

Чтобы использовать "Prettier" в VSCode нужно установить плагин [Prettier - Code formatter](https://github.com/prettier/prettier-vscode):

В терминале VSCode выполните следующую команду:

```sh
ext install esbenp.prettier-vscode
```

Откройте файл .vscode/settings.json и добавьте настройки:

- Расширение "Prettier - Code formatter" настроено в качестве средства форматирования по умолчанию.
- Форматирование при сохранении включено.

```json
{
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "editor.formatOnSave": true
}
```

## Расширение конфигурации

Чтобы расширить конфигурацию и перезаписать некоторые свойства из конфигурации, импортируйте в файл `.prettierrc.mjs` конфиг и экспортируйте изменения, например:

```js
// .prettierrc.mjs
import prettierConfig from '@michael-yakovlev/prettier-config'

/**
 * @type {import("prettier").Config}
 */
const config = {
    ...prettierConfig,
    tabWidth: 2,
}

export default config
```
npm package: @michael.warneke/ng-schematics
Description: Schematics for Angular
Author: Michael Warneke
Latest version: 0.0.4

# NG-Schematics

This is a project for testing different angular schematic scenarios

It merges the ngrx and nrwl schematics and adds custom schematics.

At the moment the custom schematics consist of

# ngrx-action

Creates an action file with actions declared as interfaces and the usage of action creator functions.
This is the way the ngrx codegen produced actions.

ng g ngrx-action LoadBooks --groupName=Books

# ngrx-add-action

Adds an action to the specified action file by craetung the type, interface and creator function.

ng g ngrx-add-action SaveBooks --actionPath="path to action file" --payload=book --payloadType=Book
npm package: @michael1011/eth-block-tracker
Description: This module walks the Ethereum blockchain, keeping track of the latest block. It uses a web3 provider as a data source and will continuously poll for the next block.
Author: kumavis
Latest version: 3.0.0


# eth-block-tracker

This module walks the Ethereum blockchain, keeping track of the latest block.
It uses a web3 provider as a data source and will continuously poll for the next block.

```js
const HttpProvider = require('ethjs-provider-http')
const BlockTracker = require('eth-block-tracker')

const provider = new HttpProvider('https://mainnet.infura.io')
const blockTracker = new BlockTracker({ provider })
blockTracker.on('block', console.log)
blockTracker.start()
```

### methods

##### new BlockTracker({ provider, pollingInterval })

creates a new block tracker with `provider` as a data source and
`pollingInterval` (ms) timeout between polling for the latest block.

##### getCurrentBlock()

synchronous returns the current block. may be `null`.

```js
console.log(blockTracker.getCurrentBlock())
```

##### awaitCurrentBlock()

Returns a promise. asynchronously returns the current block.
if not yet available, it will wait until it has the latest block.

##### start({ fromBlock })

Start walking from the `fromBlock` (default: `'latest'`) forward.
`fromBlock` should be a number as a hex encoded string.
Returns a promise which is rejected if an error in encountered.

```js
blockTracker.start()
```

```js
blockTracker.start({ fromBlock: '0x00' })
```

##### stop()

Stop walking the blockchain.

```js
blockTracker.stop()
```

### EVENTS

##### block

The `block` event is emitted for every block in order.
Use this event if you want to operate on every block without missing any.

```js
blockTracker.on('block', (newBlock) => console.log(newBlock))
```

##### latest

The `latest` event is emitted for every that is detected to be the latest block.
This means skipping a block if there were two created since the last polling period.
Use this event if you don't care about stale blocks.

```js
blockTracker.on('latest', (newBlock) => console.log(newBlock))
```

##### sync

The `sync` event is emitted the same as "latest" but includes the previous block.

```js
blockTracker.on('sync', ({ newBlock, oldBlock }) => console.log(newBlock, oldBlock))
```

### NOTES

Does not currently handle block reorgs.
npm package: @michael1011/secp256k1-zkp
Description: Essential methods of the secp256k1-zkp lib exported to TS/JS for handling Elements confidential transactions
Latest version: 3.2.0

[![Build Status](https://travis-ci.org/vulpemventures/secp256k1-zkp.png?branch=master)](https://travis-ci.org/vulpemventures/secp256k1-zkp)
[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)

# secp256k1-zkp

Essential methods of the secp256k1-zkp lib exported to JS for handling Elements confidential transactions

## Installation

Use the package manager yarn or npm to install secp256k1-zkp.

```bash
yarn add @vulpemventures/secp256k1-zkp

npm install @vulpemventures/secp256k1-zkp

```

## Usage

The library is exported as a function that returns a promise.

```ts
import secp256k1 from '@vulpemventures/secp256k1-zkp'

async function main() {
    const lib = await secp256k1();
    // use the library functions
}

```

## Documentation

Typedoc html page is available via:

```bash
yarn doc
```

## Development

Fetch submodules

```bash
git submodule update --init --recursive
```

Install dependencies

```bash
yarn install
```

Compile the WASM (writes ./lib/secp256k1-zkp.js file)

```bash
yarn compile
```

Build the library

```bash
yarn build
```

Run tests

```bash
yarn test
```

## Contributing

Pull requests are welcome. For major changes, please open an issue first
to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License

[MIT](https://choosealicense.com/licenses/mit/)
npm package: @michael44/seo-review-plugin
Description: SEO Review Plugin for Builder.io
Author: Michael Dixon
Latest version: 0.0.3

# Builder.io SEO Review Plugin

Plugin for extracting and processing html content of iframed preview areas within Builder.io

The plugin sends the extracted iframe content, sends it to the SEO Review Tools API (https://api.seoreviewtools.com/) for real-time analysis based on the users' keyword input.

The plugin then displays all of the data in a modal with organized data.

## Installation

- clone this repo
- `cd plugins/example-seo-review`
- `npm install`
- `npm run start`

Now the plugin will be running on `http://localhost:1268/plugin.system.js`

- Go to your Builder account settings, and add the local plugin to your list of plugins:

```
http://localhost:1268/plugin.system.js?pluginId=@builder.io/plugin-example-seo-review
```

\*\*\* Notice the pluginId param in the path above, it's necessary to save the plugin settings.
npm package: @michael_ting/node-red-bing
Description: A Node-RED node to perform Bing searches
Author: Michael Ting
Latest version: 1.0.0

# Node-RED Bing Node

This Node-RED node allows you to perform searches using the Bing Search API.

## Installation

Run the following command in your Node-RED user directory (typically `~/.node-red`):

```bash
npm install @michael_ting/node-red-bing
```
# Usage
Drag the Bing node into your flow.
Configure the node with your Bing API subscription key and custom config ID.
Pass the search query in msg.payload.
The search results will be returned in msg.payload.
# Configuration
Subscription Key: Your Bing API subscription key.
Custom Config ID: Your custom configuration ID for the Bing search.
# Input
msg.payload: The search query string.
# Output
msg.payload: The search results object.
npm package: @michael_ting/node-red-milvus
Description: Node-RED nodes to interact with Milvus database.
Author: Michael Ting
Latest version: 1.0.0

# Node-RED Milvus Nodes

This package provides Node-RED nodes to interact with a Milvus database. The nodes allow you to perform various operations on Milvus collections, vectors, partitions, databases, and authentication.

## Nodes

### Milvus Config
This configuration node allows you to set up the connection to a Milvus database.

### Vector Node
This node allows you to perform vector operations on a Milvus database collection.

#### Supported Methods
- `delete`
- `get`
- `insert`
- `query`
- `search`
- `upsert`

### Collection Node
This node allows you to interact with a Milvus database collection.

#### Supported Methods
- `alterAlias`
- `createAlias`
- `createCollection`
- `describeAlias`
- `describeCollection`
- `dropAlias`
- `dropCollection`
- `getCollectionStatistics`
- `hasCollection`
- `listAliases`
- `listCollections`
- `renameCollection`

### Database Node
This node allows you to manage Milvus databases.

#### Supported Methods
- `createDatabase`
- `dropDatabase`
- `listDatabases`
- `useDatabase`

### Management Node
This node allows you to manage Milvus database collections and indexes.

#### Supported Methods
- `createIndex`
- `describeIndex`
- `dropIndex`
- `getLoadState`
- `loadCollection`
- `releaseCollection`

### Authentication Node
This node allows you to manage Milvus database authentication, including roles and users.

#### Supported Methods
- `createRole`
- `createUser`
- `deleteUser`
- `describeRole`
- `describeUser`
- `dropRole`
- `grantPrivilege`
- `grantRole`
- `listGrants`
- `listRoles`
- `listUsers`
- `revokePrivilege`
- `revokeRole`
- `updatePassword`

### Partitions Node
This node allows you to manage Milvus database partitions.

#### Supported Methods
- `createPartition`
- `dropPartition`
- `getPartitionStatistics`
- `hasPartition`
- `listPartitions`
- `loadPartitions`
- `releasePartitions`

## Installation

To install this package, run the following command in your Node-RED user directory (typically `~/.node-red`):

```sh
npm install @michael_ting/node-red-milvus
```

## Usage
1. Drag the desired Milvus nodes from the palette into your flow.
2. Configure the Milvus Config node with the connection details of your Milvus instance.
3. Connect the nodes as needed and deploy your flow.

## Example
Here is an example of how to use the Vector node to insert data into a Milvus collection:

1. Drag a Vector node into your flow.
2. Configure the Vector node with the collection name and method (insert).
3. Connect an Inject node to the Vector node to provide the data to be inserted.
4. Deploy the flow and trigger the Inject node to insert the data.

## Milvus Node API Reference
For detailed information on the Milvus Node API, please refer to the Milvus Node API Reference.

## License
This project is licensed under the MIT License.
npm package: @michael_ting/node-red-mp4-to-mp3
Description: A Node-RED node to convert MP4 video files to MP3 audio files.
Author: Michael Ting
Latest version: 1.0.1

# Node-RED MP4 to MP3 Node

This Node-RED node converts an MP4 video file to an MP3 audio file.

## Installation

Run the following command in your Node-RED user directory (typically `~/.node-red`):

```sh
npm install @michael_ting/node-red-mp4-to-mp3
```

## Usage
1. Drag the mp4-to-mp3 node into your flow.
2. Configure the node with the path to the MP4 file, the output directory, and the output file name.
3. Deploy the flow.
4. Inject a message to trigger the conversion.
## Node Properties
- Video Path: Path to the MP4 file.
- Output Directory: Directory to save the MP3 file.
- Output File Name: Name of the output MP3 file.
- 
## Example
Here is an example of how to use the node:
```json
[
    {
        "id": "n1",
        "type": "inject",
        "name": "",
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "x": 150,
        "y": 100,
        "wires": [["n2"]]
    },
    {
        "id": "n2",
        "type": "mp4-to-mp3",
        "name": "",
        "videoPath": "/path/to/video.mp4",
        "outputDir": "/path/to/output",
        "outputFileName": "output.mp3",
        "x": 350,
        "y": 100,
        "wires": [["n3"]]
    },
    {
        "id": "n3",
        "type": "debug",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "payload",
        "x": 550,
        "y": 100,
        "wires": []
    }
]

```