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

@lcsga/zod-operators

v1.3.0

Published

Provides custom RxJS operators to empower the use of zod.js with RxJS

Downloads

4

Readme

@lcsga/zod-operators

This package provides a custom RxJS operator, used to empower the use of zod schemas alongside RxJS observables.

  • zodParse: This operator is usefull to parse zod schemas within an RxJS stream, in order to check types at runtime.

    zodParse<TInput, TOutput>(schema: ZodType<TOutput, ZodTypeDef, TInput>, options?: { strict?: boolean }): OperatorFunction<TInput, TOutput>

    | argument | type | description | | --------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | schema | ZodType<TOutput, ZodTypeDef, TInput> | The schema to provide for the parsing.A description can also be provided to improve the debugging by calling the describe() method to it. | | options | { strict: boolean } | Optional. Default is {}.A configuration object to modify the behavior of the operator. |

    Example:

    const GithubUserSchema = z.object({
      id: z.string().uuid(),
      login: z.string(),
    });
    
    type GithubUser = z.infer<typeof GithubUserSchema>;
    
    fromFetch<GithubUser[]>('https://api.github.com/users?per_page=5', { selector: (res) => res.json() })
      .pipe(zodParse(GithubUserSchema.array()))
      .subscribe(console.log);

    Since the id of a Github user is of type number and since the zodParse operator is not strict by default, the console.log will return the object fetched without any parsing and the console will print the following warning:

    ZodError: [
      {
        "code": "invalid_type",
        "expected": "string",
        "received": "number",
        "path": [
          0,
          "id"
        ],
        "message": "Expected string, received number"
      },
      {
        "code": "invalid_type",
        "expected": "string",
        "received": "number",
        "path": [
          1,
          "id"
        ],
        "message": "Expected string, received number"
      },
      {
        "code": "invalid_type",
        "expected": "string",
        "received": "number",
        "path": [
          2,
          "id"
        ],
        "message": "Expected string, received number"
      },
      {
        "code": "invalid_type",
        "expected": "string",
        "received": "number",
        "path": [
          3,
          "id"
        ],
        "message": "Expected string, received number"
      },
      {
        "code": "invalid_type",
        "expected": "string",
        "received": "number",
        "path": [
          4,
          "id"
        ],
        "message": "Expected string, received number"
      }
    ]

    If we want to throw an error instead of a simple warning, we can pass an options object as the second argument and set strict to true:

    fromFetch<GithubUser[]>('https://api.github.com/users?per_page=5', { selector: (res) => res.json() })
      .pipe(zodParse(GithubUserSchema.array(), { strict: true }))
      .subscribe(console.log);

    The error will be the same as in the warning above, but this time we won't receive any data in the console.log.