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

@alu0101051420/addlogging

v1.5.7

Published

Addlogging ==============

Downloads

49

Readme

Addlogging

A small library providing a method to add logging messages in existing functions (js).

Installation

npm install addlogging --save

Usage

You can import the main function and use it like this:

const { addLogging } = require('@alu0101051420/addlogging');

let code = `function foo() { var x = 'blah'; } foo();`,
commented = addLogging(code);

console.log('Original Code: \n', code);
console.log('Code with logs: \n', commented);

Output:

Original Code: 
  function foo() { var x = 'blah'; } foo();
Code with logs:
  function foo() {
    console.log(`Entering foo() at line 1`);
    var x = 'blah';
  }   
foo();

An executable is also imported. You must specify an input file, and may or may not specify an output file and/or a name pattern. This pattern will be used to comment only functions whose name match it. (You can specify "anonymous" in order to comment anonymous functions.)

npx addlogging myfile.js
npx addlogging myfile.js --output output.js
npx addlogging myfile.js --output output.js --pattern foo

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

npm test

Release History

  • 1.0.0 Initial release
  • 1.4.0 Big changes. Added executable, and --pattern function.
  • 1.5.3 Latest version. Minor bug fixes.