New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deep debugger integration #1821
Comments
We currently do not have the bandwidth to implement or maintain this. Would you like to work on this problem? We can start a new repo or unarchive pino-inspector |
@mcollina, sure, but currently I'm not in resource to tackle with technical or ecosystem barriers. I'll need consultative help to effectively deal with it. ~ Roadmap:
|
I can't really help with the VSCode/Inspector part, but happy to answer questions on pino itself. |
@mcollina, |
In my case, when
pino
is used with vscode debugger (vscode-js-debugger
) logs are missed, but it can be fixed with"outputCapture": "std"
in thelaunch
configuration.However, when
"outputCapture": "std"
is used, the debugger sometimes randomly combine different logs (1-20) into one output record, as shown in the screenshot below:(Mouse hovered at "2")
This behavior makes it impossible to use VSCode filters feature in debugger console (especially when dealing with large amounts of prettified logs combined into one):
(This issue also reproduces when using pure console.log, so I believe this is nature of the
std
.)I noticed that there was a tool called pino-inspector in the past, it was not designed as well as it should have been, in my opinion:
1 - It shouldn't function as a serializer, it could be a pipeable transformer transport, similar to
pino-syslog
, to provide more flexibility.2 - Instead of just redirecting everything to
inspector.console.*
it could emitRuntime.consoleAPICalled
events withcontext
andstackTrace
to indicate the line from which the logs were originally sent (which is currently not possible with pino). (or withargs
to make objects foldable, don't know).3 - It should have its own place in the documentation, particularly in the Inspection section.
4 - It should not check inspector.url() because it's empty when VSCode debugger is attached.
Repro:
launch.json
The text was updated successfully, but these errors were encountered: