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

yaschema-api-fetcher

v5.1.0

Published

Fetch support for yaschema-api

Downloads

393

Readme

yaschema-api-fetcher

Downloads Size

Fetch support for yaschema-api.

Basic Example

// You'll typically define this in a separate library shared by your server and clients
export const postPing = makeHttpApi({
  method: 'POST',
  routeType: 'rest',
  url: '/ping',
  isSafeToRetry: true,
  schemas: {
    request: {
      body: schema.object({
        echo: schema.string().allowEmptyString().optional()
      })
    },
    successResponse: {
      status: schema.number(StatusCodes.OK),
      body: schema.string()
    }
  }
});
// Use the API via fetch to post the specified string
const doPing = async (echo?: string) => {
  const pingRes = await apiFetch(postPing, { body: { echo } });
  if (!pingRes.ok) {
    console.error('Something went wrong', pingRes)
    return;
  }

  console.log(pingRes.body);
}

The above example demonstrates compile-time, type-safe use of a yaschema-api, which also performs runtime validation. With yaschema-api, both the client and server can use the same API definitions. However, it's also fine for the API definitions to be used in a one-sided way, for example, when integrating with third-party REST APIs.

With yaschema-api, types can be defined for:

  • request headers, params, query, and body
  • success response status, headers, and body
  • expected failure response status, headers, and body

Using with node.js

yaschema-api-fetcher works out-of-the-box for web, but it can also work with node.js. To set the package up to work with node, do something like:

import nodeFetch, { Blob, FormData } from 'node-fetch';
import type { BlobConstructor, Fetch } from 'yaschema-api-fetcher';
import { setBlobConstructor, setFetch, setFormDataConstructor } from 'yaschema-api-fetcher';

…

setFetch(nodeFetch as Fetch);
// The following are only needed to support form-data requests
setFormDataConstructor(FormData);
setBlobConstructor(Blob as BlobConstructor);

You should do these once around application start time, before apiFetch is used.

Thanks

Thanks for checking it out. Feel free to create issues or otherwise provide feedback.

API Docs

Be sure to check out our other TypeScript OSS projects as well.