Skip to content

ideaq/halp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

HALP

If teh codez got u sad call for HALP!

halp

The idea is to have an awesome stack trace when ever we call halp() or halp(str) or halp(obj) etc.

Why?

Why do we need another logging library?

Top 5 Reasons

  1. Intuitive (don't make me think!) "works like console.log but much cooler" (no learning curve!);
  2. Sensible defaults means it "Works out of the box" & Nothing to configure until you want to use more advanced options.
  3. Clarity / Simplicity in both the code and tests (easier to understand for beginners)
  4. **

Sample HALP! User Quotes

"Wow! I didn't know that was possible! HALP! has completely changed how I write node.js apps!"

(this is what we want people to say...)

Philosophy

Sensible Defaults

Easy

  • output a little or as much as you want/need!
  • do not force people to *remember the order of arguments/parameters.
  • any number of arguments permissable.
  • intelligently

Evironment Variables as Settings

__line (global to help you debug)

Run with environment variables not config files.

### Output to Logstash

About

Bugs got you 😭 ? HALP will make you 😃

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published