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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fp-serv

v0.0.1

Published

## Installation

Downloads

7

Readme

Functional Server Example

Installation

NOTE: This package is not actually on npm yet due to some publishing issues, but will be soon.

npm install --save fp-serv

# or

yarn add fp-serv

Getting Started

Getting a server up and running is as simple as:

const { createServer } = require('fp-serv')

createServer()

You should see a message in the console Server now listening on port 3000

createServer arguments

createServer takes in port, middlewares, and routes, all of which are optional parameters. Below is an example of a very simple server where the output of each request just reveals details about the route and query parameters:

const {
	createServer,
	route,
} = require('fp-serv')

async function handler(req, res) {
	const hasQuery = Object.keys(req.query).length > 0
	const hasParams = Object.keys(req.params).length > 0

	res.write([
		`method: ${req.method}`,
		`path: ${req.url.split('?')[0]}`,
		hasParams ? `params: ${JSON.stringify(req.params)}` : '',
		hasQuery ? `query: ${JSON.stringify(req.query)}` : '',
	].join('\n'))
	res.end()
}

const routes = [
	route.get({
		path: '/',
		handler: handler,
	}),

	route.get({
		path: '/tests/:testId/subItem/:subItemId',
		handler: handler,
	}),

	route.applyNamespace('/api')([
		route.get({
			path: '/blah',
			handler: handler,
		}),

		route.post({
			path: '/blah',
			handler: handler,
		}),

		route.applyNamespace('/v2')([
			route.get({
				path: '/blah',
				handler: handler,
			}),
		]),
	]),
]

createServer({
	port: 3002,
	middlewares: [
		function logRequestTimes(req, res, next) {
			if (req.url === '/favicon.ico') {
				return next()
			}

			const d1 = new Date()

			req.on('end', () => {
				const d2 = new Date()
				const route = `${req.method} ${req.url}`

				console.log(`${route} ${res.statusCode} (${d2 - d1}ms)`)
			})

			next()
		},
	],
	routes,
})