Read the statement by Michael Teeuw here.
Integrate logging framework
-
What do you think about using a logging framework like winston (the fork in the link seems to work with electron)?
I don’t know if my debugging methods are wrong, but currently I’m debugging with a ssh session, having
tail -ffor error and out logs (orpm2 log) and via web browser console to my mirror’s IP on port 8080 to catch logs from the main application, thenode_helperand a fetcher class.In my opinion this method kinda inconvenient. I’d like to have all logs (even the ones from fetcher modules and
node_helpermodules) in one place.If anyone has a better debugging method I’d appreciate any help and advice.
If all of you are doing it like me, I’d start integrating a logging framework for the whole node.js application, which covers global logging over modules and make a PR when ready (and of course if @MichMich wants this).What do you think? Or do you have any advices for me?
-
I agree this should be improved. In the front end I already used a placeholder/proxy which we can simply adjust. (See the Log object).
In the backend such a proxy is not yet available. I think the best approach is adding a similar proxy so that we easily can swap out any 3rd party framework.
-
Any update?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login