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

@jsoverson/test-server

v1.3.3

Published

Quick local server for http integration tests

Downloads

153

Readme

Local test server

This is a quick server library that exposes one async, start to control a local static file server. You can only control the path that is served. The port is assigned for you and this always binds to 127.0.0.1.

Who is this for?

People who want to test interaction with an HTTP server and want to control that dependency locally so tests don't have to reach out to the internet.

Usage

const {start} = require('@jsoverson/test-server');
const fetch = require('node-fetch');

(async function () {
  const server = await start();

  console.log(`Server started on port ${server.port}, serving directory ${server.path}.`);

  const response = await fetch(server.url('index.html'));

  await server.stop();
})();

Magic URLs

/drop : any URL ending in /drop will drop the connection

/wait/#### : any URL ending in /wait/#### (e.g. /wait/5000) will wait #### milliseconds before responding. The response is the time actually waited.

/status/#### : any URL ending in /status/#### (e.g. /status/404) will return an HTTP status of ####. The response text is also the status code.

Debugging

This library uses debug so you can start your script with DEBUG=test-server* yourScript.js to get debug output.

API

start(...pathParts = [process.cwd(), 'server_root']) returns TestServer

pathParts are the parts of the path that can be passed to path.join(). Defaults to a 'server_root' directory in the current working directory.

TestServer();

.port

The assigned port

.path

The path that is being served

.address

The http path + port.

.url(path)

Convenience method that appends path to .address