Skip to content

fix: Console.log Statements Left in Production Code#75

Open
Aditya8369 wants to merge 1 commit intoomkarhole:mainfrom
Aditya8369:73
Open

fix: Console.log Statements Left in Production Code#75
Aditya8369 wants to merge 1 commit intoomkarhole:mainfrom
Aditya8369:73

Conversation

@Aditya8369
Copy link
Contributor

What I changed

  • Added Winston dependency in package.json and updated package-lock.json.
  • Created shared logger at logger.js with JSON logs, timestamps, stack support, and environment-based log level.
  • Replaced console logging with logger calls (info/warn/error + context metadata) in:
    • auth.controller.js
    • group.controller.js
    • message.controller.js
    • privacy.controller.js
    • socket.js
    • db.js
    • email.js
    • auth.middleware.js
    • index.js
    • user.seed.js

Verification performed

  • Ran install: npm install winston in backend.
  • Searched for remaining console usage in backend source: no console.* matches found in backend/src.
  • Checked diagnostics on backend/src: no errors found.

closes #73

@vercel
Copy link

vercel bot commented Mar 18, 2026

@Aditya8369 is attempting to deploy a commit to the omkarhole's projects Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Console.log Statements Left in Production Code

1 participant