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

server-io-debugger-client

v1.0.0-alpha.2

Published

separate client for server-io-core debugger server

Downloads

6

Readme

server-io-debugger-client

separate client with stacktrace-js / socket.io-client to hijack the console.log for your remote debugging need (use with server-io-core series of tools)

Installation (For CLI client)

It's recommend to install this globally

$ npm i -g server-io-debugger-client

Usage (For CLI client)

$ srvioDebuggerClient https://domain.com/nsp-name

Then wait for the connect message to make sure you are connected. Then whenever your debugging target using the console.log or an Javascript error happen, it will broadcast the message and received by the listening client.


Installation for your browser app (or phonegap app)

You need to include the server-io-debugger-client/src/main.js and add to your html document. Also you need to add stacktrace-js and socket.io-client to your dependencies (and add to the html document if needed).

If you are using it with fancy JS UI library. You might get away with using

import 'server-io-debugger-client';

Because it doesn't export anything. Try this at your own risk.

Initialize your debugger

The debugger listen to a custom event serverIoDebuggerStart and expect a parameter nsp from the event. What you can do is after your app init. You can trigger an event like this.

var evt = new CustomEvent('serverIoDebuggerStart');
evt.nsp = 'http://your-server.com/your-nsp';
window.dispatchEvent(evt);

Once the client is connect to the debugger server. You will get a serverIoDebuggerInited event back.

So you can listen to this event and decided to what to do.

window.addEventListener('serverIoDebuggerInited', function(e) {
  // do something with the e.msg
  // but don't use the console.log perhaps use console.info instead :)
});

Once the init is done. Whenever your app has error, onunhandledrejection event, or call the console.log they will get send to the remote debugger server. Then you can use the cli client as describe above to observe what is going on in your app.


TODO

  • add more options to how this capture data
  • add secondary logging option to log to file or database

MIT (c) NEWBRAN LTD 2018