MetricInsights Portal Page development framework and build tools
This monorepo contains tools and packages for developing MetricInsights Portal Pages:
pp-dev: Core development framework and build tool for Portal Pagescreate-pp-dev: CLI tool for scaffolding new Portal Page projects
| Package | Description | Version |
|---|---|---|
| @metricinsights/pp-dev | Core development framework and build tool for Portal Pages | |
| @metricinsights/create-pp-dev | CLI tool for scaffolding new Portal Page projects |
This repository uses semantic-release for automated versioning and releases with a PR-based workflow. Direct pushes to the main branch are not allowed - all releases go through Pull Requests.
- Create feature branch from
mainordevelop - Make changes following conventional commit format
- Create Pull Request and get it reviewed
- Merge to main → Automatic release! 🎉
main→ Production releases (stable versions)develop→ Beta releases (pre-release versions)- Feature branches → Development work
# New feature (minor version bump)
git commit -m "feat: add new authentication system"
# Bug fix (patch version bump)
git commit -m "fix: resolve memory leak in data processing"
# Breaking change (major version bump)
git commit -m "feat!: change API response format
BREAKING CHANGE: The API now returns data in a different structure"- 📖 Complete Release Workflow Guide - Detailed user guide
- ⚙️ Semantic Release Setup - Technical setup details
- pp-dev documentation - Core framework docs
- create-pp-dev documentation - CLI tool docs
- Contributing Guidelines - How to contribute
# Using npm
npm create @metricinsights/pp-dev@latest
# Using yarn
yarn create @metricinsights/pp-dev
# Using pnpm
pnpm create @metricinsights/pp-dev# Clone and install
git clone https://github.com/mi-examples/pp-dev-js.git
cd pp-dev-js
npm install
# Build all packages
npm run build
# Available scripts
npm run release # Run semantic-release
npm run release:beta # Run beta release on develop branchNote: This project includes a .cursorrules file with comprehensive commit message guidelines and development best practices for Cursor AI users.
- Fork the repository
- Create a feature branch from
mainordevelop - Make your changes with conventional commits
- Push to your fork and create a Pull Request
- Get it reviewed and merge when approved
- Automatic release happens on merge to main! 🎉
- Use conventional commit format
- Keep commits focused and atomic
- Provide clear PR descriptions
- Ensure tests pass and documentation is updated
ISC License - see LICENSE file for details.
Happy Developing! 🚀
For detailed information about the release process, check the Release Workflow Guide or Semantic Release Setup documentation.