Thank you for your interest in contributing to electron-progress-window! This document provides guidelines and instructions for contributing.
- Fork the repository
- Clone your fork:
git clone https://github.com/YOUR_USERNAME/electron-progress-window.git cd electron-progress-window - Install dependencies:
npm install
- Create a branch for your changes:
git checkout -b feature/your-feature-name
npm run buildThis builds both CommonJS and ESM versions and runs post-build processing.
npm testFor test coverage:
npm run test:coveragenpm run lintTo auto-fix linting issues:
npm run lint:fixTo regenerate API documentation:
npm run docs- We use ESLint and Prettier for code formatting
- TypeScript is required for all source files
- Follow existing patterns in the codebase
- Add TSDoc comments for public APIs
- Ensure your code passes all tests and linting
- Update documentation if you're adding or changing features
- Add tests for new functionality
- Keep commits focused and use clear commit messages following Conventional Commits:
feat:for new featuresfix:for bug fixesdocs:for documentation changeschore:for maintenance taskstest:for test additions/changes
- Submit your pull request with a clear description of the changes
When reporting issues, please include:
- A clear description of the problem
- Steps to reproduce
- Expected vs actual behavior
- Your environment (Electron version, OS, Node.js version)
- Any relevant code snippets or error messages
If you discover a security vulnerability, please do NOT open a public issue. Instead, please email the maintainers directly so we can address it before public disclosure.
By contributing to electron-progress-window, you agree that your contributions will be licensed under the MIT License.