npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

log3

v1.0.6

Published

Easy logging for node.js, with automatic file/line output

Downloads

17

Readme

log3

npm Version

Easy logging for node.js, with automatic file/line output.

This module was inspired by log2 by Andrew Chilton.

Installation:

npm install --save log3

Usage example:


const log = require('log3')({ out: 'server.log' });

log.debug('A log used for debugging');
// 2016-06-28T03:14:20.000Z | DEBUG | testDebug (/test.js:1:1) | A log used for debugging

log.info('This is just a nice-to-know');
// 2016-06-28T03:14:20.000Z | DEBUG | testDebug (/test.js:2:1) | This is just a nice-to-know

log.warn('Something went wrong, but we can keep on going.');
// 2016-06-28T03:14:20.000Z | DEBUG | testDebug (/test.js:3:1) | Something went wrong, but we can keep on going.

log.error('An error occured... Some explanation here');
// 2016-06-28T03:14:20.000Z | DEBUG | testDebug (/test.js:4:1) | An error occured... Some explanation here

log.fatal('A fatal error occurred, cannot proceed.');
// 2016-06-28T03:14:20.000Z | DEBUG | testDebug (/test.js:5:1) | A fatal error occurred, cannot proceed.

log.debug('A log used for debugging, specifying a custom origin', 'server.js, start()');
// 2016-06-28T03:14:20.000Z | DEBUG | server.js, start() | A log used for debugging, specifying a custom origin

log('A log with a custom level', 'hey', 'server.js, test()');
// 2016-06-28T03:14:20.000Z | HEY   | server.js, test() | A log with a custom level

log.end(); // Closes the writable stream (To file etc.)

The options you can pass are:

Name | Type | Default | Explanation ---- | ---- | ------- | ----------- timestamp | boolean | true | Log the timestamp out | Stream|String|? | process.stdout | A stream or a filename to output to title | boolean | false | Log current process title pid | boolean | false | Log current process id hostname | boolean | false | Log current machine name console | Array.<String> | ['fatal'] | Array of levels that are outputted to console too autoorigin | boolean | true | Will try to autodetect origin of log call origin | String | null | Predefined origin to log, when autoorigin is disabled

Contributing

If you have anything to contribute, or functionality that you lack - you are more than welcome to participate in this! If anyone wishes to contribute unit tests - that also would be great :-)

Me

  • Hi! I am Daniel Cohen Gindi. Or in short- Daniel.
  • [email protected] is my email address.
  • That's all you need to know.

Help

If you want to buy me a beer, you are very welcome to Donate Thanks :-)

License

All the code here is under MIT license. Which means you could do virtually anything with the code. I will appreciate it very much if you keep an attribution where appropriate.

The MIT License (MIT)

Copyright (c) 2013 Daniel Cohen Gindi ([email protected])

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.