open-index/open-npm huggingface dataset:
npm package: @ryaninvents/new
Description: Yeoman generators, set up the way I like
Latest version: 1.7.1

# @ryaninvents/new

> Yeoman generators, set up the way I like

[![CircleCI][circleci-image]][circleci-url]
[![GitHub repository][github-image]][github-url]
[![semantic-release][semantic-release-image]][semantic-release-url]
![Maintenance status as of 2019][maint-image]

[semantic-release-image]: https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg

[semantic-release-url]: https://github.com/semantic-release/semantic-release

[maint-image]: https://img.shields.io/maintenance/yes/2019.svg

[github-image]: https://img.shields.io/github/stars/ryaninvents/generator-new.svg?style=social

[github-url]: https://github.com/ryaninvents/generator-new

[circleci-image]: https://img.shields.io/circleci/project/github/ryaninvents/generator-new/master.svg?logo=circleci

[circleci-url]: https://circleci.com/gh/ryaninvents/generator-new
npm package: @ryaninvents/prosemirror-doc-tpl
Description: Create Prosemirror documents using JSX-like syntax
Latest version: 1.0.1

# @ryaninvents/prosemirror-doc-tpl

> Create [Prosemirror](pm) documents using JSX-like syntax

[![CircleCI][circleci-image]][circleci-url]
[![GitHub repository][github-image]][github-url]
[![semantic-release][semantic-release-image]][semantic-release-url]
![Maintenance status as of 2019][maint-image]

## Why do I want to use this?

This package provides a concise way to create [Prosemirror](pm) documents using a JSX-like syntax, for testing or content generation.

## Installation

```bash
npm install --save @ryaninvents/prosemirror-doc-tpl
```

## Usage

This package uses your schema to generate nodes. Create the template tag with `createBuilder`, then use the tag
to generate ProseMirror documents.

```js
import createBuilder from '@ryaninvents/prosemirror-doc-tpl';
import mySchema from './schema';

const pm = createBuilder(mySchema);

const starterDocument = pm`
<doc>
  <heading level=1>prosemirror-doc-tpl</heading>
  <blockquote>
    Create <link href="https://prosemirror.net" title="ProseMirror">ProseMirror</link>
    documents using JSX-like syntax
  </blockquote>
  <paragraph>
    This package provides a concise way to create Prosemirror documents using
    a JSX-like syntax, for testing or content generation.
  </paragraph>
</doc>
`;

```

[pm]: https://prosemirror.net

[semantic-release-image]: https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg

[semantic-release-url]: https://github.com/semantic-release/semantic-release

[maint-image]: https://img.shields.io/maintenance/yes/2019.svg

[github-image]: https://img.shields.io/github/stars/ryaninvents/prosemirror-doc-tpl.svg?style=social

[github-url]: https://github.com/ryaninvents/prosemirror-doc-tpl

[circleci-image]: https://img.shields.io/circleci/project/github/ryaninvents/prosemirror-doc-tpl/master.svg?logo=circleci

[circleci-url]: https://circleci.com/gh/ryaninvents/prosemirror-doc-tpl
npm package: @ryanjerskine/homebridge-motionblinds
Description: Homebridge plugin to control MOTION Blinds by Coulisse B.V. including derivative products such as OmniaBlinds.
Latest version: 2.0.7

# homebridge-motionblinds

[![npm](https://badgen.net/npm/v/homebridge-motionblinds)](https://www.npmjs.com/package/homebridge-motionblinds)
[![npm](https://badgen.net/npm/dt/homebridge-motionblinds)](https://www.npmjs.com/package/homebridge-motionblinds)

Homebridge plugin to control MOTION Blinds by Coulisse B.V. including derivative products such as OmniaBlinds.

## Installation
1. Follow the step-by-step instructions on the [Homebridge Wiki](https://github.com/homebridge/homebridge/wiki) for how to install Homebridge.
2. Follow the step-by-step instructions on the [Homebridge Config UI X](https://github.com/oznu/homebridge-config-ui-x/wiki) for how to install Homebridge Config UI X.
3. Install homebridge-motionblinds using: `npm install -g homebridge-motionblinds` or search for `MOTION Blinds` in Config UI X.

## Info
1. Blinds are only identified by a 16-character MAC address. They will show up in HomeKit with the MAC address as their name. You can rename them in HomeKit or using the configuration options below.
2. If your blinds support tilt angle control, you must manually enable it using the "tilt" config option described below.
3. If your blind is moving up when it should move down, or left when it should move right, use the "invert" config option described below.

## Configuration

All fields are optional except `"platform"`, and `"mac"` if any blinds are specified. If no `"key"` is given, blinds will appear as read only with no control. If you are having connectivity issues, try specifying the `"gatewayIp"`.

```json
{
  "platform": "MotionBlinds",
  "key": "xxxxxxxx-xxxx-xx",
  "gatewayIp": "10.0.0.23",
  "blinds": [
    {
      "mac": "xxxxxxxxxxxxxxxx",
      "name": "Bedroom Blinds",
      "tilt": true,
      "invert": false
    },
    {
      "mac": "xxxxxxxxxxxxxxxx",
      "name": "Living Room Roller Shade",
      "tilt": false,
      "invert": false
    }
  ]
}
```
npm package: @ryanjoserbrosas/ultradev
Description: The Unified OpenCode Engine — Bootstrap and Runtime in One CLI
Author: Ryan Jose Brosas
Latest version: 1.1.2

# Ultra

Ultra is the unified OpenCode product. It combines bootstrap and runtime orchestration into a single CLI and package.

## Install

```bash
npm install -g @ryanjoserbrosas/ultradev
# or
bunx @ryanjoserbrosas/ultradev --help
```

## Quick start

```bash
ultra init
ultra run "Fix the bug in index.ts"
ultra doctor
```

## Configuration

Ultra reads JSONC config from:

- User: `~/.config/ultra/ultra.jsonc`
- Project: `.opencode/ultra.jsonc`

See [docs/CONFIG.md](docs/CONFIG.md) for schema and merge rules.

## CLI reference

See [docs/CLI.md](docs/CLI.md).

## Migration

See [docs/MIGRATION.md](docs/MIGRATION.md) for upgrading from legacy installs.
npm package: @ryanjoy/vitepress-plugin-sidebar
Description: A vitepress plugin to generate sidebar for your site.
Author: RyanJoy
Latest version: 1.0.2

# `@ryanjoy/vitepress-plugin-sidebar`

A vitepress plugin to generate sidebar for your site.

## Install

### Npm

```shell
npm i @ryanjoy/vitepress-plugin-sidebar -D
```

### Yarn

```shell
yarn add @ryanjoy/vitepress-plugin-sidebar -D
```

### Pnpm

```shell
pnpm add @ryanjoy/vitepress-plugin-sidebar -D
```
npm package: @ryanke/eslint-config
Description: An eslint config I share between projects.
Author: Ryan
Latest version: 1.0.3

# eslint-config

> A [shareable config](https://eslint.org/docs/developer-guide/shareable-configs) for [ESLint](https://eslint.org/). 

I never liked existing configs, they always have rules that I find unnecessary causing each project to end up with a dozen rules being disabled because they end up getting in the way. This config aims to fix that, for me anyway. I'm sure other people will find issues with what I've chosen, but eventually this config will be the default for all my projects without each project having a a separate config with a dozen plugins and a dozen more rules disabled.

TypeScript and React support is included. React-specific rules are only enabled for files ending with `jsx` or `tsx` because I'm concerned about performance and realistically the only thing without those extensions *might* be hooks.

# usage

> For NextJS projects, use the [official NextJS config](https://github.com/vercel/next.js/tree/canary/examples/with-eslint).

- `pnpm add --save-dev eslint @ryanke/eslint-config eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-unicorn @typescript-eslint/eslint-plugin`
- Create a `.eslintrc` file with the content below

```jsonc
{
    "extends": "@ryanke",
    "parserOptions": {
        "project": "./tsconfig.json"
    }
}
```

I intend on some rules being disabled depending on the project. In particular, `@typescript-eslint/explicit-function-return-type` will cause issues for some projects. For libraries I'd keep this on, but otherwise you will probably want to turn it off once it gets annoying.

# assumptions

- React projects will always be TypeScript.
- React hooks will be `.tsx` files.

# todo

- [ ] Benchmark linter performance and remove unnecessary or expensive rules
npm package: @ryanke/pandora
Description: A collection of components and hooks I find myself needing in a lot of projects.
Author: Ryan
Latest version: 0.0.9

# pandora

A collection of components and hooks I find myself needing in a lot of projects.

## components

- [x] Toasts
- [x] Button
- [x] Breadcrumbs
- [x] Card
- [ ] Select
- [ ] Input
- [x] Spinner
- [x] Container
- [ ] Center
- [ ] Pagination?
- [ ] Navigation?
- [ ] Layout?

## hooks

- [x] useOnClickOutside
- [x] useAsync
npm package: @ryanke/violet
Description: > [!IMPORTANT] > This is absolutely not ready for production - a lot of features are missing, incomplete, or untested.
Latest version: 0.0.2

# violet

> [!IMPORTANT]
> This is absolutely not ready for production - a lot of features are missing, incomplete, or untested.

Bundle your TypeScript app or library with ease.

- Reduce the size of Docker builds
- Support [macros](#macros) for compile-time code generation
- Make sure you forget you're using ESM
- Handle bundling optional dependencies properly

## installation

```bash
# only pnpm is supported for now. violet needs to read the lockfile
pnpm add @ryanke/violet
```

For improved compatibility, you may also update your `tsconfig.json` to extend the included preset, it may fix some issues that either slow down or break bundling in some circumstances.

```json
{
  "extends": "@ryanke/violet/tsconfig-base.json",
  // or...
  "extends": ["...", "@ryanke/violet/tsconfig-base.json"]
}
```

Then, to run and build your app, you can add this to your package.json

```json
{
  "scripts": {
    "build": "tsc --noEmit && violet build ./src/index.ts",
    "dev": "violet run --watch ./src/index.ts",
    "start": "node ./dist/index.js"
  }
}
```

## usage

```bash
# run an app, similar to `tsx` or `ts-node`
# this builds your app in the background and runs it on success
violet run ./src/index.ts --args-to-pass
violet run --watch ./src/main.ts
# build your app
# automatically bundles app dependencies except those in package.json "dependencies"
# "devDependencies" are always bundled - if you want to bundle everything, move everything to "devDependencies"
violet build ./src/index.ts
# there are a few additional options, run `violet --help` for more info
```

## macros

> [!IMPORTANT]
> Because of unfortunate limitations with esbuild and swc, macros do not work in files that require decorator metadata. This may be fixed in the future.

Macros are functions that run at compile time.
Unlike rust, you cannot _generate_ code with macros (yet..!), but they can still be extremely powerful in the right circumstances.

```ts
// helpers.ts
import { execSync } from "child_process";

export const getCommitHash = async () => {
  return execSync("git rev-parse HEAD").toString().trim();
};
```

```ts
// index.ts
import { getCommitHash } from "./helpers.js" assert { type: "macro" };

const commitHash = await getCommitHash();
```

This will compile to:

```js
const commitHash = "7fe6d2c105dec483c85355976d6f4307c78e66bc";
```
npm package: @ryanknutson/rkgis
Description: a fast no-api Google Images search
Author: Ryan D. Knutson
Latest version: 1.1.4

# rkgis
### a fast no-api Google Images search

## Installation

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

```bash
npm i imagemagick
```

## Usage

Include with
```javascript
const rkgis = require('rkgis')
```

rkgis returns a promise, which you can use as follows
```javascript
rkgis('cats').then(e=>console.log(e))
```

there are currently 2 options available, random, and max
```javascript
rkgis('cats', {random: true, max: 5})
```
random will shuffle the array, and max will limit the number of results


## License
[MIT](https://choosealicense.com/licenses/mit/)
npm package: @ryanlee2014/markdown-it
Description: markdown-it browser build
Author: Ryan Lee
Latest version: 1.0.2

# Markdown-It-Browser-Library

Make for [CUP Online Judge](http://acm.cup.edu.cn)

## Usage
**Browser:**

```html
<script src="/markdown-it.js"></script>

<!-- some code -->
<script>
markdownIt.render(`# Hello MarkdownIt!`)
</script>
```

## Dependencies
* markdown-it
* markdown-it-katex
* markdown-it-highlightjs
* github-markdown.css

## Build

```bash
npm install
webpack
```
npm package: @ryanlee2014/vue-gravatar
Description: Gravatar component for VueJS
Author: Ryan Lee
Latest version: 1.1.1

# vue-gravatar

[![Build Status](https://travis-ci.org/JiriChara/vue-gravatar.svg?branch=master)](https://travis-ci.org/JiriChara/vue-gravatar)
[![NPM Version](https://img.shields.io/npm/v/vue-gravatar.svg)](https://www.npmjs.com/package/vue-gravatar)
[![NPM Dowloads](https://img.shields.io/npm/dm/vue-gravatar.svg)](https://www.npmjs.com/package/vue-gravatar)

A dead-simple gravatar component for VueJS applications.

**[DEMO](https://jirichara.github.io/vue-gravatar/)**


## Installation

```
yarn add vue-gravatar
```

## Usage

Register the component

```js
import Vue from 'vue';
import Gravatar from 'vue-gravatar';

Vue.component('v-gravatar', Gravatar);
```

You may now use the component in your markup

```vue
<v-gravatar email="somebody@somewhere.com" />
```

### Props

The following props are available:

* **hash** (type: String) md5 hash of the gravatar
* **email** (type: String) email address of the gravatar (used when md5 hash not given)
* **size** (type: Number, default: 80) size of the avatar
* **default-img** (type: String, default: 'retro') default image type (see. http://en.gravatar.com/site/implement/images/)
* **rating** (type: String, default: 'g') rating of the image (see. http://en.gravatar.com/site/implement/images/)
* **alt** (type: String, default: 'Avatar') The alternative text of the image

#### Example

```vue
<v-gravatar hash="f3ada405ce890b6f8204094deb12d8a8" alt="Nobody" :size="200" default-img="mm" />
```

## License

The MIT License (MIT) - See file 'LICENSE' in this project

## Copyright

Copyright © 2017 Jiří Chára. All Rights Reserved.