No Progress indication

Repository metrics

Stars

1,442 stars (1,442 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

Contributor guide

Research direction

Investigate the existing download mechanism in the codebase to find where progress data can be captured. Look for any existing event emitters or callbacks from the download library (e.g., ytdl core). Determine how to expose progress via an API endpoint or WebSocket, and then update the frontend to display a progress bar.

Tech stack

javascript

Domain

backend

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

None

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70