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

trace-line

v0.0.6

Published

A function to aid debugging by logging the line number and filename when executed

Downloads

177

Readme

trace-line

A function to aid debugging by logging the line number and filename when executed, optionally passing a value to display

Install the plugin

npm install trace-line --save-dev

To use as an import or required

Require or import the module

var trace = require('trace-line');

or if you are using import

import trace from 'trace-line';

Call the function in your code

trace();
var x = 33;
trace(x);

will produce

--- Line #1 of <your filename>.js hit ---
--- Line #3 of <your filename>.js hit with value of:
  33

If desired for more compact usage you could name the function something smaller like this:

var d = require('trace-line');
...
d(); 

To use as a global

A global trace function is also created when the module is imported/required. Just make sure that you import the module somewhere before the first call to trace. From then on it can be called in anywhere without re-importing. This is, of course, not a best practice for Javascript code... but this library is only to be used for debugging. You could potentially leave these statements in your code after deployment, but there is a small performance penalty and it clutters up your logs, so I suggest removing them.