-
Notifications
You must be signed in to change notification settings - Fork 62
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
process.stdout.write does not output to DevTools console? #30
Comments
Did you checked the devtools console? |
a normal |
Not very beautiful but I got output to terminal console I have noticed some other things regarding to that as described at electron/electron#2390 |
@BlackBarn do you see any output like on my console? Otherweise I would like to change the issue title. |
My guess is that the isbrowser method does not work correct within electron environment. https://github.com/trentm/node-bunyan/blob/master/lib/bunyan.js#L407 can you clarify this? |
Sorry, I was preoccupied there for awhile. I'm glad it seems to be working and sorry for causing any problems. When I have time i'll dig into my implementation a bit more to see if I can find my issue. Thanks for all your work on the project! |
Absolutely no problem, feel free to submit issues! Well I am not shure it isjust a guess. So if you want. Would be nice to keep us up-to-date here. |
I'm having the same issue. Logs that are piped to |
Can you publish a reproducable code example? |
If you clone the Kibana repo (https://github.com/elastic/kibana) and run Note that these logs are ultimately getting sent to process.stdout in |
Ty, I will check this out this weekend .
|
Sir @BlackBarn I will not find time this we again :\ pls can u try #60 (comment). there where a lot of improvements by the creators of Electron regarding console log. Hope this will help u. You can try to upgrade electron within iron -node |
Hi @s-a , I tried upgrading Electron, unfortunately it didn't make a difference. |
@Bargs ty for the attempt. Could you please open an issue at the electron repo? |
Yes I'll try to get to that this weekend. Thanks! |
@Bargs I plan a new release this weekend. Any news about this topic? |
Hi @s-a. I have to admit this slipped my mind. I haven't been working with iron node much recently, if I get back into it I'll make sure to follow up. |
Hi! I'm having the same issue. Any updates on this? I'm happy to make an issue on the electron repo, but haven't used electron and wouldn't know how to properly describe what we think is happening. |
I believe you experience this issue when using console output log streams. I never used this. But it seems you have reproducable code there? |
Yeah, when using streams process.stdout like this: process.stdout.write("doesn't work")
console.log('works') |
Ok. Could you plz send an issue to the creator s of electron? |
Per electron/electron#3979 (comment) to get output in the console via process.stdout.write = console.log.bind(console); Can you confirm? |
@willhoag thanks for clarify! Yes it sounds very reasonable. You can test if this works when you put this code into your startup script. I will implement the code into iron-node core if this works for you. I would test it but realy never used |
Please use https://github.com/s-a/iron-node/releases/tag/v2.1.4 for further testings. |
Confirming that the update produces output using process.stdout.write in the console. Thx! |
The app i was testing with uses bunyan which logs to the console. However when running with iron-node the console/stdout is suppressed for some reason.
The text was updated successfully, but these errors were encountered: