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

servehere

v1.10.1

Published

Serve from the local directory, immediately

Downloads

96

Readme

servehere

Host a webserver from the local directory, immediately

 

 

tl;dr

npm install -g servehere
servehere

Now hit http://localhost:4400.

 

 

Command-line arguments

--port / -p: Set the port. Defaults to 4400. Ports below 1024 may need account privileges on unix machines.

--directory / -d: Set the directory to serve from. Defaults to ./.

--jsonapi / -j: Pretend to be a JSON api; usually needs -c (send application/json for files without extensions; default is text/html)

--cors / -c: Emit universal CORS headers

--silent / -s: Be silent (no output; default is verbose)

--haltroute / -z: Hook /z-terminate as a route that will halt the server when opened

--help / -h: Show help in the console

 

 

Usage examples

  • Run a server, sharing the current directory on default host localhost and default port 4400
    • servehere
  • Run a server, sharing the current directory on default host localhost and custom port 12345
    • servehere -p 12345
  • Run a server, shipping CORS allow-all headers, set up as a JSON api, shipping the contents of a subdirectory "fixtures"
    • servehere -c -j -d fixtures/
  • Run a server in silent mode (don't write anything in console) with a halt route
    • servehere -s -z

 

 

... why?

Pretty often I have to put stuff on my webserver because I want to figure out how its AJAX or websockets work, but CORS and localhost don't play well together.

Also, I'm mildly annoyed at how often I see JavaScript projects install Python to get simple_server.

Also, this is a quick way to stub the JSON backend of something when I want to start with the frontend, or for testing.

 

 

Polemic :neckbeard:

servehere is MIT licensed, because viral licenses and newspeak language modification are evil. Free is only free when it's free for everyone.