unstale

npm / electron-log

electron-log

What changed in electron-log 5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-23.

8 breaking3 new APIs and options

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.4 on npm

electron-log 511 changes

Breaking changes 8

  • The file transport option archiveLog was renamed to archiveLogFn.

    5.0.0release notes

  • The call signature changed from log.create(logId) to log.create({ logId }).

    5.0.0release notes

  • All logs are now written to main.log; renderer logs can be directed to a separate file by overriding resolvePathFn.

    5.0.0release notes

  • The remote transport option transformBody was renamed to makeBodyFn({ logger, message, transport }).

    5.0.0release notes

  • The library now requires Node.js 14+ or Electron 13 at least.

    5.0.0release notes

  • The remote transport option onError was renamed to processErrorFn({ error, message, request }).

    5.0.0release notes

  • Renderer processes now send log data to the main process through IPC, so only the main logger can be configured.

    5.0.0release notes

  • The file transport option resolvePath was renamed to resolvePathFn.

    5.0.0release notes

New APIs and options 3

  • Electron event logging was implemented to simplify app debugging.

    5.0.0release notes

  • A property for each transport configures transformations performed on message data.

    5.0.0release notes

  • The console transport adds a writeFn callback, which by default passes message.data to console.log.

    5.0.0release notes