MLSAKIIT / MLSAKIIT/ComposeGenie

Backend - Initialize Express + TypeScript Server

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Backend enhancement
Dominant language
TypeScript
Stars
4
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.

The backend folder currently lacks a runnable API server, making it impossible to develop or test backend endpoints locally.


Describe the solution you'd like

Set up a TypeScript-based Express server with:

  • A /health endpoint
  • Routing support for future APIs
  • Middleware for error handling and logging

Describe alternatives you've considered
  • Using Fastify, which is faster, but Express provides simplicity and strong community support, making it ideal for contributors and long-term maintenance.

Use Case

Provides a foundation for all backend endpoints and microservice integrations, allowing the frontend and services to connect seamlessly.


Additional context
  • Include ESLint for consistent code style
  • Use nodemon for automatic server restarts during development
  • Optional: integrate dotenv for environment variable management

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the backend folder and existing package configuration to find the server entry point and development scripts. Done means a TypeScript Express server runs locally, exposes /health, supports future routing, includes logging and error-handling middleware, and provides the requested lint and restart tooling.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, express, typescript
Domain
api, backend, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.