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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@forgerock/sdk-logger

v1.3.0

Published

A flexible and configurable logging utility for the Ping Identity JavaScript SDK.

Downloads

465

Readme

Logger

A flexible and configurable logging utility for the Ping Identity JavaScript SDK.

Features

  • Multiple log levels (error, warn, info, debug, none)
  • Ability to change log level at runtime
  • Support for multiple arguments in log messages
  • TypeScript support with proper type definitions

Installation

npm install @ping-identity/effects-logger

Usage

import { logger } from '@ping-identity/effects-logger';

// Initialize the logger with a specific log level
const log = logger({ level: 'info' });

// Basic usage
log.info('Application started');
log.error('An error occurred:', new Error('Something went wrong'));

// Multiple arguments
log.debug('User data:', { id: '123', name: 'John Doe' });

// Change log level at runtime
log.changeLevel('debug'); // Enable debug logs
log.debug('Debug information is now visible');

log.changeLevel('none'); // Disable all logs
log.error('This error will not be logged');

Log Levels

The logger supports the following log levels (in order of severity):

  1. error - Critical errors that may cause the application to fail
  2. warn - Warnings that don't interrupt application flow but require attention
  3. info - General information about application flow
  4. debug - Detailed information for debugging purposes
  5. none - No logs will be output

When a log level is set, only messages of that level or higher severity will be displayed.

API Reference

logger({ level })

Initializes a new logger instance.

Parameters:

  • level: The initial log level ('error', 'warn', 'info', 'debug', or 'none')

Returns: A logger instance with the following methods:

  • error(...args): Log an error message
  • warn(...args): Log a warning message
  • info(...args): Log an informational message
  • debug(...args): Log a debug message
  • changeLevel(level): Change the current log level

Building

Run nx build logger to build the library.

Running unit tests

Run nx test @forgerock/sdk-logger to execute the unit tests via Vitest.