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

@ggcristo/logging-input

v0.4.2

Published

Este programa recibe otro programa en forma de string, el cual modifica añadiendole sentencias ```console.log``` cada vez que se aparece una función.

Downloads

4

Readme

CI for addLogging module
addLogging

Module to apply "printf() debugging", trought metaprograming every time you call a function

Installation

npm install @ggcristo/logging-input -g

Usage

add-logging --pattern foo --output salida.js input.js  
This read the "input.js" file search and in case the file has valid
javascript in it, search for the funtion whose identifier match with the one you write in the --pattern option, written a console.log on it.

Hipotetic file

function foo(a, b) {
  var x = 'blah';
  var y = (function () {
    return 3;
  })();
}
foo(1, 'wut', 3);

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

Module Help

~: add-logging
Usage: add-logging [options] <filename> [...]

Metaprogramación con AST

Options:
  -V, --version               output the version number
  -o, --output <filename...>  fichero de salida
  -h --help                   output usage information
  -p --pattern <pattern>      filter the function to process

API usage

This is an one-function module:

addLogging(code, functionNamePattern)

This function take the code in the form of a string (code), the functionNamePattern is opcional.
It will return the result code in a form of a string as well.

Tests

npm test

Constributing

Try to use a consist style with the already existing code, avoid monster commits.
If you consider the contribution is big, create a pr and add the tag [WIP] so others can watch over the process

Release History

  • 0.2.0 Initial release
  • 0.2.1 Básic test(WIP)
  • 0.2.2 Actions
  • 0.2.3 Minor bug fixes
  • 0.3.0 Executable file
  • 0.4.0 Patter option