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

relogger-cli

v0.0.7

Published

Comand line interface for ReLogger

Downloads

17

Readme

relogger-cli

Command Line Interface for relogger

Install

$ npm install -g relogger-cli

Usage

On your command line type

$ relogger

You can also specify the port (defaults to 9090)

$ relogger --port 9090

Once the server is up an running you will see an message like

$ relogger --port 1234
                .__                                             
_______   ____  |  |    ____     ____     ____    ____  _______ 
\_  __ \_/ __ \ |  |   /  _ \   / ___\   / ___\ _/ __ \ \_  __ \
 |  | \/\  ___/ |  |__(  <_> ) / /_/  > / /_/  >\  ___/  |  | \/
 |__|    \___  >|____/ \____/  \___  /  \___  /  \___  > |__|   
             \/               /_____/  /_____/       \/         

        Relogger Server up and running on port: 1234
        To enable remote logging please add the following script tag to your page: 
        <script type="text/javascript" src="http://YOUR_IP_ADDRESS:1234/relogger/reloggerclient.js"></script>

The logs are sent through a FIFO queue which ensures that the all the logs happen in order. You add the script to your page and whenever you want to add a remote log you can do so with:

   console.re.log('test log');
   console.re.warn('test warn log', {data: 'some data'}, ['MORE DATA']);
   console.re.debug('test debug log');
   console.re.error('test error log');

Also once you have added relogger to your page, all uncaught errors will automatically be remotely logged.

Remote logging on a page that uses https

If you want to use relogger on a page that uses https, you need to pass a certificate to relogger so that he can serve the pages with it.

You can generate a certificate in unix/linux with the following commands:

openssl genrsa -out key.pem
openssl req -new -key key.pem -out csr.pem
openssl x509 -req -days 9999 -in csr.pem -signkey key.pem -out cert.pem
rm csr.pem

Once you have the certificate in place, you need to tell relogger where to get the private key and the cert.

If you call your private key, key.pem and your certificate cert.pem you can tell relogger where to search for them

$ relogger --cert-data PATH_TO_THE_CERTIFICATES_FOLDER

You may can also spefify where to seach for the key and the cert separately.

$ relogger --key PATH_TO_key.pem  --cert PATH_TO_cert.pem