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

nc.js

v1.0.20

Published

A simplified nc(netcat)

Downloads

21

Readme

nc.js

A simplified nc(netcat)

Why i made it

  • On Windows, nc/ncat/socat.exe can not be trusted because they are not signed.
  • I want a prototype so can be easily modified to do more works such as dump, analyse data.
  • I want to see connection info CLEARLY which almost not provided by nc/ncat/socat.
  • I want the TCP server send data to all clients (like broadcast)
  • I don't want to remember complicated arguments for socat, and also nc which are distribution-dependent.

Usage

(You can install it by npm install -g nc.js)

  • TCP Server

    nc-listen.js [localAddress:]port
    nc-listen.js localAddress port
    • Listen at a port, wait for connection from clients.
    • Data from standard input will be send to all clients (like broadcast).
    • Data from clients will be output to standard output.
  • TCP Client

    nc-connect.js [host:]port
    nc-connect.js host port
    • Connect to server
    • Data from standard input will be send to server.
    • Data from server will be output to standard output.

Samples:

  • TCP-Server

    $ nc-listen.js 8888
    Using parameters {
        "localAddress": "",
        "localPort": 8888
    }
    Listening at [::]:8888
    [[::ffff:127.0.0.1]:64212] Connected from [::ffff:127.0.0.1]:64212
    ... data ...
    [[::ffff:127.0.0.1]:64212] EOF
    [[::ffff:127.0.0.1]:64212] closed

    Do not worry about the log of listening at ::(all IPv6 interfaces), as far as i'v tested, on Windows and Mac OS X, listening at :: will cause all IPv4 interfaces being listened either.(called dual-stack).

    More:

    $ nc-listen.js a.b.c:8888
    $ nc-listen.js [2001:db8:a0b:12f0::1]:8888
  • TCP-Client

    $ nc-connect.js 8888
    Using parameters {
        "host": "",
        "port": 8888
    }
    Connected to 127.0.0.1:8888 source 127.0.0.1:64212
    ...
    EOF
    closed
    
    $ nc-connect.js a.b.c:8888
    $ nc-connect.js [2001:db8:a0b:12f0::1]:8888