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 🙏

© 2026 – Pkg Stats / Ryan Hefner

pino-log-link

v1.0.3

Published

Pino Log Link adds a link to each log entry to the file that generated it .

Readme

Pino Log Link

Pino Log Link adds a link to each log entry to the file that generated it .

Usage

1. Setup the logger

   const pinoConfig = {} // can be pre configured.
   const pinoConfigLinked = setupLogLink( pinoConfig, 'module', () => moduleMap, 'http://localhost:3000/');
   logger = pino(pinoConfigLinked)

2. Log Messages

Add the module name to your entries with the prop name you've chosen: logger.log( { module: 'MyModule', msg: 'hello' } );

3. Results

The log entry will have a link to the file that generated it: { msg: 'hello http://localhost:3000/MyModule.ts' }

4. Connect the source map

This is the only thing that must run on the server. You can use the generateSource map from a WebPack plugin:

//... plugins...
new webpack.DefinePlugin({
          "process.env.MODULE_MAP": JSON.stringify(
              generateModuleMap(rootDirectory)
          ),
      }),

Limitations

While quick and dirty, this is functional and makes life so much easier. It's not, however, without its limitations. Namely:

  • You do need to add the module name to your log entries ( no need to enter the full path). Most IDE's will autocomplete this for you..
  • No line numbers are included.
  • WebPack works out of the box , but for other setups , you need to plug the source map generator.

Enjoy!