-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use util.inspect with depth: null for traceAny on node.js #5
Conversation
It seems like this way of checking whether we're running on node.js doesn't work (with node v0.10). I'll see if I can find something better. @hdgarrood did you ever have this problem with |
Maybe we make it simpler and just check if |
I don't think we should worry about node 0.10 if it makes things significantly harder; we don't with the purescript-node libraries. I think we should support Node 4 but not older versions. |
Okay, I've rewritten the commit so it checks for |
Doesn't work like this. Seems like you have to import |
You also have to import util on node 6, it seems. Maybe it's just in the repl that the node api modules like |
Oh, okay. And I guess I'll also have to use |
Also, since we're here, maybe we should consider providing a version of You shouldn't need |
Okay, now I'm really out of ideas. It just keeps saying that everything I check for being undefined is undefined, and that is somehow is an error. What's going on here? :/ |
Ah, that's the linter. You have to tell the linter separately that a global |
Thanks, should work now then. Actually I got the same error locally from my linter editor plugin, I just didn't expect that the server reported linter errors as build fails. |
Because currently recursive types without a `Show` instance are pretty much non-printable.
Aaand another rewrite... This time the linter didn't like my code style (but only on the server, no local errors) ^^° |
Finally! :) |
Thanks, sorry this turned out so painful! 😄 |
No problem, at least I learned something :) |
That might be useful, but I think it should be in a seperate package that wraps the whole |
^ agreed. The depth argument would only apply on node too, as when you |
Because currently recursive types without a
Show
instance are pretty much non-printable.