question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Environment Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

CLI: 5.2.0 Cross-platform modules: Android Runtime: 5.2.0 iOS Runtime: 5.2.0 Plugin(s): How can I prevent application logs in the console output?

CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(NativePage)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativeflexboxlayout)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativegridlayout)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativelabel)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativegridlayout), ElementNode(nativelabel))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativestacklayout)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativebutton)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativestacklayout), ElementNode(nativebutton))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativebutton)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativestacklayout), ElementNode(nativebutton))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativebutton)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativestacklayout), ElementNode(nativebutton))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativebutton)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativestacklayout), ElementNode(nativebutton))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> CreateElement(nativebutton)'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativestacklayout), ElementNode(nativebutton))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativegridlayout), ElementNode(nativestacklayout))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativeflexboxlayout), ElementNode(nativegridlayout))'
CONSOLE LOG file:///app/vendor.js:33228:14: '{NSVue (Vue: 2.5.17 | NSVue: 2.0.2)} -> AppendChild(ElementNode(nativepage), ElementNode(nativeflexboxlayout))'

This makes debugging much more difficult. An option of some sort to disable the CreateElement / AppendChild messages would be welcomed. Through some sort of flag of course to enable should they be needed but at this point they seem clutter looking for real console log messages.

Thanks!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:10
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

6reactions
maxorlovskycommented, Nov 21, 2019

Proposing to have a Vue.config.suppressRenderLogs = true to suppress just rendering logs in my PR, but still leave Vue warns and console errors to be displayed.

5reactions
SpurguXcommented, Oct 23, 2019

The disadvantage with Vue.config.silent = true is that it indeed suppresses more than just the UI creation messages.

For instance warnings such as the following will be omitted. [Vue warn]: Error in render: "TypeError: _vm.someObject.someFunction is not a function"

Not seeing the warnings slowed down debugging for me so I turned the logs back on. Would be nice to get rid of the excess logs though…

Read more comments on GitHub >

github_iconTop Results From Across the Web

CWE-779: Logging of Excessive Data (4.9) - MITRE
The software logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack....
Read more >
Troubleshooting excessive logging (syslog)
To investigate excessive logging (system logs -> all) , the idea is to look for a pattern to see what is appearing most...
Read more >
How to know when there's too much logging messages?
Were the "excessive logs" a bad practice? Say that to your clients when you have to prove that the error came from the...
Read more >
10 Mistakes To Avoid For Effective Logging In Your Service
Avoid excessive error logging when system is down. Error logs tend to be large and errors happen at the same time so make...
Read more >
what is the impact of logging (or excessive logging) of ...
Asynchronous logging : it will take more memory and some more thread to handle. If your application interrupts, you will probably miss some...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found