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

http-echo-server

v2.1.1

Published

A simple HTTP echo server

Downloads

377

Readme

http-echo-server

Will accept any TCP connection and echo back a HTTP response with the entire content of the incoming TCP connection.

The server makes no attempt to understand the incoming HTTP request hence it doesn't know when the request is completed and therefore just terminates the TCP connection 2 seconds after the first data packet.

npm Build status js-standard-style

Installation

To setup a simple echo-server on Heroku just click this button:

Deploy

Note that the Heroku routing stack will proxy the incoming request and add custom HTTP headers.

Alternatively, to start it locally just run (only supported on newer versions of npm):

npx http-echo-server

Or if you whish to install the module globally:

npm install http-echo-server -g

Example usage

Just curl the URL of the app:

curl http://<heroku-app-name>.herokuapp.com

Alternatively - if installed locally - you can start the server using the command http-echo-server, take note of the port it starts on and then curl it:

curl http://localhost:<port>

Setting listening port

To set the http port, either supply the port as an argument to the http-echo-server executable:

http-echo-server 3005

Or use the PORT environment variable:

export PORT=3005
http-echo-server

License

MIT