open-index/open-npm huggingface dataset:
npm package: @mpxjs/mpx-query
Description: Hooks for managing, caching and syncing asynchronous and remote data in Mpx
Author: Mater
Latest version: 0.0.2

# Mpx Query

## Usage

```js
import { MpxQueryPlugin } from '@mpxjs/mpx-query'
mpx.use(MpxQueryPlugin)
```

document: https://tanstack.com/query/latest/docs/framework/vue/overview

forked from Vue query
npm package: @mpxjs/stylelint-config-recommended-mpx
Description: The recommended shareable Mpx config for Stylelint.
Author: Yosuke Ota
Latest version: 1.0.2

# stylelint-config-recommended-mpx

```js
// stylelint config

module.exports  = {
    extends: ['@mpxjs/stylelint-config-recommended-mpx'],
}
```
npm package: @mpxjs/template-engine
Description: template-engine for mpx runtime render
Author: xiaolei
Latest version: 2.8.7

# Template-engine

小程序运行时渲染基础模板生成引擎。

> Fork from @tarojs/shared for generating template.

# Install

```sh
npm install @mpxjs/template-engine
# or
yarn add @mpxjs/template-engine
# or
pnpm add @mpxjs/template-engine
```

# Basic Usage

1. 生成模板代码

```js
const { createTemplateEngine } = require('@mpxjs/template-engine')

const templateEngine = createTemplateEngine('wx') // 'wx' | 'ali' | 'swan' | 'qq' | 'tt' | 'dd' | 'web' | 'tenon'

const templateCode = templateEngine.buildTemplate({
  baseComponents: ['view', 'button'] // 需要使用的小程序基础组件
})
```

将会输出

```html
<template name="mpx_tmpl">
  <element r="{{r}}" wx:if="{{r}}" />
</template>
<template name="t_0_view">
  <view data-mpxuid="{{i.d.uid}}">
    <block wx:for="{{i.c}}" wx:key="index">
      <template is="t_1_container" data="{{i:item}}" />
    </block>
  </view>
</template>
<template name="t_0_button">
  <button data-mpxuid="{{i.d.uid}}">
    <block wx:for="{{i.c}}" wx:key="index">
      <template is="t_1_container" data="{{i:item}}" />
    </block>
  </button>
</template>
<template name="t_0_#text" data="{{i:i}}">
  <block>{{i.ct}}</block>
</template>
<template name="t_0_container">
  <template is="t_0_{{i.nt}}" data="{{i:i}}" />
</template>
<template name="t_1_container">
  <block wx:if="{{i.nt === '#text'}}">
    <template is="t_0_#text" data="{{i:i}}" />
  </block>
  <block wx:else>
    <element r="{{i}}" />
  </block>
</template>
```

2. 写入文件

```js
const fs = require('fs')
fs.writeFile('base.wxml', code)
```

3. 引入基础模板，使用vnode渲染页面

```html
<import src="base.wxml" />
<template is="t_0_container" data="{{ i: r }}" />
```

```js
Component({
  data: {
    r: {
      // 描述节点的vnode
      nt: 'view', // 节点类型
      d: {
        class: "view-class" // 节点属性值
      },
      c: [ // 子节点
        {
          nt: 'button',
          d: {},
          c: [
            {
              nt: '#text',
              ct: '运行时渲染'
            }
          ]
        }
      ]
    }
  }
})
```

4. 模板引擎将会在渲染出正确的组件

# Build Options

### 自定义组件/运行时组件

除了基础组件外，模板引擎还支持自定义组件的渲染

```js
const templateCode = templateEngine.buildTemplate({
  normalComponents: [ 'custom-dialog' , 'custom-popup'], // 需要使用的自定义组件
})
```

### 自定义属性名

如果需要自定义某个模板组件的属性，例如生成的组件需要一个`class`属性。可以通过传入对象配置。

```js
const templateCode = templateEngine.buildTemplate({
  baseComponents: [
    {
      view: ['class']
    }
  ] // 需要使用的小程序基础组件
})
```

### 自定义属性值

如果想自定义`class`从`data`的取值。

```js
const templateCode = templateEngine.buildTemplate({
  baseComponents: [
    {
      view: {
        class: 'c'
      }
    }
  ] // 需要使用的小程序基础组件
})
```
npm package: @mpxjs/vuese-parser
Description: Vue file parser for automatic document generation
Author: qiushuibai
Latest version: 1.0.6

# `@mpxjs/vuese-parser`

## mixin 逻辑

```typescript
export interface ParserResult {
  props?: PropsResult[]
  events?: EventResult[]
  slots?: SlotResult[]
  mixIns?: MixInResult[]
  methods?: MethodResult[]
  computed?: ComputedResult[]
  data?: DataResult[]
  watch?: WatchResult[]
  name?: string
  componentDesc?: CommentResult
  externalClasses?: ExternalClassesResult[]
}
```

基于 vue2.x mergeOptions 策略
npm package: @mpya-digital/component-library
Description: Component library for Mpya Digital
Latest version: 0.0.4

# Mpya Component Library 🍕

_Lorem ipsum._

## Table of contents

- [Mpya Component Library 🍕](#componet-library-)
  - [Table of contents](#table-of-contents)
  - [Built With](#built-with)
  - [Getting Started](#getting-started)
    - [Installation](#installation)
  - [Available scripts](#available-scripts)
  - [Project Structure](#project-structure)
    - [Gitlab Issues](#gitlab-issues)
    - [Git Branch Structure](#git-branch-structure)
      - [`main`](#main)
      - [`Working branches`](#working-branches)
  - [Deployment](#deployment)
  - [Contributing](#contributing)
  - [Contributors](#contributors)

## Built With

## Getting Started

### Installation

Clone the project and install all dependencies with `yarn`:

```
yarn
```

### Set prettier as the default code formatter

1. Open the command palette using `cmd` + `,`.
2. Choose the **Workspace** tab from the two tabs 'User' and 'Workspace'
3. Search for "Default Formatter" in the search bar.
4. Set the default formatter to **Prettier - Code Formatter** under the heading _Editor: Default Formatter_.

### Run the code locally

Run the code locally using the script:

```
yarn dev
```

Happy coding! 👩‍💻🧑‍💻

## Available scripts

In the project directory, you can run:

### Create component

To generate a component, you can run `./create_component.sh`. This will create a new component for you based on the files in `/template`. To modify the template, just modify the files under `/template`.

## Project Structure

### Gitlab Issues

The built-in Gitlab Issues functionality is used for project management and task structuring.
Opening a merge request through an issue will automatically create a branch for the issue. A merge to main will automatically close the branch unless specified otherwise.

### Git Branch Structure

#### `main`

#### `Working branches`

## Deployment

🔨 Lorem ipsum

## Contributing

Contributions are welcome. If you've fixed a bug or implemented a cool new feature that you would like to share, please feel free to open a pull request here.

## Contributors

_Add your name here if you start contributing_ 👩‍💻🧑‍💻

- Johan Sjöstrand
- Mathilda Moström