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

@aslope/node-test-server

v1.0.2

Published

Server for mocking/simulating HTTP APIs to ease development and testing of client-side code

Downloads

2

Readme

node-test-server

Node-based HTTP server for recording requests and serving responses.

Write automated tests for codebases or programs that don't support intercepting HTTP requests. For example, when testing Node CLI applications inside a child process.

Develop your client-side applications like CLIs or web apps without depending on external HTTP APIs.

Features

📜 MIT licensed

🚀 No dependencies besides TypeScript and others required for building and testing the node-test-server. No headaches with large dependency trees.

🛡️ Supports TLS / HTTPS

✅ Thoroughly tested with unit and integration tests. On all Node versions that did not reach EOL.

🕹️ Control the server programmatically from your TypeScript or JavaScript code. Or control it via its HTTP management API from any other code base.

🧩 OpenAPI 3 specification of node-test-server's HTTP management API for your convenience. Generate client-side code to integrate seamlessly into your tests.

Getting started

Examples

Check out the examples directory for code snippets!

Using npx

# start the server on port 8090
export NODE_TEST_SERVER_PORT=8090
npx @aslope/node-test-server

# define a mock response
curl --request POST \
  --url http://localhost:8090/_/mock-responses \
  --header 'Content-Type: application/json' \
  --data '{
	"mockRequest": {
		"path": "/resources",
		"method": "POST"
	},
	"mockResponses": [
		{
			"status": 201,
			"headers": {
				"Content-Type": "application/json",
				"Location": "/resources/1"
			},
			"body": {
				"hello": "world",
				"foo": "bar"
			}
		}
	],
	"mode": "REPEAT"
}'

# stop the server
curl --request POST \
  --url http://localhost:8090/_/stop

Enable TLS/HTTPS support:

export NODE_TEST_SERVER_TLS_CRT_PATH=path/to/cert.pem
export NODE_TEST_SERVER_TLS_KEY_PATH=path/to/key.pem
npx @aslope/node-test-server

Using TypeScript

import {
  DynamicMockResponse,
  MockRequest,
  MockResponse,
  NodeTestServer,
  NodeTestServerConfig,
  StaticMockResponse
} from '@aslope/node-test-server';
import { IncomingMessage, ServerResponse } from 'http';

const server: NodeTestServer = new NodeTestServer();
const config: NodeTestServerConfig = {
  port: 8090
};
server.startServer(config);

const mockRequest: MockRequest = {
  path: '/resources',
  method: 'POST'
};
const staticMockResponse: StaticMockResponse = {
  status: 201,
  headers: {
    'Content-Type': 'application/json',
    'Location': '/resources/1'
  },
  body: {
    hello: 'world',
    foo: 'bar'
  }
};
const dynamicMockResponse: DynamicMockResponse = (req: IncomingMessage, res: ServerResponse) => {
  res.writeHead(201, {
    'Location': '/resources/1'
  });
  res.end();
};

const mockResponses: MockResponse[] = [staticMockResponse, dynamicMockResponse];
server.setMockResponses(mockRequest, mockResponses, 'REPEAT');

// close after 60 seconds
setTimeout(() => server.stopServer(), 60000);

Enable TLS/HTTPS support:

import {
  NodeTestServer,
  NodeTestServerConfig
} from '@aslope/node-test-server';

const server: NodeTestServer = new NodeTestServer();
const config: NodeTestServerConfig = {
  https: {
    crt: 'path/to/cert.pem',
    key: 'path/to/key.pem'
  }
};
server.startServer(config);

Manually building and testing the application

git clone https://dev.azure.com/aslope/node-test-server/_git/node-test-server
cd node-test-server
npm ci

# Create a self-signed private key and certificate for TLS/HTTPS tests
npm run init:tls

# either build and run the application with your current node version...
npm run build
NODE_TLS_REJECT_UNAUTHORIZED=0 npm test # accept self-signed certificates for HTTPS tests

# ... or build with the lowest, supported node version and test with all supported node versions
./test.sh

# test the openapi file by generating client-side code from it
npm run test:api