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

basic-serve

v0.1.0

Published

A basic static file http server for development

Downloads

1

Readme

BasicServe

A basic static file http server for development.

No frills, no dependencies, no hassle.

Usage

> basicServe -h

Usage: basicServe [options] <directory_to_serve>

Options:

  -h, --help    output usage information
  -p, --port    listen port (default: 8080)

Output

First, logs served directory and server URL.

Then, logs one line per request, with request URL, served file, and content type (if recognized).

Example:

> basicServe public -p 12345
serving public at http://localhost:12345
/ -> public/index.html (text/html)
/bundle.js -> public/bundle.js (text/javascript)
/favicon.svg -> public/favicon.svg (image/svg+xml)

Path Mappings

The following request paths are mapped:

  • / -> /index.html

Status Codes

One of two status codes will be returned, depending on whether a file was found at the requested path:

  • 200 OK
  • 404 Not Found

Content Types

The extension of the file served is used to determine the content type.

The following extensions are recognized:

  • .apng -> image/apng
  • .bmp -> image/bmp
  • .css -> text/css
  • .cur -> image/x-icon
  • .html -> text/html
  • .gif -> image/gif
  • .gzip -> application/gzip
  • .ico -> image/x-icon
  • .jfif -> image/jpeg
  • .jpeg -> image/jpeg
  • .jpg -> image/jpeg
  • .js -> text/javascript
  • .json -> application/json
  • .otf -> font/otf
  • .pdf -> application/pdf
  • .pjp -> image/jpeg
  • .pjpeg -> image/jpeg
  • .png -> image/png
  • .sfnt -> font/sfnt
  • .svg -> image/svg+xml
  • .tif -> image/tiff
  • .tiff -> image/tiff
  • .ttf -> font/ttf
  • .txt -> text/plain
  • .webp -> image/webp
  • .woff -> font/woff
  • .woff2 -> font/woff2
  • .xml -> application/xml
  • .zip -> application/zip

Files with unrecognized extensions will be served without a content type.