open-index/open-npm huggingface dataset:
npm package: @mersenneab/builder-plugin-search-input
Description: > Search input plugin for [Builder](https://builder.io)
Latest version: 1.0.0

# builder-plugin-search-input

> Search input plugin for [Builder](https://builder.io)


## Usage

```js
withBuilder(Component, {
	name: 'Component',
	inputs: [
		{
			name: 'data',
			type: 'search-input',
			options: {
				url: 'https://unicorn.com/search?query={{value}}',
				wait: 500,
				mapper: `result => result.map(data => {
					return {
						label: data.name,
						value: data
					};
				})`
			}
		},
		{…}
	]
});
```
npm package: @mershjs/mersh
Description: 基于 vue3 + typescript + vite 的 webUI 组件库
Author: fengwang
Latest version: 0.0.5

# Vue 3 + TypeScript + Vite

This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 `<script setup>` SFCs, check out the [script setup docs](https://v3.vuejs.org/api/sfc-script-setup.html#sfc-script-setup) to learn more.

## Recommended IDE Setup

- [VS Code](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).

## Type Support For `.vue` Imports in TS

TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to make the TypeScript language service aware of `.vue` types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a [Take Over Mode](https://github.com/johnsoncodehk/volar/discussions/471#discussioncomment-1361669) that is more performant. You can enable it by the following steps:

1. Disable the built-in TypeScript Extension
   1. Run `Extensions: Show Built-in Extensions` from VSCode's command palette
   2. Find `TypeScript and JavaScript Language Features`, right click and select `Disable (Workspace)`
2. Reload the VSCode window by running `Developer: Reload Window` from the command palette.
npm package: @mershjs/theme
Description: 基于VitePress的reco主题
Author: fengwang
Latest version: 0.0.4

# Vue 3 + TypeScript + Vite

This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 `<script setup>` SFCs, check out the [script setup docs](https://v3.vuejs.org/api/sfc-script-setup.html#sfc-script-setup) to learn more.

## Recommended IDE Setup

- [VS Code](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).

## Type Support For `.vue` Imports in TS

TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to make the TypeScript language service aware of `.vue` types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a [Take Over Mode](https://github.com/johnsoncodehk/volar/discussions/471#discussioncomment-1361669) that is more performant. You can enable it by the following steps:

1. Disable the built-in TypeScript Extension
   1. Run `Extensions: Show Built-in Extensions` from VSCode's command palette
   2. Find `TypeScript and JavaScript Language Features`, right click and select `Disable (Workspace)`
2. Reload the VSCode window by running `Developer: Reload Window` from the command palette.
npm package: @mersocarlin/api-error
Description: Named API errors with original status code and custom message.
Author: Hemerson Carlin
Latest version: 0.0.2

# @mersocarlin/api-error

Named API errors with original status code and custom message.

## Install

```bash
yarn add @mersocarlin/api-error
```

```bash
npm i @mersocarlin/api-error
```

## Errors included

- BadGateway
- BadRequest
- Conflict
- Forbidden
- GatewayTimeout
- InternalServerError
- MethodNotAllowed
- NotFound
- PaymentRequired
- RequestTimeout
- TooManyRequests
- Unauthorized

## Usage

```ts
import { ApiError, UnauthorizedError } from '@mersocarlin/api-error'


function login(credentials) {
  try {
    await doLogin(credentials)
  } catch (error) {
    throw new UnauthorizedError('Invalid credentials', error)
  }
}

function otherOperation() {
  try {
    ...
  } catch (error) {
    throw new ApiError('Something went wrong', 500, error)
  }
}

```

## API

### `ApiError`

| Prop          | Type   | Default  | Description                                               |
| ------------- | ------ | -------- | --------------------------------------------------------- |
| message       | String | ApiError | Message that describes the type of error                  |
| statusCode    | Number | 500      | Status code                                               |
| originalError | Object |          | Original error thrown (from try/catch, promise reject...) |

### `BadGatewayError`

| Prop          | Type   | Default     | Description                                               |
| ------------- | ------ | --------    | --------------------------------------------------------- |
| message       | String | Bad Gateway | Message that describes the type of error                  |
| error         | Object |             | Original error thrown (from try/catch, promise reject...) |

**Note**: Same applies for all other error types.
npm package: @mersocarlin/fetch
Description: `fetch` wrapper on top of `isomorphic-fetch`.
Author: Hemerson Carlin
Latest version: 0.0.5

# @mersocarlin/fetch

`fetch` wrapper on top of `isomorphic-fetch`.

## Motivation

I needed a consistent `fetch` wrapper that always returns the same structure (`body` and `statusCode`) for all API calls throughout my projects.

Basic error handling was also a "_must-have_" and I ended up duplicating the same code in every new project/repository I was working on.

I've also written this code a long time ago but never had the chance to give it the attention it deservs + open source it.

It works seamless with [@mersocarlin/mersocarlin/api-error](https://github.com/mersocarlin/api-error) so I get named API errors for free.

## Install

```bash
yarn add @mersocarlin/fetch
```

```bash
npm i @mersocarlin/fetch
```

## Usage

```ts
import fetch from '@mersocarlin/fetch'

const login = async (username: string, password: string) => {
  try {
    const { body, statusCode } = await fetch('https://example.com/api/signin', {
      body: {
        username,
        password,
      },
      method: 'post',
    })

    return body
  } catch(error) {
    throw error
  }
}

const fetchPrivateUsers = async () => {
  try {
    const { body, statusCode } = await fetch('https://example.com/api/users', {
      headers: {
        'Authorization': 'Bearer TOKEN',
      }
    })

    return body
  } catch(error) {
    throw error
  }
}

const fetchPublicUsers = async () => {
  try {
    const { body, statusCode } = await fetch('https://example.com/users')

    return body
  } catch(error) {
    throw error
  }
}
```
npm package: @mert.alptekin/auto-focus
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.3.0.
Author: mert.alptekin
Latest version: 1.0.0

# AutoFocus

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.3.0.

## Code scaffolding

Run `ng generate component component-name --project auto-focus` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project auto-focus`.
> Note: Don't forget to add `--project auto-focus` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build auto-focus` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build auto-focus`, go to the dist folder `cd dist/auto-focus` and run `npm publish`.

## Running unit tests

Run `ng test auto-focus` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.