Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
An extremely simple (but powerful) logging system for NodeJS and browser.
npm install acho
If you want to use it in the browser (powered by Browserify):
bower install acho --save
and later add it to your HTML:
<script src="bower_components/acho/dist/acho.js"></script>
Acho exports itself according to UMD best practices, which means that no matter where you are using the library, you get a version tailored for your environment.
If you're using a module loader (or Node), simple require the library as you would any other module.
If you're using a browser, the library falls back to attaching itself to window as the global Acho
.
var Acho = require('acho');
var acho = Acho();
var acho = Acho();
I don't use personally use AMD, so I can't conjure an example, but it should work fine as well.
It's time to use it!
acho.info('hello world');
// => 'hello world'
All public methods are chainable:
acho
.info('hello world')
.error('something bad happens');
// => 'info: hello world'
// => 'error: 'something bard happens'
Maybe you don't want to output the message, but store it for later use:
acho.push('success', 'good job!');
console.log(acho.messages.success);
// => ['good job']
If you want to print previously stored messages, just call the method print
:
acho.print()
// => 'success: good job!'
You might be thinking: Can I combine both, to store and both print a message? Absolutely!
acho.add('info', 'this message is printed and stored');
// => 'info: 'this message is printed and stored'
console.log(acho.messages.info)
// => ['this message is printed and stored']
Establishing the loglevel is a good way to filter out undesired information from output. The available levels by default are:
error
: Display calls to .error()
messages.warn
: Display calls from .error()
, .warn()
messages.success
: Display calls from .error()
, .warn()
, success()
messages.info
: Display calls from .error()
, .warn()
, success()
, info()
messages.verbose
: Display calls from .error()
, .warn()
, success()
, info()
, verbose()
messages.debug
: Display calls from .error()
, .warn()
, success()
, info()
, verbose()
, debug()
messages.silly
: Display calls from .error()
, .warn()
, success()
, info()
, verbose()
, debug()
, silly()
messages.Additionally exists two special levels:
silent
: Avoid all output.all
: Allow print all message types.The default log level is all
. You can define it in the constructor:
var acho = Acho({level: 'silly'})
or at runtime:
acho.level = 'debug';
You can completely customize the library to your requirements: changes colors, add more types, sort the priorities... the internal structure of the object is public and you can edit it dynamically. You have the power.
By default the messages structure is brief: Just the message type followed by the message itself.
But you can easily modify the output. For example, let's add a timestamp to each message:
acho = Acho({
color: true,
level: 'silly',
// Customize how to print the 'type' of each message
outputType: function(type) {
return '[' + type + '] »';
},
// Customize how to print the message.
// Add things before and/or after.
outputMessage: function(message) {
return Date() + ' :: ' + message;
}
});
This results in your awesome output:
acho.info('I am hungry');
// => '[ info ] » Fri Mar 13 2015 18:12:48 GMT+0100 (CET) :: I am hungry'
In addition, you can use a custom keyword to use as logging level instead of print the logging level. Just provide keyword
parameter in the constructor. Providing it in the above example as { keyword: 'acho' }
the result is:
acho.info('I am hungry');
// => '[ acho ] » Fri Mar 13 2015 18:12:48 GMT+0100 (CET) :: I am hungry'
If you need customize more the output you can setup .print
.generateMessage
(see below) that are a more low level methods for generate and print the output message.
Create a logger. Available options:
Default: loglevel
Instead of print the type log level, print the keyword. By default this behavior is not activated.
You can pass the special keyword symbol
to show an unicode icon. This is special behavior for CLI programs.
Default: false
Prints timestamp between log from the same level.
Default: false
.
Enable or disable colorized output.
Default: all
Provides the logging level.
You can provide the types and priorities.
Provides a function that determines how to print the messages. By default uses .generateMessage
for generate the mesage that will be outputted.
Default: console.log
Defines what happens with the log message.
Provides a function to customize the type in the output.
Provides a function to customize the message in the output.
Provides a function that generate the message to be outputted. It combines other internal methods for generate the output (as .isPrintable
or .colorize
) and normally you are not interested in the definition of it, but you can provide it as option as well.
Provides a function used to generate the type message.
Store a message of given type
internally.
Store a message of given type
internally and also output it.
For each level you have a function following the pattern:
Prints all messages internally stored.
For each log level that you declared in the constructor (or the default log levels provides by the library if you don't declare nothing) will be created a function with the same name to output a message with these log level.
MIT © Kiko Beats
FAQs
The Hackable Log
We found that acho demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.