open-index/open-npm huggingface dataset:
npm package: @suntree/tarojs-plugin-platform-miniprogram
Description: @tarojs/plugin-platform-weapp custom wxml support
Author: suntree
Latest version: 1.0.8

# tarojs-plugin-platform-miniprogram

[![](https://img.shields.io/npm/v/tarojs-plugin-platform-miniprogram)](https://www.npmjs.com/package/tarojs-plugin-platform-miniprogram)
[![Node.js Package](https://github.com/baranwang/tarojs-plugin-platform-miniprogram/actions/workflows/npm-publish.yml/badge.svg)](https://github.com/baranwang/tarojs-plugin-platform-miniprogram/actions/workflows/npm-publish.yml)
![](https://img.shields.io/npm/l/tarojs-plugin-platform-miniprogram)

[@tarojs/plugin-platform-weapp](https://github.com/NervJS/taro/tree/next/packages/taro-weapp) 自定义 wxml 支持，目前可主要用于支持 [`page-meta`](https://developers.weixin.qq.com/miniprogram/dev/component/page-meta.html) 和 [`navigation-bar`](https://developers.weixin.qq.com/miniprogram/dev/component/navigation-bar.html)，[`Taro`](https://github.com/NervJS/taro) 版本需大于 `3.1.0`


### 2022-09-21
- 该版本升级了对taro 3.5.X的插件支持


## 安装

```shell
npm i -D tarojs-plugin-platform-miniprogram
# or
pnpm add -D tarojs-plugin-platform-miniprogram
# or
yarn add -D tarojs-plugin-platform-miniprogram
```

## 配置

`config/index.js` 中引入 plugin

```javascript
const config = {
  // ...
  plugins: ["tarojs-plugin-platform-miniprogram"],
  // ...
};

// or

const config = {
  // ...
  plugins: [
    [
      "tarojs-plugin-platform-miniprogram",
      /**
       * @type {import('tarojs-plugin-platform-miniprogram').Options}}
       */
      {
        prefix: "<page-meta></page-meta>", // or path.resolve(__dirname, './prefix.wxml')

        /**
         * @version 0.1.0
         */
        include: [
          "pages/index/index",
          "pages/logs/logs",
          new RegExp('^pages/foo'),
        ],
        exclude: []
      },
    ],
  ],
  // ...
};
```

修改 `package.json`

```diff
{
  "scripts: {
-   "build:weapp": "taro build --type weapp",
+   "build:weapp": "taro build --type miniprogram",
  }
}
```

## 使用

### 通用

```javascript
const { page } = Taro.getCurrentinstance();

page.setData({
  pageMeta: {
    backgroundTextStyle: 'dark',
    // ...
  },
  navigationBar: {
    // ...
  },
});
```

### React

除了通用方法外，为 React 封装了组件

```tsx
import { PageMeta, NavigationBar } from "tarojs-plugin-platform-miniprogram/dist/components";

export default () => {
  return (
    <>
      <PageMeta backgroundTextStyle='dark'>
        <NavigationBar title='Awesome Taro' />
      </PageMeta>
    </>
  )
}
```
npm package: @sunvcloud/core
Description: This template should help get you started developing with Vue 3 and Typescript in Vite.
Author: sunv
Latest version: 0.0.4

# Vue 3 + Typescript + Vite

This template should help get you started developing with Vue 3 and Typescript in Vite.

## Recommended IDE Setup

[VSCode](https://code.visualstudio.com/) + [Vetur](https://marketplace.visualstudio.com/items?itemName=octref.vetur). Make sure to enable `vetur.experimental.templateInterpolationService` in settings!

### If Using `<script setup>`

[`<script setup>`](https://github.com/vuejs/rfcs/pull/227) is a feature that is currently in RFC stage. To get proper IDE support for the syntax, use [Volar](https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.volar) instead of Vetur (and disable Vetur).

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

Since TypeScript cannot handle type information for `.vue` imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can use the following:

### If Using Volar

Run `Volar: Switch TS Plugin on/off` from VSCode command palette.

### If Using Vetur

1. Install and add `@vuedx/typescript-plugin-vue` to the [plugins section](https://www.typescriptlang.org/tsconfig#plugins) in `tsconfig.json`
2. Delete `src/shims-vue.d.ts` as it is no longer needed to provide module info to Typescript
3. Open `src/main.ts` in VSCode
4. Open the VSCode command palette
5. Search and run "Select TypeScript version" -> "Use workspace version"
npm package: @sunvcloud/cseditor
Description: SunvCloud Editor V3
Author: sunvcloud@126.com
Latest version: 0.4.0

# 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

- [VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.volar)

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

Since TypeScript cannot handle type information for `.vue` imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can enable Volar's `.vue` type support plugin by running `Volar: Switch TS Plugin on/off` from VSCode command palette.
npm package: @sunvcloud/csuse
Description: SunvCloud Use V3
Author: sunvcloud@126.com
Latest version: 2.0.6

# 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

- [VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.volar)

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

Since TypeScript cannot handle type information for `.vue` imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can enable Volar's `.vue` type support plugin by running `Volar: Switch TS Plugin on/off` from VSCode command palette.
npm package: @sunvcloud/csweb
Description: SunvCloud Web V3
Author: sunvcloud@126.com
Latest version: 0.3.3

# 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

- [VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.volar)

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

Since TypeScript cannot handle type information for `.vue` imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can enable Volar's `.vue` type support plugin by running `Volar: Switch TS Plugin on/off` from VSCode command palette.
npm package: @sunweibin/linters
Description: Dobby Eslint StyleLint CommitLint 规则集合
Author: sunweibin
Latest version: 2.2.3

# fe-linters
一个包含 prettier，eslint，stylelint 等代码规范校验的配置文件合集

简化 ESLint, StyleLint, commitLint 等工具的使用

## 功能点

- [x] ESLint
- [x] ReactLint
- [x] StyleLint
- [ ] commitLint

## 安装

```bash
yarn add @sunweibin/linters
```

## 使用

### eslint [rules](/lib/eslint.js)

项目根目录创建 `.eslintrc.js`

```js
const { eslint, lintMerge } = require('@sunweibin/linters');

module.exports = lintMerge(eslint, {
  parserOptions: {
    // 使用项目的 babel 配置
    babelOptions: {
      configFile: './babel.config.js',
    },
  },
});
```

### reactlint [rules](/lib/reactlint.js)

如果项目使用 React ,项目根目录创建 `.eslintrc.js`

```js
const { reactlint, lintMerge } = require('@sunweibin/linters');

module.exports = lintMerge(reactlint, {
  parserOptions: {
    // 使用项目的 babel 配置
    babelOptions: {
      configFile: './babel.config.js',
    },
  },
});
```

### stylelint [rules](/lib/stylelint.js)

项目根目录创建 `.stylelintrc.js`

```js
const { stylelint } = require('@sunweibin/linters');

module.exports = stylelint;
```
npm package: @sunweibin/yrm
Description: yarn registry manager can help you easy and fast switch between different yarn registries, now include: yarn, tabao, npm
Author: sunweibin
Latest version: 1.3.0

# yrm -- Yarn Registry Manager
管理所有的yarn包的下载源Registry

[![NPM version][npm-image]][npm-url]

`yrm`可以帮助你轻松地添加、删除、查询、切换所有的Yarn Registries,目前内置`npm`,`cnpm`,`yarn`三个源

## Install

```
$ npm install -g @sunweibin/yrm
```

## Example

列出所有Registry
```
$ yrm ls
或者
$ yrm list

┌───────┬──────┬─────────────────────────────────┐
│ Using │ name │ Registry                        │
├───────┼──────┼─────────────────────────────────┤
│ -     │ npm  │ https://registry.npmjs.org/     │
│ *     │ cnpm │ https://registry.npmmirror.com/ │
│ -     │ yarn │ https://registry.yarnpkg.com/   │
└───────┴──────┴─────────────────────────────────┘

```

列出当前正在使用的源
```
# 默认查看 yarn  配置的镜像源
$ yrm now
// 查看 npm 配置的镜像源
$ yrm now npm
// 查看 pnpm 配置的镜像源
$ yrm now pnpm
// 查看所有的包管理器的镜像源
$ yrm now all
```

切换 yarn 的镜像源
```
$ yrm use cnpm

Your yarn registry has been set to:

yarn's Current Registry:
   [cnpm](https://registry.npmmirror.com/)
```

往镜像源列表中添加镜像源进行管理
```
$ yrm add swb https://registry.npmjs.org/

You have added swb successfully!
// ....
```

从镜像源列表中删除配置的自定义的镜像源
> 当删除的源正在使用时会指定 yarn 的官方源
```
$ yrm del swb
```

## Usage

```
$ yrm help

Usage: yrm [options] [command]

Options:
  -V, --version                               output the version number
  -h, --help                                  display help for command

Commands:
  list|ls                                     列出所添加的包管理器镜像源，高亮的为 yarn 当前使用的镜像源
  now [packageManagerName]                    显示包管理器当前使用的镜像源, 默认显示 yarn 使用的镜像源, 可以查看比如:npm, pnpm配置的镜像源
  use <registry-name>                         切换 yarn 的当前镜像源
  add <name> <registry> [home]                添加镜像源管理
  del <name>                                  删除指定的镜像源，当删除的源正在使用时会指定 yarn 的官方源
  set <package-manager-name> <registry-name>  给其他包管理器设置 registry 例如: npm, pnpm
  help                                        打印出yrm的命令帮助信息
```

## Default Registries

* [npm](https://registry.npmjs.org/)
* [cnpm](https://registry.npmmirror.com/)
* [yarn](https://registry.yarnpkg.com/)

## LICENSE
MIT


[npm-image]: https://img.shields.io/npm/v/@sunweibin/yrm.svg?style=flat-square
[npm-url]: https://npmjs.org/package/@sunweibin/yrm