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

@tsofist/schema-forge

v1.34.0

Published

Generate JSON schema from TypeScript types

Downloads

231

Readme

Schema Forge

This library is a set of utilities for generating JSON schemas from TypeScript types of your project, as well as for validating data according to these schemas.

Please note: Instruction is under construction

Use ./test-sources directory and *.spec-files for examples.

Generator

You can organize your types and interfaces in such a way that it is they who generate the json-schema. Thus, unnecessary types will not get into the result. You can also control the descriptions of types and the selectivity of interface members and individual types (be careful with these features, they can lead to the impossibility of full validation on the side that will use this data).

How it works?

Main idea is to create type descriptions by whose schemes in the future it will be possible to validate arbitrary data.

Validator

todo