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

flog.io

v3.2.1

Published

Nested Log Trees // Console And Socket Logging

Downloads

18

Readme

flog.io

Nested Log Trees // Console And Socket Logging

flog.io is a tool for nested tree logging. The nested structure allows for a more varied console.log() usage. Replace your console.log() calls with flog.io.print(), or use them together.

npm install flog.io

Create new logs by: ---with or without a config object ---const flog=require('flog.io') ---let log=new flog.io({config object})

Default Config Object: { name:'flog.io' ,readconsole:false -> read console.log() calls ,writeconsole:true -> send to console.log() ,logfile:false -> save a log file ,sockets:[] -> sockets array ,emitname:'flog.io' -> socket emit event name ,parents:[] -> parents array ,children:[] -> children array }

Functions: .print(arguments) .addsocket(socket) .addchild(child) .addparent(parent) .removesocket(socket) .removechild(child) .removeparent(parent) Using print(): ---using a comma between arguments will start a new line ---replace the use of console.log() with .print(), .print() will write to the console, send over any sockets, save to a log file, and send to any parents ---or use console.log() and declare a flog.io with 'readconsole:true' to read the console.log() and automatically send to any log files, sockets, or parent logs

To use nested tree logging: ---.addchild(child) -> add a child log, the child.print() calls will also call the parent.print() ---.addparent(parent) -> add a parent log, similar to above ---.removechild(child) -> remove a child log ---.removeparent(parent) -> remove a parent log ---parents/children can also be added at instantiation ---Children copy their parents to the child's .print() calls, and those parents will copy their parents to the .print() call, etc ---Create any tree structure you like

Log to file: ---use the config setting 'logfile:true' ---every new flog.io has its own log file ---for now logs can be found in the 'flog.io' module folder

To enable the socket logging: ---.addsocket(socket) -> add a socket to pass print() arguments to using config.emitname ---the receiving socket.on(event,args) event by default is 'emitname:'flog.io'' ---sockets can also be added at instantiation