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

@vortus-solutions/logger-service

v1.0.0

Published

Enhanced logging service for Node.js applications with pretty printing and structured logging

Downloads

30

Readme

@vortus-solutions/logger-service

A robust logging service for Node.js applications built on top of Pino, providing enhanced console logging capabilities with pretty formatting.

Features

  • Built on top of the high-performance Pino logger
  • Console method overriding (log, error, warn, info, debug)
  • Pretty printing with colorization
  • ISO timestamp formatting
  • Automatic error object handling
  • Configurable log levels
  • Maintains original console references

Installation

npm install @vortus-solutions/logger-service

Requirements

  • Node.js >= 14.0.0

Usage

Basic Usage

const logger = require('@vortus-solutions/logger-service');

// Regular logging
console.log('Hello World'); // Will use enhanced logging

// Object logging
console.log({ user: 'john', action: 'login' });

// Error logging
console.error(new Error('Something went wrong'));

// Other log levels
console.warn('Warning message');
console.info('Info message');
console.debug('Debug message');

Accessing Original Console

If you need to access the original console methods:

console.original.log('Using original console.log');

Configuration

The logger can be configured through environment variables:

| Variable | Default | Description | |-------------|---------|------------------------| | LOG_LEVEL | 'info' | Minimum logging level | | LOG_TRANSLATE_TIME | 'pattern' | Date pattern |

Log Levels

Available log levels in order of priority:

  1. error
  2. warn
  3. info
  4. debug

Features in Detail

Automatic Error Handling

When logging Error objects, the logger automatically formats them properly:

const error = new Error('Database connection failed');
console.error(error);
// Will output formatted error with stack trace

Object Logging

Objects are automatically stringified and formatted:

console.log({
  event: 'user_action',
  details: {
    userId: 123,
    action: 'login'
  }
});

ISO Timestamp

All logs include ISO formatted timestamps for precise timing information.

Development

# Run tests
npm test

# Run linting
npm run lint

# Format code
npm run format

# Build
npm run build

License

MIT

Author

Danilo Recchia [email protected]

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -am 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Create a new Pull Request

Support

For support, issues, or feature requests, please file an issue in the GitHub repository.