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

@akash-electron/ts-backend

v1.0.6

Published

A robust, scalable, and production-ready starter template for building Node.js backends with TypeScript. This boilerplate follows industry best practices for architecture, error handling, and type safety.

Readme

🚀 Quick Start

Initialize your new TypeScript backend project in seconds:

# Create a new project in the current directory
npx @akash-electron/ts-backend .

# OR create a new project in a new folder
npx @akash-electron/ts-backend my-backend-api

📦 What's Included?

This package is a full-featured boilerplate generator that sets up:

  • TypeScript pre-configured for Node.js
  • Express 5 for modern routing
  • Zod for schema validation
  • Winston & Morgan for structured logging
  • CatchAsync & AppError for clean, centralized error handling
  • Security with helmet and cors
  • Developer Experience with nodemon and ts-node

📂 Project Structure

src/
├── config/             # Env vars, database, and logger config
├── controllers/        # Request/Response logic
├── middlewares/        # Error handlers, auth, etc.
├── models/             # Data schemas
├── routes/             # API endpoints
├── services/           # Business logic
├── utils/              # Global helpers (AppError, catchAsync)
├── validations/        # Zod validation schemas
├── types/              # TS interface definitions
├── app.ts              # Express setup
└── server.ts           # Server entry point

🛠️ Usage Post-Initialization

Once you run the initialization command:

  1. Install Dependencies
    npm install
  2. Setup Environment Rename .env.example to .env and configure your variables.
  3. Run in Development
    npm run dev
  4. Build for Production
    npm run build

🛡️ Important Files (Quick Reference)

src/utils/AppError.ts

export class AppError extends Error {
  public readonly statusCode: number;
  public readonly isOperational: boolean;

  constructor(message: string, statusCode: number) {
    super(message);
    this.statusCode = statusCode;
    this.isOperational = true;
    Error.captureStackTrace(this, this.constructor);
  }
}

src/middlewares/errorMiddleware.ts

import { Request, Response, NextFunction } from "express";
import { AppError } from "../utils/AppError";

export const globalErrorHandler = (
  err: any,
  req: Request,
  res: Response,
  next: NextFunction,
) => {
  err.statusCode = err.statusCode || 500;
  err.status = err.status || "error";

  res.status(err.statusCode).json({
    status: err.status,
    message: err.message,
    ...(process.env.NODE_ENV === "development" && { stack: err.stack }),
  });
};

src/utils/catchAsync.ts

import { Request, Response, NextFunction } from "express";

export const catchAsync = (fn: Function) => {
  return (req: Request, res: Response, next: NextFunction) => {
    fn(req, res, next).catch(next);
  };
};

📝 Best Practices Included

  • Environment Safety: Validate .env variables at startup.
  • Security Check: Pre-configured with helmet for secure headers.
  • Clean Code: Deep separation of concerns (Routes → Controllers → Services).
  • Graceful Shutdown: Handles SIGTERM and SIGINT signals to close DB connections properly.