Thanks Tim. Based on what you're saying I'm leaning to just leaving the
console.log statements in there. Though, I'm a little unclear on how you'd
actually go about overriding console.(log|warn|error) etc. in client code.
Are you able to provide an example of how you'd do it?
Something like this in my client code doesn't work because my winston
config has the console logger transport setup which consequently blows the
call stack:
console.log = function(msg) {
logger.info(msg);
};
Dave
On Tuesday, August 7, 2012 7:39:59 AM UTC-7, Tim Caswell wrote:
>
> It's only "bad form" if it doesn't fit your use case. Every situation
> is different. That's the nature of software. I tend to write mostly
> small libraries and micro-sites. Winston is overkill for me. I don't
> know what's best for other people because I'm not in their shoes.
>
> On Tue, Aug 7, 2012 at 12:18 AM, kuhnza <[email protected]> wrote:
> > Interesting, thanks for that...what do you think about using something
> like
> > winston (which we currently use for all our custom stuff)? Do the same
> > principle still apply, or is it bad form to use third-party logging in
> libs?
> >
> > Dave
> >
> >
> > On Monday, August 6, 2012 8:45:07 PM UTC-7, Tim Caswell wrote:
> >>
> >> I use console.log. I override the function when I want to redirect the
> >> output.
> >>
> >> On Mon, Aug 6, 2012 at 3:08 PM, kuhnza <[email protected]> wrote:
> >> > One thing I am keen to know right off the bat is what's the standard
> >> > practice for logging within node libraries? Right now mule simply
> uses
> >> > console.log but I don't think this is an ideal solution.
> >> >
> >> > What are others doing here?
> >> >
> >> >
> >> > On Monday, August 6, 2012 10:32:52 AM UTC-7, kuhnza wrote:
> >> >>
> >> >> Hey guys & girls,
> >> >>
> >> >> First time open sourcing something for the node community. Hope some
> >> >> find
> >> >> it useful. You can get it here:
> >> >>
> >> >> https://github.com/Hubify/node-mule, or here;
> >> >> npm install mule
> >> >>
> >> >> We created it for use at Hubify after trying some of the other
> options
> >> >> out
> >> >> there such as Q-Oper8 and found they weren't particularly up to date
> or
> >> >> suited to our problem.
> >> >>
> >> >> We'd love to hear your suggestions on how it could be made it
> better.
> >> >>
> >> >> Cheers,
> >> >> Dave
> >> >
> >> > --
> >> > Job Board: http://jobs.nodejs.org/
> >> > Posting guidelines:
> >> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> >> > You received this message because you are subscribed to the Google
> >> > Groups "nodejs" group.
> >> > To post to this group, send email to [email protected]
> >> > To unsubscribe from this group, send email to
> >> > [email protected]
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/nodejs?hl=en?hl=en
> >
> > --
> > Job Board: http://jobs.nodejs.org/
> > Posting guidelines:
> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> > You received this message because you are subscribed to the Google
> > Groups "nodejs" group.
> > To post to this group, send email to [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]
> > For more options, visit this group at
> > http://groups.google.com/group/nodejs?hl=en?hl=en
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
