- Clone the repository
- Install dependencies:
pnpm install - Run tests:
pnpm test - Start development:
pnpm dev
This project uses Virtualdisplay shared configuration for:
- ESLint with strict defensive programming rules
- TypeScript with maximum type safety
- Prettier for consistent formatting
- Vitest for testing
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a pull request
- Run
pnpm validateto ensure all checks pass - Write tests for new functionality
- Update documentation as needed
- Follow the existing code style
Follow conventional commits specification for automated releases:
feat:New feature (minor release)fix:Bug fix (patch release)perf:Performance improvement (patch release)refactor:Code refactoring (patch release)revert:Revert previous changes (patch release)
docs:Documentation changes (no release)style:Code style changes (no release)test:Test changes (no release)chore:Build process or tooling (no release)ci:CI configuration changes (no release)build:Build system changes (no release)
- Add
BREAKING CHANGE:in commit body for major release - Or use
scope: BREAKINGfor major release
feat: add new user authentication system
fix: resolve memory leak in data processing
perf: optimize database queries for faster response
refactor: simplify user validation logic
docs: update API documentation with new endpointsFor questions or help, please contact: support@virtualdisplay.io
By contributing, you agree that your contributions will be licensed under the MIT License.