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 🙏

© 2026 – Pkg Stats / Ryan Hefner

echoclientserver

v0.0.2

Published

Simple echo client and server for code challenge

Downloads

10

Readme

EchoServerApp

This is a Node.js exercise to create an echo server and client. The client and server ports are configured by individual discretion, or the default 3000 can be used. The client and server communicate via socket connections. Further details about the module are:

  • EchoClientServer.js is a valid Node.js module
  • Asynchronous, Non-blocking IO
  • TCP Server handles Socket Connected Clients

#Installation

npm install EchoClientServer

#Code Usage

##Server

var app = require("./EchoClientServer"),
	options = {
		port: 3000,
		quiet: true
	};
app.server.start( options );

##Client

var app = require("./EchoClientServer"),
	options = {
		port: 3000,
		timer: true
	};

function listener( msg ){
	console.log( "Received MSG: "+ msg );
}

app.client.listen( listener) ;
app.client.send( "HELLO WORLD", options );

#Sample Client and Server Be sure to start the server first before the client. Also, note that both the ports, of client and server, need to the same.

EchoClientServer-server.js

The following command starts the server at port (-p) 3005 and listens quietly (-q) for socket connections.

node EchoClientServer-server.js -q -p 3005

EchoClientServer-client.js

The following command begins the client connection at port (-p) 3005 and measures time (-t) in ms from connection until message is received. In addition, the message sent to the server is "Hello World!"

node EchoClientServer-client.js "Hello World!" -t -p 3005

#TESTING ##Jasmine-Node (Behavior-Driven Development) The EchoClientServer module has been tested with Jasmine (jasmine-node). Two test cases were conducted, one to test using the default port and the other test using a custom port. For each of these tests we start and stop the server, in addition to also creating and destroying a socket connection. The server is closed once we process the data received by the client and the client's socket connection is destroyed right after the custom function handles the response.

jasmine-node spec

Finished in 0.009 seconds
2 tests, 0 assertions, 0 failures, 0 skipped

#Bonus

  • Server and Client are accessible from one module and can be included into any other Node.js app
  • Ports are optional and configurable
  • The serves has quiet capability, which means it does not print any output on connection
  • The time can be computer on the client to determine how long it takes to receive the echo from server