Pinak

A modern monorepo project built with Turborepo, featuring a Node.js API, Expo React Native mobile app, and Vite React web app. This setup provides a scalable foundation for full-stack development with shared packages for UI components, TypeScript configurations, and ESLint rules.

Tech Stack

• Monorepo Management: Turborepo
• Language: TypeScript
• Linting & Formatting: ESLint, Prettier
• API: Node.js, Express, Prisma (PostgreSQL), Zod validation
• Mobile: Expo, React Native, Expo Router
• Web: Vite, React
• Shared Packages: UI components (React), TypeScript configs, ESLint configs

Apps and Packages

Apps

• apps/api: Node.js REST API with Express, Prisma ORM, PostgreSQL database, rate limiting, logging, and input validation.
  • API Coverage:
    • Authentication: Login, register, email verification, password reset, refresh tokens, Google OAuth
    • Products: Full CRUD with variants, images, related products, and category management
    • ComboKits: Full CRUD with item management
    • Catalog: Brands, categories, options, filters, tax classes, length/weight classes, featured sections
    • Not yet implemented: Reviews (tables exist but no endpoints yet)
• apps/mobile: Expo React Native app with navigation, haptic feedback, and shared UI components.
• apps/web: Vite-based React web app with shared UI components.

Packages

• packages/ui: Shared React component library (buttons, cards, etc.).
• packages/eslint-config: Shared ESLint configurations for consistent code quality.
• packages/types: Shared TypeScript type definitions and Zod validation schemas for API contracts.
  • Exports namespaced types (AuthApi, ProductApi, ComboKitApi, CatalogApi) to prevent collisions
  • Root-level convenience aliases (AuthBodyTypes, AuthParamsTypes, etc.)
• packages/typescript-config: Shared TypeScript configurations for apps and packages.

Prerequisites

• Node.js >= 18
• npm (or yarn/pnpm)
• PostgreSQL database (local or cloud, e.g., Prisma Postgres)
• For mobile: Expo CLI (npm install -g @expo/cli)

Setup

1. Clone the repository:

   git clone <repository-url>
   cd pinak

2. Install dependencies:

   npm install

3. Set up environment variables:

   • Copy .env.example to .env in each app directory:

     cp apps/api/.env.example apps/api/.env
     cp apps/web/.env.example apps/web/.env
     cp apps/mobile/.env.example apps/mobile/.env

   • Edit each .env file with your actual values (see ENV_SETUP.md for details).
   • For the API, ensure DATABASE_URL points to your PostgreSQL database.

4. Set up the database:

   • Navigate to the API app:

     cd apps/api

   • Generate Prisma client:

     npm run prisma:generate

   • Run database migrations:

     npm run prisma:migrate:dev

   • (Optional) Open Prisma Studio to view/edit data:

     npm run prisma:studio

5. Build shared packages (if needed):

   npm run build

Running the Project

All Apps

npm run dev

Individual Apps

• API:

  npm run dev:api  # or cd apps/api && npm run dev

  API runs on http://localhost:3000 (or configured PORT)

  • Base route: /api/v1
  • Health check: GET /api/v1/health
  • Swagger docs (if enabled): /api/v1/docs

• Web:

  npm run dev:web  # or cd apps/web && npm run dev

• Mobile:

  npm run dev:mobile  # or cd apps/mobile && npm run dev

  Then use Expo Go app or simulator.

Building

All Apps and Packages

npm run build

Individual Apps

• API: cd apps/api && npm run build
• Web: cd apps/web && npm run build
• Mobile: cd apps/mobile && npx expo build

Other Commands

• Linting: npm run lint
• Type Checking: npm run check-types
• Formatting: npm run format
• Prisma Studio: npm run prisma:studio

Project Structure

pinak/
├── apps/
│   ├── api/          # Node.js Express API with Prisma
│   │   ├── src/
│   │   │   ├── controllers/    # HTTP request handlers
│   │   │   ├── services/       # Business logic layer
│   │   │   ├── repositories/   # Database access layer
│   │   │   ├── routes/         # API route definitions
│   │   │   ├── middlewares/    # Auth, validation, error handling
│   │   │   ├── lib/            # Utilities (config, logger, jwt, etc.)
│   │   │   ├── types/          # API-specific types
│   │   │   └── index.ts        # App bootstrap
│   │   └── prisma/             # Schema, migrations, seed
│   ├── mobile/       # Expo React Native app
│   └── web/          # Vite React app
├── packages/
│   ├── ui/           # Shared React components
│   ├── eslint-config/# Shared ESLint configs
│   ├── types/        # Shared TypeScript types & Zod schemas
│   └── typescript-config/  # Shared TS configs
├── package.json
├── turbo.json
└── README.md

API Architecture

The backend follows a layered architecture:

• Controller → Service → Repository → Prisma Client
• Controllers: Thin HTTP layer, parse requests, return standardized JSON responses
• Services: Business logic, validation, orchestration
• Repositories: Database access abstraction
• All errors extend BaseError and are handled by centralized error middleware

Contributing

1. Follow the existing code style (ESLint + Prettier).
2. Run tests and linting before committing.
3. Use conventional commits for PRs.

License

See LICENSE file.

cd my-turborepo

# With [global `turbo`](https://turborepo.dev/docs/getting-started/installation#global-installation) installed (recommended)
turbo login

# Without [global `turbo`](https://turborepo.dev/docs/getting-started/installation#global-installation), use your package manager
npx turbo login
yarn exec turbo login
pnpm exec turbo login

This will authenticate the Turborepo CLI with your Vercel account.

Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your Turborepo:

# With [global `turbo`](https://turborepo.dev/docs/getting-started/installation#global-installation) installed (recommended)
turbo link

# Without [global `turbo`](https://turborepo.dev/docs/getting-started/installation#global-installation), use your package manager
npx turbo link
yarn exec turbo link
pnpm exec turbo link

Useful Links

Learn more about the power of Turborepo:

• Tasks
• Caching
• Remote Caching
• Filtering
• Configuration Options
• CLI Usage