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

@nxht/typebox-extended-openapi

v0.0.8

Published

Collection of custom [@sinclair/typebox](https://github.com/sinclairzx81/typebox) schema, primarily for OpenAPI specification.

Downloads

28

Readme

Typebox Extended for OpenAPI

Collection of custom @sinclair/typebox schema, primarily for OpenAPI specification.

Install

$ npm install @nxht/typebox-extended-openapi

Types

StringEnum

Similar to Type.Enum but

  • Only accepts string.
  • Uses JSONSchema enum keyword instead of anyOf for OpenAPI compatibility.
  • Unlike using Type.Unsafe, this Validates if the value is in the enum list.
import { TypeX, TypeXGuard } from '@nxht/typebox-extended-openapi';
import { Value } from '@sinclair/typebox/value';

const T = TypeX.StringEnum(['a', 'b', 'c']);
// Json Schema
// const T = {
//   type: "string",
//   enum: [ "a", "b", "c" ],
// }

type T = Static<typeof T>;
// type T = 'a' | 'b' | 'c'

Value.Check(T, 'a') // true
Value.Check(T, 'd') // false

// TypeGuard for StringEnum
TypeXGuard.IsStringEnum(T); // true

StringWithAutoComplete

Similar to TypeX.StringEnum but doesn't validate if the value is in the enum list.

import { TypeX, TypeXGuard } from '@nxht/typebox-extended-openapi';

const T = TypeX.StringWithAutoComplete(['a', 'b', 'c']);
// Json Schema
// const T = {
//   type: "string",
//   enum: [ "a", "b", "c" ],
// }

type T = Static<typeof T>;
// type T = "a" | "b" | "c" | (string & {})

Value.Check(T, 'a') // true
Value.Check(T, 'd') // true

Nullable

  • Makes a schema nullable
  • Unlike Type.Union([Type.Null(), schema]), this emit JSONSchema nullable: true instead of using anyOf
  • Unlike using Type.Unsafe, this schema doesn't emit error if the value is null

Known limitations

  • TypeGuard doesn't work as this has Nullable schema type
import { TypeX, TypeXGuard } from '@nxht/typebox-extended-openapi';
import { Value } from '@sinclair/typebox/value';

const T = TypeX.Nullable(Type.String());
// Json Schema
// const T = {
//   type: "string",
//   nullable: true
// }

type T = Static<typeof T>;
// type T = string | null

Value.Check(T, 'a') // true
Value.Check(T, null) // true
Value.Check(T,  1) // false

Merge

Merge multiple Typebox schema into one

  • Unlike Type.Intersect, the result schema will have merged properties instead of allOf which could be better for OpenAPI specification readability.
  • Unlike Type.Composite, if there's key conflict, the right-most schema will be used. Also, much faster type inference.
import { Type, type Static } from '@sinclair/typebox';
import { TypeX } from '@nxht/typebox-extended-openapi';

const T = TypeX.Merge([
  Type.Object({ a: Type.String() }),
  Type.Object({ a: Type.Number(), b: Type.String() }),
]);

type T = Static<typeof T>;
// type T = {
//   a: number;
//   b: string;
// }