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

nestjs-standard-schema

v0.1.1

Published

NestJS DTO validation based on standard schema

Readme

nestjs-standard-schema

A flexible validation pipe for NestJS that leverages @standard-schema to support multiple validation libraries like Zod, Valibot, ArkType and more.

Features

  • 🔄 Drop-in replacement for NestJS's ValidationPipe
  • 🎯 Support for multiple validation libraries (Zod, Valibot, ArkType, etc.)
  • 🚀 Easy integration with existing NestJS applications
  • 📦 Lightweight with minimal dependencies

Installation

Using npm

npm install nestjs-standard-schema

Using yarn

yarn add nestjs-standard-schema

Using pnpm

pnpm add nestjs-standard-schema

Quick Start

  1. Create your DTO using your preferred validation library (example with Zod):
import { z } from 'zod';
import { createStandardSchemaDTO } from 'nestjs-standard-schema';

const createUserSchema = z.object({
  name: z.string(),
  age: z.number(),
});

export const CreateUserDTO = createStandardSchemaDTO(createUserSchema);
  1. Use the CreateUserDTO in your NestJS application:

import { Controller, Post, Body } from '@nestjs/common';
import { StandardSchemaValidationPipe } from 'nestjs-standard-schema';

@Controller('users')
export class UsersController {
  @Post()
  createUser(@Body(new StandardSchemaValidationPipe()) user: CreateUserDTO) {
    return user;
  }
}

Global Usage

To use the validation pipe globally, register it in your app module:

import { StandardSchemaValidationPipe } from 'nestjs-standard-schema';

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  app.useGlobalPipes(new StandardSchemaValidationPipe());

  await app.listen(3000);
}
bootstrap();

Roadmap

  • [ ] Support for all ValidationPipe options from @nestjs/common
  • [ ] Custom error messages
  • [ ] Transform options
  • [ ] Whitelist/strip options
  • [ ] Detailed validation error messages

Contributing

Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments