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

nbrest-logger

v1.0.7

Published

Basic logging framework for node apps

Downloads

20

Readme

| Home | Docs |


nbrest-logger:

Basic logging framework to format logs to the console in a node app.

Install or Update:

  • In the root of your node app:
npm i nbrest-logger

Usage:

const logger = require("nbrest-logger");
logger.trace("my message");
logger.debug("my message");
logger.info("my message");
logger.warn("my message");
logger.error("my message");
  • Change the log level during runtime:
logger.setLogLevel("ERROR");
logger.setLogLevel("WARN");
logger.setLogLevel("DEBUG");
logger.setLogLevel("trace");
  • The default log level is INFO, so DEBUG and TRACE entries are hidden by default. To change the log level at application startup, pass the log or LOG argument to your node app:
npm start LOG=TRACE // enables both trace and debug logs
npm start log=debug // enables debug logs
npm start log=warn // set log level to warn
npm start log=error // set log level to error

Output:

> [email protected] start
> npm run devserver LOG=trace


> [email protected] devserver
> node ./server/node/server.js LOG=trace

2023-12-06 23:01:53 - [INFO] - Overriding logLevel with command line parameter log: trace mapped to logLevelNumber: 4
2023-12-06 23:01:54 - [TRACE] - Finished initializing nbrest-logger
2023-12-06 23:01:54 - [INFO] - Initializing endpoints
2023-12-06 23:01:54 - [INFO] - Startup server
2023-12-06 23:01:54 - [DEBUG] - my DEBUG message
2023-12-06 23:01:54 - [TRACE] - my TRACE message
2023-12-06 23:01:54 - [INFO] - Listening on http://localhost:8080

Publish:

  • Update version in package.json
  • Publish changes to npmjs with:
npm publish