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

gopher-server

v1.0.0

Published

A simple gopher server for Node-JS.

Downloads

1

Readme

gopher-server

npm (tag) npm bundle size (version) npm NPM

A simple gopher server for Node-JS.

Setup

  1. Install using npm install gopher-server

  2. Create the server

    const { GopherServer } = require("gopher-server");
    
    let server = new GopherServer();
  3. Start the server

    server.listen(70);

Creating Content

Content is created through routers. Different routers have different jobs.

Static router

The static router serves content based on files. So, files are layed out like the server will display them.

static
- .gophermap
  content1
  dir1
  - .gophermap
    content2

When accessing a directory, the directory's .gophermap is sent. When the requested resource is a file, the file is sent.

Here is what a .gophermap file may look like.

iHello World	fake	(NULL)	0
0Content 1	/content1	localhost	70

Gopher maps can be confusing to make at first, so the wikipedia page is a good resource. Keep in mind that localhost needs to be changed to your server's hostname. For example, example.com.

app.use(
	new StaticRouter(path.join(__dirname, "static"))
);

Dynamic Router

The dynamic router serves content programmatically. Take for example the dynamic route /test/:id. :id can be replaced by any value. This value can then be used to render and send content to the user.

app.use(
	new DynamicRouter("/test/:id", (request, params) => {
		request.send(`You sent an ID of ${params.id}.`);
	})
);

URL Router

The URL router simply redirects all "URL:" requests to a redirect page. It's more of a utility, and can simply be thrown in and forgotten about.

app.use(new URLRouter());

Example

A full example setup can be found in ./test.