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

zod-extended

v1.0.5

Published

Do more with your Zod schemas.

Downloads

6

Readme

Zod Extended

Do more with your Zod schemas.

npm add zod-x

API

zx(schema)

Resolve

Resolve/computed fields according to a parent object.

Description

The resolve functionality aims to make "field-resolution" or "computed fields" simple in Zod. Computed or resolved fields enable deriving new fields based on existing object fields. A common use case for computed fields is collecting relation data.

⚠️ This requires using .parseAsync() to parse schema

Usage

First define a "resolveable" field on an object.

// Schema of resolved type
const Photo = z.object({
	src: z.string(),
	width: z.number(),
	height: z.number()
})

const User = z.object({
	id: z.string(),
	photoId; z.string(),

	// Add a resolved field
	Photo: zx(Photo).resolve(async (parent) => {
		return db.photo.findUnique({
			where: { id: parent.photoId }
		})
	})
})

By default these resolvers won't ever be run, and the computed fields never populated, until you wrap a schema in the .resolved() function.

// Upon .parseAsync(), the resolved fields will be appended to the resulting value.
const UserWithResolved = zx.resolved(User);

By moving this relation data-fetching to the application boundary, we can easily include and exclude relation data, without altering our business logic in our functions.