Logging in JavaScript Applications: Best Practices for Beginners

Logging in JavaScript Applications: Best Practices for Beginners

Logging is one of the most important yet often underestimated tasks when developing web applications in JavaScript, especially in the Node.js environment. Properly configured logging helps not only debug code during development but also identify issues in production, analyze user behavior, and track system performance. In this article, we will cover the best practices for logging in JavaScript applications that will help you, as a beginner developer, avoid common mistakes and build a reliable monitoring system.

Why is logging necessary?

Imagine your application is running on a server and suddenly stops responding. Without logs, you would be like a blind kitten — guessing what went wrong. Logs provide detailed information about every step of program execution: what requests come in, what errors occur, what data is being processed. This is an indispensable tool for:

\n
• Debugging — quickly finding and fixing errors.
\n
• Monitoring — tracking application health in real time.
\n
• Auditing — recording user actions for security.
\n
• Performance — identifying bottlenecks and slow queries.
\n

Basic logging levels

To structure logs, importance levels are used. The most common standard is RFC 5424, which includes the following levels (from most critical to least):

\n
• ERROR — critical errors requiring immediate intervention (e.g., database failure).
\n
• WARN — warnings about potential issues (e.g., memory limit exceeded).
\n
• INFO — important application events (server startup, successful user registration).
\n
• DEBUG — debugging information for developers (variable values, algorithm steps).
\n
• TRACE — extremely detailed tracing (rarely used, mainly for diagnosing complex bugs).
\n

Using levels allows flexible filtering: in production, only ERROR, WARN, and INFO are usually kept, while DEBUG is enabled only when necessary.

Libraries for logging in Node.js

Although you can use the built-in console.log, this is insufficient for serious projects. Manual formatting, level management, and file output are too time-consuming. Specialized libraries come to the rescue. Let's look at the two most popular ones: Winston and Pino.

Winston: versatile and powerful

Winston is the de facto standard for logging in Node.js. It supports many transports (where to output logs: console, file, database, external services), formats, and levels.

Example of Winston setup:

const winston = require('winston');\n\nconst logger = winston.createLogger({\n  level: 'info',\n  format: winston.format.combine(\n    winston.format.timestamp(),\n    winston.format.json()\n  ),\n  transports: [\n    new winston.transports.Console(),\n    new winston.transports.File({ filename: 'error.log', level: 'error' }),\n    new winston.transports.File({ filename: 'combined.log' })\n  ]\n});\n\n// Usage\nlogger.info('Server started');\nlogger.error('Database connection error', { error: err.message });

Pino: ultra-fast and lightweight

Pino is positioned as the fastest logger for Node.js. It is ideal for applications with high performance requirements. By default, Pino outputs logs in JSON format, which is convenient for parsing.

Example of Pino setup:

const