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

@alu0101017396/addlogging

v0.4.18

Published

Update the code passed with console logs

Downloads

51

Readme

addLogging

A small library providing a method that put a console.log after each function with a description of it.

Installation

npm install @alu0101017396/addlogging --save

or

npm install --global @alu0101017396/addlogging 

Usage

How to use the package as a library

Add the followin lines to the head of your program:
let logging_espree = require('@alu0101017396/addlogging');
let addlogging = logging_espree.addLogging; The function addLogging can receive one or two parameters, the first one is a string with the code that will be transform; and the second one is an optional pattern that will filter the function names that are parsed.
An example of use would be:

  let logging_espree = require('@alu0101017396/addlogging');  
  let addlogging = logging_espree.addLogging;  
  let declared = addlogging(`function foo(a, b) {  
    var x = 'blah';  
    var y = function () {  
        return 3;  
    }();  
  }    
  foo(1, 'wut', 3);`);  
  console.log("\n\nNormal Function: ")  
  console.log(declared); 

With the following output:

  Normal Function:
  function foo(a, b) {
    console.log(`Entering foo(${ a }},${ b }}) at line 1`);
    var x = 'blah';
    var y = function () {
        console.log(`Entering <anonymous function>() at line 3`);
        return 3;
  }();
  }
  foo(1, 'wut', 3);

How to execute

This program contains four options:
-V, --version output the version number
-o, --output file where is the output
-p, --pattern <function_name> name of the functions that are parsed
-h, --help output usage information
to use it put in bash:
$ addlogging <filename> [options]

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.

Tests

If you change any functionality of the package you can add tests to the tests directory and run them with:
npm test

Documentation

https://ull-esit-pl-2021.github.io/espree-logging-module-alu0101017396/

Release History

  • 0.2.4 Initial release
  • 0.3.9 Patten addition
  • 0.4.14 Executable addition