A pretty logger for Electron apps that displays renderer process logs in the terminal.
Electron Timber is a logging library specifically built for Electron applications. It enables developers to see logs from both the main and renderer processes in the terminal, solving the common issue where renderer process logs are invisible during development. It provides a prettified, unified logging interface with features like custom logger instances and stream support.
Electron developers who need better visibility into their application's logging, especially when debugging multi-process issues or wanting consistent log output across main and renderer contexts.
Developers choose Electron Timber because it directly addresses Electron's logging limitations with a simple, focused API. It requires minimal setup, works out-of-the-box across processes, and offers just enough customization (like log levels and named loggers) without unnecessary complexity.
Pretty logger for Electron apps
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Solves Electron's key limitation by making renderer process logs visible in the terminal with clear 'main' or 'renderer' prefixes, as demonstrated in the usage examples where logs from both processes appear unified.
Provides familiar methods like log, warn, and error that mirror the console API, requiring minimal learning curve and easy adoption, as highlighted in the API section.
Allows creating named loggers with configurable options such as log level and ignore patterns, enabling fine-grained control for different app modules, as shown in the create() method documentation.
Can log each line from readable streams, such as child process output, directly to the console using streamLog, streamWarn, or streamError methods, useful for debugging subprocesses.
Lacks features for saving logs to files or databases, focusing solely on terminal output, which limits long-term debugging and production monitoring without additional tooling.
Requires Electron 30 or later, as stated in the README, making it incompatible with projects using older Electron versions, which could be a barrier for legacy apps.
Logs from the renderer process only appear if electron-timber is imported in the main process, adding an extra setup step that might be missed, as noted in the API documentation.