open-index/open-npm huggingface dataset:
npm package: @gmcb/prettier
Description: 代码美化规则
Author: yinjiazeng@163.com
Latest version: 0.1.6

# @gmcb/prettier

代码美化统一工具包

## 安装

```
npm i @gmcb/prettier --save-dev
```

## eslint
根目录新建`.eslintrc.js`

```js
const { eslint } = require('@gmcb/prettier');

module.exports = eslint();
```

## stylelint
根目录新建`.stylelintrc.js`

```js
const { stylelint } = require('@gmcb/prettier');

module.exports = stylelint();
```

## prettier
根目录新建`.prettierrc.js`

```js
const { prettier } = require('@gmcb/prettier');

module.exports = prettier();
```
npm package: @gmcb/uniapp
Description: uniapp公共模块
Author: yinjiazeng@163.com
Latest version: 0.21.3

# @gmcb/uniapp

uniapp项目公共模块，包含公共样式、方法、组件、类库等

## 安装

```
npm i @gmcb/uniapp
```

## 按需引入组件

```json
{
  "easycom": {
    "autoscan": true,
    "custom": {
      "^g-(.*)": "@gmcb/uniapp/lib/components/g-$1/g-$1.vue"
    }
  }
}
```
npm package: @gmcb/vite
Description: vite配置
Author: yinjiazeng@163.com
Latest version: 0.2.2

# @gmcb/vite

uniapp项目vite配置

## 安装

```
npm i @gmcb/vite --save-dev
```

## 使用
```js
// vite.config.js
import { defineConfig } from '@gmcb/vite';
import uni from '@dcloudio/vite-plugin-uni';

export default defineConfig({
  plugins: [uni()],
});
```
npm package: @gmcfall/react-firebase-state
Description: `react-firebase-state` is state management library for Firebase in React apps.
Author: Greg McFall
Latest version: 3.0.0

# react-firebase-state

`react-firebase-state` is state management library for Firebase in React apps.

The library helps you manage
- server-side state from *Firebase Auth* and *Firestore*
- client-side state that you control

## Installation

To use `react-firebase-state`, you must install four peer dependencies if you don't already have them:
- `react`
- `react-dom`
- `immer`
- `firebase`

In your react project folder, use npm to install these dependencies:
```sh
npm install react react-dom immer firebase
```

Then install the `react-firebase-state` component library.
```sh
npm install @gmcfall/react-firebase-state
```

## Usage
For usage instructions, see the
[react-firebase-state documentation](https://gmcfall.github.io/react-firebase-state-docs/) 
on Github Sites.

## Licensing and Attribution
This repository is licensed under the [MIT License](https://en.wikipedia.org/wiki/MIT_License). 
You are generally free to reuse or extend upon this code as you see fit; just include the 
[original copy](./LICENSE.md) of the license.  If you modify the software, you can add
additional copyright notices if appropriate.
npm package: @gmdaoeth/collections
Description: gmdao collections
Author: bhishp
Latest version: 3.19.6

# collections

An npm package that includes collection and contract info, including ABIs and addresses. A single source of truth across
all gmdao projects, reducing manual copy-pasta.

## Installing the package

This package is published to npm and can be installed like any other npm package.

```
yarn add @gmdaoeth/collections@latest
```

## Usage

### getContract

```ts
const fracturaContract = getContract(ChainID.MAINNET, CollectionID.Factura, provider);
```

## Development

### Generating new types

- do `yarn gen` from the root directory

### Publishing a new version

Publishing a new version is done as follows:

- branch-off from main
- run `yarn version --new-version [new-version] && git push --follow-tags`
- CI will recognise the new tag and publish to npm

## Build and publish

The publish step is done via a GitHub workflow, [collections.publish.yml](/.github/workflows/collections.publish.yml).
When executing the `yarn version` command, yarn will do a couple of things. First it will make a commit to modify the
package.json to be equal to the new version you provided, it will then tag the commit with the version. The second
command you instruct, `git push --follow-tags` will push the new commit and tags to the branch. The workflow has an
`on.push.tags` trigger, filtered on tags prefixed with collections/v. On a run, the workflow simply does a
`yarn publish [new-version]` based on the tag version that triggered the run. Note, the version prefix is set in the
[.yarnrc file](./.yarnrc) included in this directory.

The publish step will push to the gmdaoeth org npm package, therefore an npmjs token with **automation** privileges
needs to be added as a secret to the workflow, this is passed as `env.NODE_AUTH_TOKEN`.

## Manually publishing a new package

If needed/you want, you can manually publish a new version of the package, simply by running `yarn publish` from the
root of the project. For example, you may want to test your branch changes from another repo, so can do something like
`yarn publish --new-version 1.0.1-alpha`

Note, in order to publish from your machine you will need to have logged-in with npm (use `npm adduser` and enter your
npm login details). Additionally, your account should be added to the `@gmdaoeth` team on npmjs.