Choose appropriate log levels

Select log levels based on the intended audience and actionability of the message. Use debug for internal development information that helps with troubleshooting, warn or error for user-actionable issues, and avoid logging messages that add noise without providing value to the user.

Key principles:

• Don’t log messages users cannot act upon - this creates noise in console output
• Use debug logs for internal state and development information
• Ensure log formatting doesn’t depend on specific log levels being enabled
• User-facing logs should provide clear, actionable information

Example:

// Good: Internal information for developers
debug('launch project')

// Good: User-actionable warning
logger.warn(stripIndent(msg))

// Avoid: Noise that users can't act on
console.warn(`Could not get the original source file from line "${line}"`)

When in doubt, prefer debug logs for internal information and reserve user-facing logs for messages that require user attention or action.