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

@fizker/serve

v0.3.1

Published

A static file HTTP server

Downloads

3

Readme

@fizker/serve

A static file HTTP server, designed to be running in Docker.

It has no dependencies and does as little work as possible in order to serve files. This is achieved by running a tool like @fizker/serve-prepare first to prepare the files.

How to use

See @fizker/serve-prepare for how to prepare the Docker container. Once the container is built, execute the following command: docker run -p <desired HTTP port>:8080 -p <desired HTTPS port>:8081 -d <your docker user>/<your project name>

Internally, the server is configured to run on port 8080 per default, which is why the -p <desired HTTP port>:8080 ends with 8080. If desired, the port can be changed by either altering the Dockerfile or by adding -e PORT=8080 to the run command. Services such as Heroku will also change the port as they require.

The 8081 port is used for HTTPS connections. It can be configured in a manner similar to the HTTP port. If HTTPS support is not wanted, or you have not set up the certificates yet, that portion can be omitted to avoid exposing an unused port to the Docker container.