Skip to content

akaushesh/Leetcode_Tracker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

36 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Leetcode Tracker

A full-stack LeetCode dashboard that helps users streamline their DSA preparation with personalized tracking, study plans, and contest updates all in one place.

πŸš€ Introduction

Leetcode Tracker is a productivity-focused platform designed for competitive programmers and coding enthusiasts. It automates progress tracking on LeetCode, segmenting problems by topic and company, and also provides real-time updates on upcoming contests β€” minimizing the manual effort needed to stay on top of your coding goals.

This platform is already used by DSA learners to track over problems, visualize their contest performance, and follow structured study plans.


πŸ“š Table of Contents


✨ Features

  • πŸ” Tracks solved Leetcode problems per user
  • πŸ“Š Topic-wise, difficulty-wise, and company-specific analytics
  • πŸ“… Aggregated timeline of upcoming LeetCode contests
  • 🧠 Personalized study plans based on user progress
  • ⚑ Fast and responsive UI with modern frontend tooling
  • 🌐 Full-stack architecture deployed via Vercel (frontend) and Render (backend)

πŸ› οΈ Tech Stack

Layer Technology
Frontend React, Vite, JavaScript
Backend Node.js, Express
Deployment Vercel (frontend), Render (backend)
Utilities Cheerio (for scraping), dotenv, ExcelJS
Styling CSS Modules / Tailwind (if applicable)

🧩 Installation

Prerequisites

  • Node.js (v16 or later)
  • npm

Steps

  1. Clone the repository:
git clone https://github.com/Anik2109/Leetcode_Tracker.git
cd Leetcode_Tracker
  1. Install dependencies:
# For the client
cd client
npm install

# For the server
cd ../server
npm install
  1. Configure environment variables (see below).

βš™οΈ Environment Configuration

Each subproject (client/ and server/) includes an .env.example file with commented instructions.

To configure:

# In both 'client' and 'server' directories
cp .env.example .env

Update the .env files with any necessary credentials or config values (API URLs, database URIs, etc.).


πŸ§ͺ Usage

Local Development

Start the backend and frontend locally:

# In one terminal
cd server
npm start

# In another terminal
cd client
npm run dev

Then open http://localhost:5173 in your browser to start using the app.


🌍 Deployment

  • Frontend is deployed on Vercel
  • Backend is hosted on Render

Make sure to update environment variables in production as needed.


πŸ’‘ Want to contribute? Fork the repo, open a pull request, or raise issues. Let’s make CP prep easier for everyone!

About

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages