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

express-typescript-jest-supertest

v0.0.75

Published

Tool to generate express boilerplate application

Readme

typescript + express + jest + supertest + swagger boilerplate

Getting started

Run these command in console

  • npm i -g express-typescript-jest-supertest
  • npx express-typescript-jest-supertest nameOfyourAwesomeServer use tab in bash not to enter full package name after you run this commands you will have folder with all required files to write express server

Why do you need it

The purpose of this boilerplate is to have fully configured express project with linter, typescript and integrational testing ready to go. So to start working with application just:

  • npm i
  • npm run dev and local server with live reload would be started for you.

typescript

It is your friend it will show when you sending wrong arguments to function or trying to call a property that doesnt exists. All the type checks is done also in tests and during the development step. So if you made the error in types you got the feedback immediatly.

tsconfig.json

{
    "compilerOptions": {
        "moduleResolution": "node",
        "target": "ES2019",
        "noImplicitAny": true,
        "module": "CommonJS",
        "baseUrl": "./src",
        "rootDir": "./src",
        "outDir": "./build",
        "esModuleInterop": true,
        "allowSyntheticDefaultImports": true,
        "strict": true,
        "paths": {
            "src/*": [
                "./src/*"
            ]
        }
    },
    "include": ["./src"],
    "exclude": ["node_modules"]
}

Code example

users.ts

import {
    Request,
    Response,
    Router,
} from 'express'

const router = Router()

/**
 * @swagger
 *
 * /users:
 *   get:
 *     description: get users
 *     produces:
 *       - application/json
 *     responses:
 *       200:
 *         description: array of users
 */
router.post(
    '/',
    (req: Request, res: Response): void => {
        res.send([{name: 'user1'}, {name: 'user2'}])
    },
)

export default router

users.spec.ts

import path from 'path'
import supertest from 'supertest'

import app from 'server'

describe('Test html root', () => {
    it('success scenario', async (done) => {
        const res = await supertest(app)
            .get('/users')

        expect(res.status).toBe(200)
        expect(res.body).toEqual([{name: 'user1'}, {name: 'user2'}])

        done()
    })
})