Bump electron-log from 4.3.0 to 5.1.5 in /electron

[dependabot]

Bumps electron-log from 4.3.0 to 5.1.5.

Changelog

Sourced from electron-log's changelog.

Changelog

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

To simplify app debugging the Electron event logging was implemented.

4.4.0

• Disable auto-loading of electron-log in the main process for using by ipc transport

Commits

• ecb92d8 5.1.5
• 500ccab fix: Add workaround when appName can't be read, fixes #418
• 957406d chore: Exclude specs from publishing
• df076c8 5.1.4
• a54cabc 5.1.3
• 40b03bc fix: Error when calling readAllLogs, fixes #414
• 58dcfae chore: Add DataDog transport
• db9f9d6 chore(docs): Add processType to ELECTRON_LOG IPC sample
• 9668b39 5.1.2
• 35f7184 fix(ipc): Message duplicated in dev console, fixes #407
• 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 #101.