Question 1

How do I change the log file location in electron-log?

Accepted Answer

Use the resolvePathFn option on the file transport, like log.transports.file.resolvePathFn = () => path.join(customDir, 'logs/main.log'), to set a custom path, as shown in the README's file transport section.

Question 2

electron-log vs winston for Electron apps

Accepted Answer

electron-log is lighter and built specifically for Electron with multi-process support, while Winston is more feature-rich but requires extra setup for cross-process logging. Choose electron-log for simplicity and Winston for advanced needs like transports or formats.

Question 3

Does electron-log work in production builds?

Accepted Answer

Yes, but IPC transport is disabled by default in production to reduce overhead; you can enable it by setting log.transports.ipc.level to a log level. File and console transports remain active unless configured otherwise.

Question 4

How to send logs to a remote server with electron-log?

Accepted Answer

Use the remote transport by setting log.transports.remote.url to your endpoint and enabling it with log.transports.remote.level = 'info' or similar, as described in the remote transport docs—it sends JSON POST requests.

Question 5

Can electron-log catch unhandled promise rejections?

Accepted Answer

Yes, via log.errorHandler.startCatching(), which logs unhandled errors and rejected promises automatically, with options to customize behavior, as detailed in the 'Catch errors' section of the README.

Question 6

How to use electron-log in a renderer process without a bundler?

Accepted Answer

Access the global variable __electronLog, which contains log functions like info and warn, since direct imports may fail without bundlers, as mentioned in the renderer process usage notes.

electron-log

What is electron-log?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions