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

sensible-salmon-sparrow

v4.4.5

Published

A simple and extensible Node.js HTTP server with routing, static file serving, and request parsing functionality. This project demonstrates how to build a basic HTTP server without using any additional packages.

Downloads

3

Readme

Simple Node.js HTTP Server

A simple and extensible Node.js HTTP server with routing, static file serving, and request parsing functionality. This project demonstrates how to build a basic HTTP server without using any additional packages.

Table of Contents

Installation

To get started, clone this repository and navigate to the project directory:

git clone https://github.com/your-username/simple-node-http-server.git
cd simple-node-http-server

Usage

Run the server using Node.js:

node index.js

The server will start on http://localhost:3000.

API

GET /

Returns a simple welcome message.

Request

GET / HTTP/1.1
Host: localhost:3000

Response

HTTP/1.1 200 OK
Content-Type: text/plain

Welcome to the Home Page

GET /about

Returns a message about the page.

Request

GET /about HTTP/1.1
Host: localhost:3000

Response

HTTP/1.1 200 OK
Content-Type: text/plain

This is the About Page

GET /data

Returns the query parameters as a JSON object.

Request

GET /data?name=John&age=30 HTTP/1.1
Host: localhost:3000

Response

HTTP/1.1 200 OK
Content-Type: application/json

{
  "name": "John",
  "age": "30"
}

POST /submit

Accepts and returns the POSTed data as a JSON object.

Request

POST /submit HTTP/1.1
Host: localhost:3000
Content-Type: application/x-www-form-urlencoded

name=John&age=30

Response

HTTP/1.1 200 OK
Content-Type: application/json

{
  "message": "Data received",
  "data": "name=John&age=30"
}

Static Files

Serve static files from the static directory. For example, accessing /static/example.html will serve the example.html file from the static directory.

Request

GET /static/example.html HTTP/1.1
Host: localhost:3000

Response

HTTP/1.1 200 OK
Content-Type: text/html

<!-- Contents of example.html -->

Contributing

Contributions are welcome! Please fork the repository and submit a pull request for any improvements or bug fixes.

  1. Fork the repository
  2. Create a new branch (git checkout -b feature/your-feature)
  3. Commit your changes (git commit -am 'Add your feature)
  4. Push to the branch (git push origin feature/your-feature)
  5. Create a new Pull Request