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

console-at

v2.0.1

Published

Add console functions that also output where the call was made.

Downloads

5

Readme

console-at

Add console functions that also output where the call was made.

The console object has several useful functions defined as properties. Because functions are not primitive we can add properties to those functions. For each of the following functions, an at property is added that is called using the same parameters. It calls the original function plus adds information about where the function was called.

These functions each have the at property added to them just by requiring the console-at package once in your project:

  • console.error
  • console.info
  • console.log
  • console.warn

Example 1

This still works.

require('console-at');
console.log('Hello, World!');
// Hello, World!

Example 2

We can also call the log function with location information:

require('console-at');
console.log.at('Hello, World!');
// Hello, World!
//   at /path/to/file.js: 2

Installation

$ npm install console-at

API

The package includes a single function that can be called to determine the location that the function is called at. Additionally this function can take an optional parameter that will specify how far back in the stack to look for location information.

at ( [ backDepth = 0 ] )

Parameters

  • backDepth - Optional. How far back in the stack trace to get location information for. Defaults to 0.

Returns an object with the following properties:

  • column - Number. The column number.
  • file - String. The file name.
  • line - Number. The line number.
  • method - String. The function name.
  • position - Number. The position in the file.
  • source - String. The file name and line number.

Example 1: Zero Depth

var at = require('console-at');

function foo() {
    return at();        // the position reported is here
}

console.log(foo());

/*
{ column: 12,
  file: '/path/to/file.js',
  line: 4,
  method: 'foo',
  position: 120,
  source: '/path/to/file.js:4' }
*/

Example 2: One Depth

var at = require('./index');

function foo() {
    return at(1);
}

var source = foo();     // the position reported is here
console.log(source);

/*
{ column: 14,
  file: '/path/to/file.js',
  line: 7,
  method: null,
  position: 143,
  source: '/path/to/file.js:7' }
*/