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

mter-rs

v1.3.2

Published

capture your terminal logs, and send to network by udp. you can use [mter](https://www.npmjs.com/package/mter) to get those logs and print.

Downloads

11

Readme

mterminal-remote-server

capture your terminal logs, and send to network by udp. you can use mter to get those logs and print.

why

Normally, your nodejs application will mix the logs of the master process and the cluster process in one terminal to print. In development mode, this can cause confusion. We need need a tool to separate these logs into different places for printing. so here you are.

usage

  1. write your code.
import { setupMter } from '../src/';

setupMter();
  1. install and run mter.
# install 
npm i -g mter
# start the server
mter 
  1. start you app.
MTER="*" node your-app.js

API

setupMter(opt?:MterOptions)

MterOptions

  • keep_stdout?: boolean,
  • process_name?: string,
  • recipient_port?: number,
  • heartbeat_udp_port?: number,
  • default_bind_udp_port?: number,
  • bind_udp_port_lock_file_name?: string,

normally, you only need config: keep_stdout. if true, the log will keep print in you terminal, and broadcast at the same time.

in mter api, you can get the debugging process name by api:http://127.0.0.1:4510/api/wss. but you maybe see like this:{"list":[{"path":"/wss/4869","process_name":"MASTER-test2.ts-9885"},{"path":"/wss/4870","process_name":"CLUSTER-test2.ts-9891"}]}, you can config the process_name to change. this can improve readability.