- Clone the repository:
git clone <repository-url>
cd partner-in-aging
- Install dependencies:
npm install
- Set up environment variables:
cp .env.example .env
Then edit .env
with your actual configuration values.
- Start the development server:
npm run dev
We use conventional commits for clear and standardized commit messages. Each commit message should follow this format:
type(scope): description
[optional body]
[optional footer]
Types:
feat
: New featurefix
: Bug fixdocs
: Documentation changesstyle
: Code style changes (formatting, etc)refactor
: Code refactoringperf
: Performance improvementstest
: Adding or modifying testschore
: Build process, dependencies, etcci
: CI/CD changesrevert
: Revert changes
Example:
git commit -m "feat(auth): add user authentication flow"
- ESLint and Prettier are configured for code quality and formatting
- Husky is set up with pre-commit hooks to:
- Run linting
- Format code
- Validate commit messages
- Run tests before pushing:
npm test
- Create feature branches from
main
:
git checkout -b feature/your-feature-name
-
Make your changes and commit using conventional commits
-
Push your branch and create a Pull Request
-
After review and approval, merge into
main
npm run dev
- Start development servernpm run build
- Build for productionnpm run preview
- Preview production buildnpm run lint
- Run ESLintnpm run lint:fix
- Fix ESLint issuesnpm run format
- Format code with Prettiernpm test
- Run testsnpm run test:coverage
- Run tests with coverage report