build(deps): bump electron-log from 5.2.2 to 5.3.2

[dependabot]

Bumps electron-log from 5.2.2 to 5.3.2.

Changelog

Sourced from electron-log's changelog.

Changelog

5.2.4

• Add Buffering feature.

5.2.0

• fix: #436 log.log isn't bound to log.info. Previously, it was processed with non-existent log level.

5.1.0

• New entry point for NW.js / Node.js apps: 'electron-log/node'

5.0.0

Core

• Now it's a time to use modern ES instead of ES5. It was a joy to use old-fashioned ES5, but since the library grows it becomes harder to follow its restrictions. Starting from v5 the library requires Node.js 14+ or Electron 13 at least.
• Now a renderer process just sends log data to the main through IPC, so only the main logger can be configured. See initialize for more information
• A new tranforms property is added for each transport. It allows to configure transformations preformed on message data. See transforms for more information.
• log.create(logId) is replaced by log.create({ logId })

File transport

• archiveLog options is renamed to archiveLogFn
• resolvePath options is renamed to resolvePathFn
• All logs are written to main.log file. If you want to write renderer logs to a separated file, you can do that by overriding resolvePathFn

Console transport

• writeFn callback is added. By default, it just passes message.data to console.log function

Remote transport

• onError is renamed to processErrorFn({ error, message, request })
• transformBody is renamed to makeBodyFn({ logger, message, transport })

Electron event logger

... (truncated)

Commits

• 670685c 5.3.2
• dc90cc2 fix(main): Deprecation message after upgrading Electron to 35, fixes #459
• 2bea837 5.3.1
• 1133619 fix(renderer): Inconsistent console.format callback type, fixes #458
• 17e8e91 feat(docs): Use logger in preload, closes #453
• f7a20b5 fix(e2e): Downgrade vite to support old nodejs
• bf49ba7 5.3.0
• 6f1b4f8 fix(renderer): Renderer transport should support transforms, fixes #452
• 5fbc131 fix: check web content is crashed or not before call ipc send (#448)
• 2520d8a fix(e2e): Run with --no-sandbox flag on linux
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #42.