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

@fict/logger

v0.1.3

Published

The logging utility package for Fict

Readme

How to use @fict/logger

@fict/logger allows multiple modules to use a logger at the same time. From each of the modules initialize it as below:

const logger = require('@fict/logger').defaultInit('../package.json', { logConfigFolder: __dirname + "/../../config/logger" });

In the package.json you can set custom property logLabel to any value that you want to show in the logs as the name of the module. If not set, the name of the package will be used by default.

The logger created above is a child object that comes in-built with {src: logLabel} context for the log. To use the logger just use any of the info, debug, warn or log methods as usual:

  app.logger.info(`Server started at ${host}:${port}`)

To add any additional context, use it as below:

  app.logger.info({additionalCtx: value}, `Server started at ${host}:${port}`)