How only9464/eweb works
Project type and purpose
• This is a WeChat Mini-Program (single-page application style) that provides a comprehensive set of utilities: payments (wallet, scan, QR, bank cards), account management, utility recharges, coupons, facial recognition (aiface), etc.
• No server-side code lives here; instead it relies on external APIs (bank/pay gateways, cloudbase functions, third-party modules) and local logic packaged as JS/WASM modules.
File structure
• Top-level config & entry points:
• app.js, app.json, app.wxss — the program’s bootstrap and global styles
• project.config.json, .cloudbase/… — deployment / cloud environment definitions
• Pages (pages/…) & sub-pages: each feature lives under pages/[featureName] with .js/.json/.wxml/.wxss
• Reusable UI Components (components/…)
• Third-party integrations (thirdpart/…, miniprogram_npm/…)
• Utility libraries (utils/…) for requests, formatting, encryption, throttling, etc.
• Static assets & styling under style/images
README
• No content; architecture must be deduced from file layout and naming conventions.
Final recommendations
• Calls with protocol (HTTPS, WebSocket) and modules used (utils/request.js, sm4, WASM).
• Review with stakeholders to ensure it aligns with actual API endpoints and deployment setup in .cloudbase.