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

mcstatusbot-logger

v1.0.5

Published

a logger for the mcstatus bot

Downloads

5

Readme

logger

a simple logger that adds times log type and also add the logs to a file

setup

make an env file that will contain your config options

MCSB_LOGGER_PATH (string)

this is the path you will store all your log files in

  • starting it with ./ will make it relative to your project directory
  • starting it with / will make it relative to your root and you have to specify a full path

it is a good idea to place it in a logs direcotry because it makes multible archive files which can get messy

default: ./logs

MCSB_LOGGER_FILE_PREFIX (boolean)

if you want your log files to be prefixed with the type of log it is eg success, error.

default: false

example .env file
MCSB_LOGGER_PATH=./logs
MCSB_LOGGER_FILE_PREFIX=true

install the module

npm i mcstatusbot-logger

example

require('dotenv').config();
const logger = require('mcstatusbot-logger');


logger.success("you are now using logger [email protected]");
logger.info("you are now using logger by mcstatusbot.site");

docs

.sucess([string: message <default: "">], [boolean: log to file <default:true>])

sends a success message

.info([string: message <default: "">], [boolean: log to file <default:true>])

sends a info message

.warn([string: message <default: "">], [boolean: log to file <default:true>])

sends a warn message

.error([string: message <default: "">], [boolean: log to file <default:true>])

sends a error message

.crash([string: message <default: "">], [boolean: log to file <default:true>])

sends a crash message