open-index/open-npm huggingface dataset:
npm package: @lsmoura/danger-plugin-eslint
Description: ESLint plugin for danger
Author: Sergio Moura
Latest version: 0.0.1

# danger-plugin-eslint

It grabs the generated json by eslint and publishes the reports.

## Usage

Install this Danger plugin:

```
yarn add --dev @lsmoura/danger-plugin-jest
```

By default, this package will assume you've set the filename as `eslint-result.json`, but you can use any path.

Add a step on your github action script to generate the linting output file:

```
  - name: linting
    continue-on-error: true
    run: yarn lint --output-file eslint-result.json --format json --no-color
```

You can check [danger.yml](blob/master/.github/workflows/danger.yml) for details.

# Author

Sergio Moura <[https://sergio.moura.ca](https://sergio.moura.ca)>
npm package: @lsmoura/danger-plugin-typecheck
Description: Typecheck plugin for danger using typescript
Author: Sergio Moura
Latest version: 0.0.3

# danger-plugin-typecheck

Uses typescript's `tsc` command output to present errors
using [danger](https://danger.system).

## Usage

Import and call the function from your _Dangerfile_;

```
import typecheck from '@lsmoura/danger-plugin-typecheck';

typecheck('tsc_raw.log');
```

The script needs to have the `tsc` command output available to parse.
You can use this script on your `package.json` file to produce the output:

```
"ci:type-check": "tsc --pretty false | tee tsc_raw.log"
```

And you can include this step on your danger CI integration (this example
is for when using github actions, but it can be easily adapted to others):

```
  - name: typechecking
    continue-on-error: true
    run: yarn ci:type-check
```

Remember, the typechecking action needs to be ran before the `danger ci` 
command.

# Author

[Sergio Moura](https://sergio.moura.ca)
npm package: @lsnsh/weui-vue
Description: A Vue.js component library based on WeUI.
Latest version: 0.1.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

## WeUI-Vue

> 当前 `WeUI` 版本：[v2.4.0](https://github.com/Tencent/weui/releases/tag/v2.4.0)

WeUI-Vue 是基于 [WeUI](https://github.com/Tencent/weui) 封装的第三方 `Vue` `组件库，WeUI` 是一套同微信原生视觉体验一致的基础样式库，由微信官方设计团队为微信内网页和微信小程序量身设计，令用户的使用感知更加统一。

## 安装

```shell
npm install @lsnsh/weui-vue -S
```

## 快速开始

```javascript
import Vue from "vue";
import WeUIVue from "@lsnsh/weui-vue";

Vue.use(WeUIVue);
```

[查看示例代码](./examples/App.vue)

## 更新日志

[github releases](https://github.com/Lsnsh/weui-vue/releases)中记录了每个发布版本的详细更改。

## 许可证

[MIT](LICENSE)
npm package: @lsolova/monobuild
Description: Monorepository building tool
Author: Laszlo Solova
Latest version: 0.0.5

# Monobuild

A simple monorepository building tool.

## Prerequisites

1. Define two scripts in every package.json, with _build_ and _serve_ property names. (The property value is just an
   example.)

   ```json
   "scripts": {
     "build": "vite build",
     "serve": "vite build --watch"
   }
   ```

## Usage

### Function

```ts
import { BuildModeSet, build } from "@lsolova/monobuild";

build({
  mode: BuildModeSet.BUILD,
  verbose: true
}).catch(console.error);
```

### CLI
npm package: @lsongzhi/openapi-typescript-codegen
Description: NodeJS library that generates Typescript or Javascript clients based on the OpenAPI specification.
Author: Ferdi Koomen
Latest version: 0.1.20

# OpenAPI Typescript Codegen

[![NPM](https://badgen.net/npm/v/openapi-typescript-codegen)](https://www.npmjs.com/package/openapi-typescript-codegen)
[![License](https://badgen.net/npm/license/openapi-typescript-codegen)](https://www.npmjs.com/package/openapi-typescript-codegen)
[![Build Status](https://badgen.net/travis/ferdikoomen/openapi-typescript-codegen/master)](https://travis-ci.org/ferdikoomen/openapi-typescript-codegen)
[![Codecov](https://codecov.io/gh/ferdikoomen/openapi-typescript-codegen/branch/master/graph/badge.svg)](https://codecov.io/gh/ferdikoomen/openapi-typescript-codegen)
[![Quality](https://badgen.net/lgtm/grade/javascript/g/ferdikoomen/openapi-typescript-codegen)](https://lgtm.com/projects/g/ferdikoomen/openapi-typescript-codegen)

> NodeJS library that generates Typescript clients based on the OpenAPI specification.

## This is a fork of openapi-typescript-codegen with some bugfixes and customizations:
* support `x-enum-varnames: string[]` and `x-enum-descriptions` in schema to generate enums with names and descriptions in the field.
* changed service parameters style

#### Why?
- Frontend ❤️ OpenAPI, but we do not want to use JAVA codegen in our builds.
- Quick, lightweight, robust and framework agnostic.
- Supports generation of Typescript clients.
- Supports generations of fetch and XHR http clients.
- Supports OpenAPI specification v2.0 and v3.0.
- Supports JSON and YAML files for input.


## Known issues:
- If you use enums inside your models / definitions then those enums are now
  inside a namespace with the same name as your model. This is called declaration
  merging. However Babel 7 now support compiling of Typescript and right now they
  do not support namespaces.


## Installation

```
npm install @lsongzhi/openapi-typescript-codegen --save-dev
```

## Example

**package.json**
```json
{
    "scripts": {
        "generate": "openapi --input ./api/openapi.json --output ./dist"
    }
    ...
}
```

Command line

```
npm install openapi-typescript-codegen -g

openapi ./api/openapi.json ./dist
```

NodeJS API:

```
const OpenAPI = require('openapi-typescript-codegen');

OpenAPI.generate(
    './api/openapi.json',
    './dist'
);
```
npm package: @lspeasy/middleware-pino
Description: Pino-based structured logging middleware for lspeasy
Author: Pradeep Mouli
Latest version: 4.0.0

# @lspeasy/middleware-pino

Pino-compatible structured logging middleware for lspeasy middleware pipelines.

## Installation

```bash
pnpm add @lspeasy/middleware-pino pino
```

## Usage

```typescript
import pino from 'pino';
import { LSPClient } from '@lspeasy/client';
import { createPinoMiddleware } from '@lspeasy/middleware-pino';

const logger = pino({ level: 'info' });

const client = new LSPClient({
	name: 'logging-client',
	version: '1.0.0',
	middleware: [
		createPinoMiddleware(logger, {
			level: 'debug',
			includeMessageContent: false,
			staticFields: {
				service: 'lsp-client'
			}
		})
	]
});
```

## Options

- `level`: logging level (`trace`, `debug`, `info`, `warn`, `error`, `fatal`)
- `includeMessageContent`: include full JSON-RPC message payload in log records
- `staticFields`: fixed metadata included in every log record
- `formatMessage`: custom formatter for emitted log messages

## Behavior

- Emits a `before` log event prior to the next middleware/handler.
- Emits an `after` log event on successful completion with `durationMs`.
- Emits an `error` log event when downstream middleware/handler throws.
npm package: @lspellman/mcp-cursor-tools
Description: MCP server providing enhanced tools for Cursor IDE
Author: Lance Spellman
Latest version: 0.1.0

# MCP Cursor Tools

An MCP server providing enhanced tools for the Cursor IDE.

## Installation

You can install this package globally using npm:

```bash
npm install -g @lancespellman/mcp-cursor-tools
```

## Configuration in Cursor

1. Open or create your Cursor MCP configuration file at `~/.cursor/mcp.json`
2. Add the following configuration (preserve any existing configuration):

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

3. Restart Cursor to load the new MCP configuration

## Available Tools

### ping

A simple tool to verify the server is working correctly.

Parameters:
- `message` (optional): A message to send to the server

Example usage:
1. Open Cursor's command palette
2. Run the command "MCP: Test Tool"
3. Select "mcp-cursor-tools" and the "ping" tool
4. Optionally provide a message
5. Check the response ("Pong!")

## Development

1. Clone the repository
2. Install dependencies:
   ```bash
   npm install
   ```
3. Start the server:
   ```bash
   npm start
   ```

## Debugging

The server writes logs to `~/mcp-debug.log`. You can monitor these logs while developing or troubleshooting:

```bash
tail -f ~/mcp-debug.log
```

## License

MIT