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

@alu0101244587/addlogging

v1.0.2

Published

PL ULL 2021 - Espree Logging

Downloads

13

Readme

addLogging

Index


Installation

Local instalation

npm install @alu0101244587/addlogging

npm i @alu0101244587/addlogging

Global instalation

npm install -g @alu0101244587/addlogging

npm i -g @alu0101244587/addlogging

To consider

When we install on local, to test our module, we need to use, for example, to open the help usage:

npx addlogging -h

But if we install as global, we could do this:

addlogging -h

go back up


Command line options

'-V' [version]
'-h, --help' [help]
'-o, --output' <filename>' [specify an output file]
'-p, --pattern <function>' [specify the name of a function]

go back up


Usage Examples

Once we had install this module, we could try first this module using the option -h to recive some help:

npx addlogging -h

Also it is a good idea see if the version that we have download is who is working on our computer (-V option).

npx addlogging -V

Now, we are going to try to seems if our program is working correctly with files, for that, we call our module with .js:

console.log( 'Hello, World!');

const first = () => {
	alert('hi!')
}


function foo( hello ) {
	return hello + 'word';
}
$ addlogging test/hello-world.js

All right, let's try sending the output to an output file:

console.log('Hello, World!');
const first = () => {
    console.log(`Entering <anonymous function>() at line 3`);
    alert('hi!');
};
function foo(hello) {
    console.log(`Entering foo(${ hello }) at line 7`);
    return hello + 'world';
}
$ addlogging test/hello-world.js -o test/output.js

With pattern we tell him wich function to analize as follows:

Previously we know that on hello-world.js exist a function called 'foo'. If it does not exist, our module return the original code.

console.log('Hello, World!');
const first = () => {
    alert('hi!');
};
function foo(hello) {
    console.log(`Entering foo(${ hello }) at line 7`);
    return hello + 'world';
}
$ addlogging test/hello-world.js -p foo

Let's see pattern and output working at the same:

console.log('Hello, World!');
const first = () => {
    alert('hi!');
};
function foo(hello) {
    console.log(`Entering foo(${ hello }) at line 7`);
    return hello + 'world';
}
$ addlogging test/hello-world.js -p foo -o test/output.js

To keep an module organization, try to keep testing files on /test.

go back up


Release History

  • 0.1.1 initial version
  • 0.1.2 some structure changes who does not affect to module funcionality
  • 0.1.3 superficial changes
  • 0.1.4 correcting some issues
  • 0.2.0 first big modification, changing some important functionalities and adding new ones
  • 0.2.1 pre-latest version, working as 0.2.0 but changing some bugs on module dependencies
  • 1.0.0 first complete usable version
  • 1.0.1 changes on the module explain
  • 1.0.2 latest: changes on usage examples

go back up


@luisleonjeremy

Search for MIT licence on node_modules/@alu0101244587/addlogging

go back up