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

@micl/server-log

v0.0.2

Published

A simple and customizable server-side logger for Node.js applications, supporting multiple logging levels and module-specific logs.

Readme

@micl/server-log

A simple and customizable server-side logger for Node.js applications, supporting multiple logging levels and module-specific logs.

Installation

npm install @micl/server-log

npm Page

🔗 @micl/server-log on npm

Usage

Importing the Logger

const { serverLogger, initLogger } = require('@micl/server-log');

Initializing the Logger

By default, logs are stored in the ./logs directory. If the specified directory does not exist, the script will create it automatically. You can also specify a custom directory and module-specific loggers:

initLogger(['auth', 'database'], './server-logs');

Logging Messages

General Logs

serverLogger.info('Server started');
serverLogger.warn('Memory usage is high');
serverLogger.error('Failed to connect to database');

Module-Specific Logs

If you initialized the logger with modules (e.g., auth and database), you can log messages for these modules:

serverLogger.auth.info('User login successful');
serverLogger.database.error('Database connection lost');

Log Output Format

Each log entry is prefixed with a timestamp and log level:

[INFO][HH:MM:SS] Server started
[WARN][HH:MM:SS] Memory usage is high
[ERROR][HH:MM:SS] Failed to connect to database

Contributing

You can contribute to this module online via CodeSandBox, or locally:

  1. Clone the repository.
  2. Install dependencies with yarn install or npm install.
  3. Start the development server using yarn dev or npm run dev.

License

This project is licensed under the MIT License.

Copyright (c) alexgogoing [email protected]