changhaoting1998-star/manufacturing-wechat-miniapp-starter

This repository is a starter kit for developers building a shop-floor data entry channel as a WeChat Mini Program on top of an existing MES. It targets small and medium manufacturers whose frontline events are still reported on paper or in chat. All data, identifiers and credentials are synthetic, and the kit is designed to be read and extended, not deployed as-is.

What it demonstrates

The starter pairs native WXML/WXSS/JavaScript page skeletons with a platform-neutral cloud gateway and domain rules. Its documented workflows cover employee access requests with reviewer approval, self-only clock-in and clock-out, payroll notice acknowledgement with a signature hash, dynamic forms with fail-closed validation, and MES exports protected by idempotency keys and payload hashes. The README states that every outbound MES event must carry a stable idempotency key, employee binding, work-order references, event time and receipt; repeated keys with the same payload return the original receipt, changed payloads fail, and uncertain writes stay pending for safe retry.

Requirements and setup path

Node.js 20 or newer is needed for the zero-dependency tests and demo (npm test, npm run demo). The Mini Program path requires WeChat Developer Tools and a locally supplied AppID, plus CloudBase configuration in the setup steps. Importantly, the included cloud gateway is described as deliberately not deployable without operator-owned identity and storage wiring, and privileged collections must be configured so clients cannot read or write employee, payroll, signature, attendance or audit data directly.

Boundaries

The kit excludes real identifiers, credentials, employee records and direct client access to privileged data. The README lists production prerequisites that remain the operator's responsibility: server-side authorization on every route, encrypted storage, audit retention, rate limits, backups and monitoring, plus data retention, deletion and incident-response policies. The test suite checks authorization and failure paths on synthetic data, which is not a substitute for production security review.

Efficiency comparisons are intended to use MES-confirmed events under comparable conditions and to support, not replace, human review of assignment, pay or employment decisions. The optional Feishu SSO boundary keeps Mini Program and Feishu identities separate and treats login as authorization for nothing beyond that login.

HotRepo's take

At the single 2026-10-29 observation, HotRepo recorded 124 total stars on its NEW-REPOSITORY board (JavaScript, #13), not a daily growth figure. Comparable daily history is insufficient, so this sample says nothing about sustained interest. The MIT licence permits reuse with attribution.