electron-log
electron-log copied to clipboard
Just a simple logging module for your Electron application
Would by nice the 'scope' value is included in transformBody of the remote transport.
Apologies if I'm missing something obvious, but I'm having a tough time figuring out how to enable the IPC transport from the renderer in a packaged application. Setting the log...
Error: ```RangeError: Maximum call stack size exceeded at Object. (/Users/workspace/node_modules/electron-log/src/transform/object.js:20:19) at JSON.stringify () at toJSON (/Users/workspace/node_modules/electron-log/src/transform/object.js:137:26) at /Users/workspace/node_modules/electron-log/src/transform/index.js:47:14 at Array.reduce () at Object.transform (/Users/workspace/node_modules/electron-log/src/transform/index.js:45:23) at transport (/Users/workspace/node_modules/electron-log/src/transports/ipc.js:34:23) at runTransport (/Users/workspace/node_modules/electron-log/src/log.js:44:5)...
![截屏2022-07-13 11 23 53](https://user-images.githubusercontent.com/9758711/178644173-6548c877-58d5-4940-9ddd-7d25aa0978db.png) Therefore, it is strange to print null in the Console
when trying to import electron-log with global sandbox enabled I get this error in the preload script which is causing it to fail to load. ``` Error: module not found:...
I use Electron v14.2.5 + Vue v3.0.0. When renderer process has UI issue, (and Vue.js check it, I guess), then renderer.log file is quickly filled by ```[Vue warn]: Avoid app...
On module load, getPathVariables will call electron API https://github.com/megahertz/electron-log/blob/16b352634887d21d155bc6bcd5af09ac8bb129bc/src/transports/file/variables.js#L103 to get the logs folder which will cause a logs folder to be created before application has a chance to change...
Currently `console.js` in electron-log makes references to console functions (e.g `console.log`, etc.) during module initialization ([source](https://github.com/megahertz/electron-log/blob/35535062403df2c3ac6e73a5d5d8886adfcab861/src/transports/console.js#L7)). This can lead to problems if the application (or its libraries) then make replacements...
The implementation of asynchronous (sync = false) file logging doesn't guarantee the logs are written out in order. The (abbreviated) code looks like this: ```javascript writeLine(text) { ... this.asyncWriteQueue.push(text); this.nextAsyncWrite();...