If a contrib node can do a job why add to core? adding to core means that it has to be maintained by core contributor, needs to be updated with new versions of nodejs, needs to be debugged if in error, is harder to update/extend ... etc
I say this as someone who sees a slim core and fat contrib as preferrable approach - i.e. something like the linux kernel. If contrib nodes become outdated, then fork and update - as Dave said above.
I won't be saying this if NR didn't have such good support for contribs and plugins - I would extend this framework so that contrib nodes can do more. I.e. as in this case, there is no documentation how to capture the debug messages before they sent to the frontend and that API might change with future versions - I would solidify that API and maintain that instead of maintaining the node that uses that API - in the core.
But that's my perspective.
Isn't there a debug-panel filter mechanism for that? Perhaps extend that so it's possible to filter a set of individual nodes - if mute is the desired action.
