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

@adrianepi/addlogging

v2.0.6

Published

Module for addlogging (PL-2021)

Downloads

42

Readme

Espree

A small library providing utility methods to addLogging functions. This searchs and prints information about the functions in the input code.

Installation

npm install @adrianepi/addlogging --save

Usage

    var addLogger = require('@adrianepi/addlogging')
        addLogging = addLogger.addLogging,
        addLoggingPattern = addLogger.addLoggingPattern;

    var inputCode = `
        function foo(a, b) {   
          var x = 'blah';   
          var y = (function () {
              return 3;
          })();
        }     
        foo(1, 'wut', 3);
        `;
    
    // Function call without pattern
    console.log('\nOriginal funcion\n', inputCode, '\nAdded function details: \n', addLogging(inputCode));

    // Function call with pattern
    var myPattern = "foo";
    console.log('\nOriginal funcion\n', inputCode, '\nAdded function details: \n', addLoggingPattern(inputCode, myPattern));

Tests

npm test

Use example

This program can be used just especifying the input, that will search all the functions in the input and print by console the extra information about the functions that has founded.

npx addLogging ./inputs/inputTest.js

Execution:

Pattern:  undefined
input:
function foo(a, b) {
    var x = 'blah';
    var y = (function () {
        return 3;
    })();
}
foo(1, 'wut', 3);
Output in file './outputs/output.js'

This program can also be used specifing the output and without especifying any search pattern, that will search all the functions in the input and the program will run for all the founded functions. The output instead of been printed by console as before, now will be saves in the output file.

npx addLogging ./inputs/inputTest.js -o ./outputs/output.js

Output:

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);

Also there's a search pattern flag than can be easily used, this will make the program to just print the information about the functions that containts teh search pattern.

npx addLogging ./inputs/inputTest.js -o ./outputs/output.js -p foo

Output:

function foo(a, b) {
    console.log(' Entering foo(${a},${b}) at line 1');
    var x = 'blah';
    var y = function () {
        return 3;
    }();
}
foo(1, 'wut', 3);

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.

Release History

  • 0.1.0 Initial release
  • 1.0.3 Functional release
  • 2.0.3 Improved documentation
  • 2.0.4 Finished version