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

console-log-proxy

v0.1.5

Published

javascript console debug proxy server

Downloads

9

Readme

Console Log Proxy

npm version MIT License

  • require node v10.x
  • It is assumed that there is no devtools, such as a TV browser, and development is difficult.
  • Only console output and DOM debugging is not supported
  • Using the nodejs standard inspector

Usage

install

$ yarn global add console-log-proxy

proxy server

$ console-log-proxy

default port is 8888

if you specify a port

$ PORT=1234 console-log-proxy

proxy client

There is a websocket client and an http client Adding this script tag to your app

websocket client

<script src="http://localhost:8888/websocket-client.js"></script>

http client

<script src="http://localhost:8888/http-client.js"></script>

if youe specify proxy server host and port

<script>
  var console_log_proxy_config = {
    host: 'xxx.xxx.xxx.xxx',
    port: 1234
  };
</script>
<script src="http://xxx.xxx.xxx.xxx:1234/websocket-client.js></script>

Supported console method

  • debug
  • error
  • info
  • log
  • warn
  • dir
  • table

inspector client

inspector client is here

It is convenient to use NIM when using Chrome