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

log.io-cmds

v1.0.1

Published

Helper tools to cennect to log.io (logio.org)

Downloads

10

Readme

log.io-cmds

Helper tools to cennect to log.io server (logio.org) (osx, win, linux, ..)

install

> npm i log.io-cmds -g

or cutting edge:

> npm i BananaAcid/log.io-cmds#master -g

usage (log.io v0.4.3+)

> msg2logio -m "test message"
> msg2logiobare "+msg|streamName1|sourceName1|this is a log message"

note

  • If you prefer the Windows style, you may use /param or /param=val
  • the "bare" variant is only connecting to localhost - use it as a simple code example

help

> msg2logio --help

Talk to Log.io Server (this is a "3rd party Harvester")
Author: Nabil Redmann 2020, www.nabil-redmann.de
docu: https://github.com/NarrativeScience/Log.io

CONFIGURATION:
        edit this file and change this part: var conConfig = { port: '6689', host: 'localhost' } ;
        or add those keys as params: --host=localhost --port=28777

        to show configuration and params use: --showconfig

USAGE SHORT: msg2logio -m "message to send" "second message to send" ...
             msg2logio --msg "message to send" "second message to send" ...
             msg2logio --msg=warn "message to send" "second message to send" ...
         OR: echo "message to send \n second message to send \n ..." | msg2logio --msg
             cat some.log | tail -5 | msg2logio --msg=info --service="status Update"

USAGE: msg2logio "+msg|service|server|info|message to send" "+msg|service|server|info|second message to send" ...

        Send a log message (if none, registers a new node and stream but does not deliver msg) - "info" can be any keyword or emoji ✔ ❌ ❤ ✨
        +msg|my_stream|my_node|info|this is log message

        Register a new node
        +input|my_node

        Register a new node, with stream associations
        +input|my_node|my_stream1,my_stream2

        Remove a node
        -input|my_node

        this will send as (msg, username, hostname, info-flag, message):
        [
                "+msg|webservice|Server01|info|message to send",
                "+msg|webservice|Server01|info|second message to send",
                ...
        ]

usage (log.io v0.3.4-)

> msg2logio.0.3 --log "test message"
> msg2logiobare.0.3 "+log|streamName1|sourceName1|this is a log message"