Installations
npm install logatim
Score
78
Supply Chain
99.5
Quality
75.8
Maintenance
100
Vulnerability
100
License
Developer
Developer Guide
Module System
CommonJS
Min. Node Version
Typescript Support
No
Node Version
4.4.4
NPM Version
2.15.6
Statistics
192 Stars
72 Commits
3 Forks
5 Watching
3 Branches
4 Contributors
Updated on 06 Nov 2024
Bundle Size
5.47 kB
Minified
2.12 kB
Minified + Gzipped
Languages
JavaScript (98.94%)
HTML (1.06%)
Total Downloads
Cumulative downloads
Total Downloads
123,811
Last day
0%
172
Compared to previous day
Last week
27%
2,604
Compared to previous week
Last month
3,424.8%
14,346
Compared to previous month
Last year
405.3%
16,085
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Logatim
Logatim is an isomorphic logger which implements log levels and ANSI 16 styles.
Finally you can use the same logger for the server and client side of your applications. Log for developers using colors, underlines, etc. in order to transform the terminal in an authentic debugger machine. And log for production managing exactly what have and what have not to be outputted.
Demo
If you're excited about this and want to try it right now you have 2 options:
- Copy the dist/logatim.umd.min.js and paste it on the browser console.
- Access to our official sandbox at Runnable.
- Go to the Logatim website and open the console :)
Why?
I've been coding for a long time and I've always feel that we need a better approach to the logging issue. I've researched a lot about the available logger modules and I've even run a questionary about this topic. After this inquiry I think that the most suitable logger should combines these six elemental features:
- 1. Free outputs: it should be able to stream the logs anywhere and to multiples targets at the same time.
- 2. Levels: it should handle which levels should be printing or not.
- 3. Styles: as a very useful resource while developing, it should implements colors, bolds, etc.
- 4. Cross-platform: it should run in all the browsers and all the node versions. This includes the different Javascript specifications.
- 5. Human-like: it shouldn't have been any learning curve, nor complex configurations; just require and go.
- 6. Customizable: it should accept addons and plugins in order to keep a light and powerful core which can be extended for specific situations.
Installation
Choose one of the following options:
- Install it via npm:
npm install logatim --save
- Download from the
dist
folder the stand-alone specification which fits better for you:var
,commonjs
,umd
oramd
. Note that the installation vianpm
uses the umd pattern so should work in all the environments.
Features
- Logatim has colors, background colors and text styles.
- Implements the five native console logging methods: trace, debug, info, warn and error. And also the silent mode.
- Production ready for server and front-end sides. Learn one, implement everywhere.
- Super lightweight, weighs in at 1.1KB minified and gzipped.
- Implements human-like code style:
logatim.green.bold.info('super sexy')
- By using the native
console
object so you'll keep the stack trace and line numbers. - Works with multiple Javascript specifications: AMD, UMD, CommonJS and declaring a
var
directly.
Server support
- All node versions via
npm
Browser support
(Only the versions which had been introduced the console colors support. We cannot do magic... yet.)
- Chrome
- Edge
- Firefox
- Internet Explorer 8+
- Opera
- Vivaldi
- Safari
Usage
The logatim API is tend to be extremely minimal and human-like. It has two different kind of options: the styling and the leveling ones. Logatim consists in:
Styles
- Use the ANSI 16 styles in a concatenable way:
1const logatim = require('logatim') 2 3logatim.blue.bgYellow.bold.info("It's like reading english") 4 5// and the next print is completely independent; zero memories 6logatim.green.info('No background color nor bold here') 7 8// you can concat different styles 9logatim.red('R').green('G').blue('B').info() 10 11// also, of course you can print without any style 12logatim.info("I'm a boring log") 13
-
The colors available are: black, red, green, yellow, blue, magenta, cyan, white, gray and grey (fixing humans).
-
The background colors available are: bgBlack, bgRed, bgGreen, bgYellow, bgBlue, bgMagenta, bgCyan, bgWhite, bgGray and bgGrey.
-
The sets available are: bold, dim, italic, underline, blink, inverse, hidden, strikethrough (Almost no browser supports blink and inverse is not supported when printing on the browser's console).
Levels
- Use the five
console
native logging methods (aka levels):
1const logatim = require('logatim') 2 3// sorted from bottom in the bubbling logging scale 4logatim.trace('Good for track pathways') 5logatim.info('Good while developing')
Note that the log methods are end-like functions. Therefore they are not returning a Logatim instance, so they're not chainable.
- And change the current level using the get/set methods:
1const logatim = require('logatim') 2 3logatim.getLevel() // by default is WARN 4logatim.debug("I won't be printed") // because debug is lower than warn 5logatim.setLevel('info') 6logatim.debug("I'll be printed") // because debug is greater than info
- Leveling also ensures that your logs don't break anything, even if there's not a
console
object (I'm staring at you IE) it will silent fallback to the safest print possible.
Contributing
Please feel free to raise issues, make contributions or suggestions/requests. Remember that we follow standard code style and the continous integration pattern so any pull request should run the tests first.
1git clone https://github.com/edravis/logatim.git 2cd logatim 3npm install 4# edit logatim 5 6# when done 7npm test 8npm run build 9# send the PR, yaaay!
Todo list
If you feel that the force is strong in Logatim keep an eye to the todo list and maybe you find something you're willing to make ;)
- Add the possibility to stream the output elsewhere than the console.
- Add the CI for client-side environments.
- Add Logatim to other source providers: bower, a CDN, etc.
- Write the technical in-code documentation.
- Allow custom prints depending on the level or globally.
Dat name, tho
Logatim comes from a combination of the words log and verbatim. The first one is obviously referred to the cutten trunk... lol no, it's for the coding logfiles. And the second one is a Latin term that can be translated as word for word. So, the term Logatim could be loosely translated as log for log.
License
The code is available under the ISC license.
Handcrafted by @sospedra_r / sospedra.me.
With contributions from:
- [be the first here, make a PR!]
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE.txt:0
- Info: FSF or OSI recognized license: ISC License: LICENSE.txt:0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Score
3
/10
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More