open-index/open-npm huggingface dataset:
npm package: @linsight/react-scripts
Description: Customised configuration and scripts for Create React App with support for multiple entry points.
Latest version: 3.4.4

# @linsight/react-scripts

Customised react-scripts to support mutiple entry points.

## Usage

1. Update your `package.json` file to replace dependency `react-scripts` into:

	```
	"dependencies": {
	    "@linsight/react-scripts": "~3.4.3",
	    ...
    }
	
	```
	

2. Create a `.env` to your project root if you don't have one. Add to the `.env` file your entry points. Example:

	```
	ENTRY_POINT_INDEX="index"
	ENTRY_POINT_ADMIN="admin"
	```

3. If your new entry point needs a HTML file (HtmlWebpackPlugin), you can simply add a HTML file named after the entry point in the public directory. e.g. `admin.html`.

4. You can also nest an `index.html` a subdirectory instead. e.g. `admin/index.html`

## Note

1. The default `index` entry point will be working as normal if no custom entry points are defined in the `.env` file.
2. However, if custom entry points are defined in the `.env` file, ONLY custom entry points will be used. This means you need to add `ENTRY_POINT_INDEX="index"` to the `.env` file if you want to keep the default `index` entry point. 


<br>

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://facebook.github.io/create-react-app/docs/getting-started) – How to create a new app.
- [User Guide](https://facebook.github.io/create-react-app/) – How to develop apps bootstrapped with Create React App.
npm package: @lint-md/ast-plugin
Description: The simplest abstract syntax tree walker.
Author: hustcc
Latest version: 1.0.1

# @lint-md/ast-plugin

> The simplest abstract syntax tree walker.

[![Build Status](https://github.com/lint-md/ast-plugin/actions/workflows/build.yml/badge.svg)](https://github.com/lint-md/ast-plugin/actions/workflows/build.yml)

## Install

> npm i --save ast-plugin

## Usage

- Traverse Ast plugins

```js
import { Ast, Plugin } from 'ast-plugin';

new Ast(ast).traverse([
  new TestPlugin(cfg),
  // ...
]);
```

- Write an ast plugin

```js
import { Ast, Plugin } from 'ast-plugin';

class TestPlugin extends Plugin {

  pre = () => {
  };

  visitor = () => {
    return {
      // process node with type = 'text'
      text: ast => {
        console.log(ast.node);
        ast.segment();
      },
    };
  };

  post = () => {
  };
}
```

## Used by

- [lint-md](https://github.com/lint-md/lint-md) Cli tool to lint your markdown file for Chinese.

## License

MIT@[hustcc](https://github.com/hustcc).
npm package: @lint-md/cli
Description: CLI tool to lint your markdown file for Chinese.
Author: hustcc
Latest version: 2.0.0

# @lint-md/cli

Lint Markdown 是检查中文 Markdown 编写格式的工具，让你的文档更加优雅规范。

请参阅 [Lint Markdown 主仓库文档](https://github.com/lint-md/lint-md#%E4%BD%BF%E7%94%A8%E5%91%BD%E4%BB%A4%E8%A1%8Ccli)
npm package: @lint-md/eslint-plugin
Description: :sunglasses: 基于 @lint-md，提供 eslint-plugin，让 lint-md 玩家得到愉悦的文档编写体验。
Author: yuzhanglong
Latest version: 0.1.0

# @lint-md/eslint-plugin

:sunglasses: 基于 @lint-md，提供 eslint-plugin，让 lint-md 玩家得到愉悦的文档编写体验。

![](http://cdn.yuzzl.top/blog/20210309172714.png)

## 安装

```shell
# use npm
npm install eslint @lint-md/eslint-plugin

# use yarn
yarn add eslint @lint-md/eslint-plugin
```

## 使用

为你的 `.eslintrc.js`
追加以下配置，关于规则的详细信息请参考 [lint-md](https://github.com/lint-md/lint-md#%E6%A3%80%E6%9F%A5%E7%B1%BB%E5%9E%8B)

```javascript
module.exports = {
  extends: ['plugin:@lint-md/recommend'],
  overrides: [
    {
      files: ['*.md'],
      // 0.0.x 版本为 '@lint-md/eslint-plugin/src/parser'
      parser: '@lint-md/eslint-plugin/lib/parser',
      rules: {
        // 在这里覆盖已有的 rules
        '@lint-md/no-long-code': [2, {
          "length": 100,
          "exclude": []
        }]
      }
    }
  ],
}
```

执行下面的命令尝试 lint，具体参数请根据项目实际情况进行调整：

```shell
eslint --ext .md ./
```

效果如下：

![](http://cdn.yuzzl.top/blog/20210309114543.png)

## IDE 支持

### 在 vscode 中使用

#### 安装 eslint 插件

在 vscode 插件商店中搜索 `eslint`，安装之：

![](http://cdn.yuzzl.top/blog/20210309102904.png)

#### 追加配置

- 在项目根目录下新建 `.vscode` 目录，然后新建 `settings.json` 文件（如果已有，忽略此步骤）
- 追加如下配置，让 eslint 插件审查 markdown 文件：

```json
{
  "eslint.validate": [
    "markdown"
  ]
}
```

![](http://cdn.yuzzl.top/blog/20210309103150.png)

#### 查看效果

最终效果如图所示：

![](http://cdn.yuzzl.top/blog/20210309103609.png)

### 在 webstorm 中使用

#### 设置 .md 后缀支持

- 进入 `file > settings > languages & frameworks > JavaScript > Code Quality Tools > ESLint` 设置项
- 在 `Run for files` 一栏中添加 `.md` 后缀。
- 点击 ok 保存设置

![](http://cdn.yuzzl.top/blog/20210309104303.png)

#### 查看效果

最终效果如图所示：

![](http://cdn.yuzzl.top/blog/20210309104035.png)

> TIP: webstorm 2021.1 及以上版本的 eslint 插件支持自定义检测文件后缀名，目前为 beta 版本，相信不久就会 release 了。
> 欲了解详细信息，请参阅[这里](https://blog.jetbrains.com/webstorm/2021/02/webstorm-2021-1-eap-5/)

## 其它案例

更多案例及配置文件请移步仓库 `examples` 目录。
npm package: @lint-md/parser
Description: lint-md 的解析器，基于 remark 生态，将 Markdown 字符串转换成 AST
Author: yuzhanglong
Latest version: 0.0.14

# @lint-md/parser

lint-md 的解析器，基于 remark 生态，将 Markdown 字符串转换成 AST。

单独拆包封装一层的意义是当前 remark 的稳定版本只支持 ESModule，但是 lint-md 主模块依赖了很多 CommonJS 的库，故无法直接迁移到 ESModule。

故将使用 remark 的那部分代码抽离到单独模块然后用 webpack 打包成 CommonJS。


## 快速开始

```ts
import { parseMd } from '@lint-md/parser';

// 将 markdown 转换成 ast
const ast = parseMd('你的 Markdown 文本');
```

## License

MIT
npm package: @lint-todo/ember-template-lint-formatter-todo
Description: An Ember Template Lint formatter for todos
Author: Steve Calvert
Latest version: 2.0.1

# @lint-todo/ember-template-lint-formatter-todo

![CI Build](https://github.com/lint-todo/ember-template-lint-formatter-todo/workflows/CI%20Build/badge.svg)
[![npm version](https://badge.fury.io/js/%40lint-todo%2Fember-template-lint-formatter-todo.svg)](https://badge.fury.io/js/%40lint-todo%2Fember-template-lint-formatter-todo)
[![License](https://img.shields.io/npm/l/@lint-todo/ember-template-lint-formatter-todo.svg)](https://github.com/@lint-todo/ember-template-lint-formatter-todo/blob/master/package.json)
![Dependabot](https://badgen.net/badge/icon/dependabot?icon=dependabot&label)
![Volta Managed](https://img.shields.io/static/v1?label=volta&message=managed&color=yellow&logo=data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QAeQC6AMEpK7AhAAAACXBIWXMAAAsSAAALEgHS3X78AAAAB3RJTUUH5AMGFS07qAYEaAAAABl0RVh0Q29tbWVudABDcmVhdGVkIHdpdGggR0lNUFeBDhcAAAFmSURBVDjLY2CgB/g/j0H5/2wGW2xyTAQ1r2DQYOBgm8nwh+EY6TYvZtD7f9rn5e81fAGka17GYPL/esObP+dyj5Cs+edqZsv/V8o//H+z7P+XHarW+NSyoAv8WsFszyKTtoVBM5Tn7/Xys+zf7v76vYrJlPEvAwPjH0YGxp//3jGl/L8LU8+IrPnPUkY3ZomoDQwOpZwMv14zMHy8yMDwh4mB4Q8jA8OTgwz/L299wMDyx4Mp9f9NDAP+bWVwY3jGsJpB3JaDQVCEgYHlLwPDfwYWRqVQJgZmHoZ/+3PPfWP+68Mb/Pw5sqUoLni9ipuRnekrAwMjA8Ofb6K8/PKBF5nU7RX+Hize8Y2DOZTP7+kXogPy1zrH+f/vT/j/Z5nUvGcr5VhJioUf88UC/59L+/97gUgDyVH4YzqXxL8dOs/+zuFLJivd/53HseLPPHZPsjT/nsHi93cqozHZue7rLDYhUvUAADjCgneouzo/AAAAAElFTkSuQmCC&link=https://volta.sh)
[![Code Style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](#badge)

> A custom formatter for `ember-template-lint` that will display a table of todos for your project, sorted by due date.

## Install

```shell
npm i @lint-todo/ember-template-lint-formatter-todo --save-dev

# or

yarn add @lint-todo/ember-template-lint-formatter-todo --dev
```

## Usage

```shell
ember-template-lint . --format @lint-todo/ember-template-lint-formatter-todo
```

Running with the formatter will output a table of todos, ordered by due dates sorted by when they're due.

<img width="784" alt="Todo Formatter" src="static/output.png">

If you'd like to restrict the output to a specific rule ID, just pass the `--rule` option to `ember-template-lint`.

```shell
ember-template-lint . --rule "no-implicit-this:error" --format @lint-todo/ember-template-lint-formatter-todo
```
npm package: @lint-todo/migrator
Description: A migration tool for lint todos
Author: scalvert
Latest version: 1.0.3

# @lint-todo/migrator

Migration tool to migrate lint todo files from multi-file storage to single-file storage.

## Usage

```bash
  A migration tool for lint todos

  Usage
    $ npx @lint-todos/migrator <working directory>

  Options
    --removeV1, -r  Remove v1 todos from migration

  Examples
    $ npx @lint-todos/migrator .
     ✔ Successfully migrated 10 todos to single file format
```

From within the project directory, run:

```bash
npx @lint-todo/migrator .
```

The number of todos migrated will be printed to the console.

```bash
✔ Successfully migrated 10 todos to single file format
```

If the project was already migrated to the new format, the tool will print to the console indicating this.

```bash
⚠ Skipped migration (.lint-todo file found)
```

If the project does not contain either a `.lint-todo` directory or `lint-todo` file, the tool will print to the console indicating this.

```bash
⚠ Skipped migration (no .lint-todo directory found)
```

### Options

```bash
npx @lint-todo/migrator . --removeV1
```

The new single file storage format does not support Version 1 of the todo format. You can optionally remove all Version 1 todos and convert the remaining Version 2 todos to single-file format. Doing so will effectively convert the Version 1 todos back to error or warn severity, so you should only do this if you are OK with exposing those lint violations to the user.

You should ensure that all your todos are using the new format by regenerating them in Version 2 format (using `ember-template-lint@3.6.0` or later and `@scalvert/eslint-formatter-todo@1.4.0` or later).

## License

This project is licensed under the [MIT License](LICENSE).
npm package: @lint-ts-index/core
Description: Check whether TS files are exported in index.ts
Author: Baptist BENOIST
Latest version: 0.1.1

# @lint-ts-index/core

[![GitHub tag (latest SemVer)](https://img.shields.io/github/v/tag/bbenoist/lint-ts-index?label=Version&logo=git&sort=semver)](https://github.com/bbenoist/lint-ts-index/releases)
[![License](https://img.shields.io/github/license/bbenoist/lint-ts-index?label=License&logo=github)](https://raw.githubusercontent.com/bbenoist/lint-ts-index/master/LICENSE)
[![GitHub issues](https://img.shields.io/github/issues/bbenoist/lint-ts-index?label=Issues&logo=github)](https://github.com/bbenoist/lint-ts-index/issues)

Purpose of this tool is to check that every files or subdirectories are exported in their corresponding `index.ts` files.

<!-- AUTO-GENERATED-CONTENT:START (SIMPLE_EXAMPLE_FAIL_OUTPUT) -->
```txt
foo.ts is not exported in index.ts
If you believe it's an error, please add an exclusion in .indexignore
```
<!-- AUTO-GENERATED-CONTENT:END -->

Have you ever forget to export the content of a new source file into the `index.ts` file of it's parent directory? Not anymore!

> :warning: **This project is still experimental and subject to important changes.
> Use it at your own risk**

## Installation

```text
npm install @lint-ts-index/core
```

## Usage

See [Api Documentation](https://github.com/bbenoist/lint-ts-index/tree/master/doc/projects/core.md).

## See also

* [`@lint-ts-index/cli`](https://npmjs.com/package/@lint-ts-index/cli) - A command line linter based on this library.
* [`@lint-ts-index/eslint-plugin`](https://npmjs.com/package/@lint-ts-index/eslint-plugin) - Use lint-ts-index as an ESLint rule.

## License

This project is licensed under the MIT license which you can find a copy in the [`LICENSE`](https://raw.githubusercontent.com/bbenoist/lint-ts-index/master/LICENSE) file.
npm package: @lint-ts-index/eslint-plugin
Description: Check whether TS files are exported in index.ts
Author: Baptist BENOIST
Latest version: 0.1.1

# @lint-ts-index/eslint-plugin

[![GitHub tag (latest SemVer)](https://img.shields.io/github/v/tag/bbenoist/lint-ts-index?label=Version&logo=git&sort=semver)](https://github.com/bbenoist/lint-ts-index/releases)
[![License](https://img.shields.io/github/license/bbenoist/lint-ts-index?label=License&logo=github)](https://raw.githubusercontent.com/bbenoist/lint-ts-index/master/LICENSE)
[![GitHub issues](https://img.shields.io/github/issues/bbenoist/lint-ts-index?label=Issues&logo=github)](https://github.com/bbenoist/lint-ts-index/issues)

Purpose of this tool is to check that every files or subdirectories are exported in their corresponding `index.ts` files.

<!-- AUTO-GENERATED-CONTENT:START (SIMPLE_EXAMPLE_FAIL_OUTPUT) -->
```txt
foo.ts is not exported in index.ts
If you believe it's an error, please add an exclusion in .indexignore
```
<!-- AUTO-GENERATED-CONTENT:END -->

Have you ever forget to export the content of a new source file into the `index.ts` file of it's parent directory? Not anymore!

> :warning: **This project is still experimental and subject to important changes.
> Use it at your own risk**

## Installation

Indeed, the `eslint` and the `typescript` packages must be installed on your project since this plugin relies on them but can't decide for you which version to use.

### npm

```text
npm install --save-dev @lint-ts-index/eslint-plugin
```

### yarn

```text
yarn add -D @lint-ts-index/eslint-plugin
```

## Configure eslint

The most minimal ESLint configuration to enable lint-ts-index should look like this:

```js
module.exports = {
  plugins: ['@lint-ts-index'],
  rules: {
    '@lint-ts-index/exports': 'error'
  }
};
```

Valid values for the `@lint-ts-index/exports` rule are `error`, `warning` and `off`.

See also [Configuration File Formats](https://github.com/bbenoist/lint-ts-index/tree/master/doc/config-files.md) to include/exclude files and directories.

## See also

* [`@lint-ts-index/cli`](https://npmjs.com/package/@lint-ts-index/cli) - A command line linter based on this library.
* [`@lint-ts-index/core`](https://npmjs.com/package/@lint-ts-index/core) - The core library behind this ESLint plugin.

## License

This project is licensed under the MIT license which you can find a copy in the [`LICENSE`](https://raw.githubusercontent.com/bbenoist/lint-ts-index/master/LICENSE) file.
npm package: @lintangoao/soulcode-api-core
Description: Core reusable utilities, logger, and environment validation for Soulcode API backend
Author: Soulcode API Team
Latest version: 1.1.1

# @soulcode-api/core

Reusable core utilities for the Soulcode API backend.

## ✨ Features
- 🌿 Environment loader & validation (Valibot)
- 🪵 Winston logger (supports object/error logging)
- ⚠️ Standardized AppError classes
- 🧩 Reusable utils (date, string)

---

## 🧠 Installation
```bash
pnpm add @soulcode-api/core
npm package: @lintangoao/soulcode-core
Description: Core reusable utilities, logger, and environment validation for Soulcode API backend
Author: Soulcode API Team
Latest version: 1.1.0

# @soulcode-api/core

Reusable core utilities for the Soulcode API backend.

## ✨ Features
- 🌿 Environment loader & validation (Valibot)
- 🪵 Winston logger (supports object/error logging)
- ⚠️ Standardized AppError classes
- 🧩 Reusable utils (date, string)

---

## 🧠 Installation
```bash
pnpm add @soulcode-api/core