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

@typed-web-api/express

v1.1.3

Published

express specific functionality for the @typed-web-api library

Downloads

11

Readme

@typed-web-api/express

Server library to validate the return type of an express web API's endpoints, based on a type declaration generated via @typed-web-api/common. Additionally, it can also be used to infer the types of the Http requests' payload.

Example

Given the following sample express web API:

import express from 'express';

const app = express();

/* ... */

app.post('/users/login', async (req, res) => {
  /* ... */
  res.status(X).send(loginResponse);
});

app.get('/users' async (req, res) => {
  /* ... */
  res.send(users);
});

app.get('/users/:userId', async (req, res) => {
  /* ... */
  res.send(user);
});

app.listen(process.env.PORT || 3000);

This is how to validate the endpoints' return type by using useServerEndpoints (given the sample UserEndpoints type described in @typed-web-api/common):

import { ServerEndpoints, useServerEndpoints } from '@typed-web-api/express';
import express from 'express';
import { UserEndpoints } from '...';

const app = express();

/* ... */

const usersController: ServerEndpoints<UserEndpoints> = {
  '/users/login_post': async (req) => {
    /* ... */
    return { payload: loginResponse, status: X }; // Expected payload type => LoginResponse;
  },
  '/users_get': async (req) => {
    /* ... */
    return { payload: users }; // Expected payload type => User[]
  },
  '/users/:userId_get': async (req) => {
    /* ... */
    return { payload: user }; // Expected payload type => User
  },
};

useServerEndpoints(app, usersController);

app.listen(process.env.PORT || 3000);

Optionally the payload of the express request objects can be inferred as well by using additional helper types:

const usersController: ServerEndpoints<UserEndpoints> = {
  '/users/login_post': async (req: TypedExpressRequest<UserEndpoints, '/users/login_post'>) => {
    const { email, password } = req.body; // email: string, password: string
    /* ... */
  },
  '/users_get': async (req: TypedExpressRequest<UserEndpoints, '/users_get'>) => {
    const { limit, skip } = req.query; // limit: string, skip: string
    /* ... */
  },
  '/users/:userId_get': async (req: TypedExpressRequest<UserEndpoints, '/users/:userId_get'>) => {
    const { userId } = req.params; // userId: string
    /* ... */
    return { payload: user }; // Expected payload type => User
  },
};

API

useServerEndpoints(appOrRouter, endpoints)

Returns

An object with a list of endpoints exposed successfully (i.e. exposedEndpoints) and a list of endpoints which failed to be exposed (i.e. failedEndpoints) due to invalid endpoint name.

Arguments

  • appOrRouter: The express() or express.Router() instance where the endpoints will be exposed.
  • endpoints: The endpoint handlers to be exposed.

Example

import { ServerEndpoints, useServerEndpoints } from '@typed-web-api/express';
import express from 'express';
import { WebApiEndpoints } from '...';

const app = express();
app.use(express.json());

useServerEndpoints(app, <WebApiEndpoints>{
  '/users/login_post': (req, res, next) => {
    /* ... */
  },
  '/users_get': (req, res, next) => {
    /* ... */
  },
  '/users/:userId_get': (req, res, next) => {
    /* ... */
  },
});

app.listen(process.env.PORT || 3000);