Logging Best Practices

Summary

Writing logs that are actually useful when something goes wrong in production — structured, leveled (info/warn/error), and free of sensitive data like passwords or tokens.

• 1Audit a project's `console.log` calls and replace them with a proper logger.
• 2Adopt log levels (debug, info, warn, error) and use them consistently.
• 3Ensure logs never include passwords, tokens, or other sensitive data.