How lspriv/wx-calendar works
Project type and purpose
• This is a WeChat Mini-Program UI component library (“wx-calendar”) packaged as an NPM module.
• Its purpose is to provide a highly configurable calendar component with multiple views (month, week, schedule) and a plugin architecture for extending functionality (e.g., lunar calendar, ICS imports).
File structure
• Top-level:
• build / — custom build‐and‐pack scripts (clean, pack, watch, handler).
• dev / — a mini-program sandbox (app.js, pages/index, config.json) used for local development & preview.
• scripts / — convenience scripts (dev, publish) invoked by npm run.
• src / — primary component source:
• src/basic: core calendar logic, layout, drag/drop, printing, service layer.
• src/interface: TypeScript interfaces, decorators, component API definitions.
• src/plugins: built-in plugins (e.g., mark.ts).
• src/utils: shared helpers (calc, shared).
• src/style, src/tpls, src/wxs: style definitions, template fragments (wxml), and mini-program JS snippets.
• tmpls / — JSON templates for packaging into mini-program apps (skyline, webview).
• build artifacts (dist) are generated under package.json’s main/lib directories at publish time.
• Config files: tsconfig.json, .eslintrc.js, gulpfile.js, .prettierrc.js, plus CI workflows under .github.
README for additional insights
• Confirms feature set: year/month/week/schedule views, plugin system, multi-render modes (Skyline vs Webview).
• Describes NPM usage, development (npm run dev triggers build/watch into dev/), packaging (npm run build, npm run package).
• Highlights dependency on WeChat SDK ≥ 3.0.0, and integration points: import component in page config, bindload/bindclick events, selectComponent API.
• Multi-platform support sections: Donut, UniApp, Taro.