daniele-liprandi/EvoNEST-backbone

Console logging in production code

Open

#22 opened on Nov 26, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)JavaScript (2 forks)auto 404
BackendLowenhancementgood first issue

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Description

Extensive use of console.log and console.error throughout the codebase without structured logging.

Files affected

  • 20+ files in src/app/api/

Recommended fix

  1. Implement a logging library (pino, winston)
  2. Add log levels (debug, info, warn, error)
  3. Include request context in logs

Contributor guide

Research direction
Implement a structured logging library, configure log levels, and add request context to logs. Replace all console.log/console.error calls.
Tech stack
javascriptnodejs
Domain
backendapi
Issue type
Refactor
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75