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 🙏

© 2025 – Pkg Stats / Ryan Hefner

docuseal-openapi

v1.0.0

Published

API client / fetch wrapper for Docuseal, generated using `@hey-api/typescript` and `@hey-api/fetch`.

Downloads

13

Readme

docuseal-openapi

API client / fetch wrapper for Docuseal, generated using @hey-api/typescript and @hey-api/fetch.

How to use

Import the package using the Github link (until I get around to publishing on an actual package manager). For instance, in Bun, run:

bun i git+https://github.com/Nmans01/docuseal-openapi.git

I have left the code untouched from how it was generated by @hey-api/typescript (more info here). To initialize it, simply import and set your client config. Set baseUrl to https://api.docuseal.co unless you are self-hosting.

import * as docuseal from "docuseal-openapi";

const apiKey = process.env.DOCUSEAL_SECRET;

docuseal.client.setConfig({
    baseUrl: "https://api.docuseal.co",
    headers: {
        "X-Auth-Token": apiKey
    }
});

Every route is exported from the generated code as its own function. By using a * as docuseal import, all routes are autocomplete-able using the docuseal object.

Some notes

  • While I am used to route parameters being referred to in most contexts as "params" in shorthand, hey-api refers to route parameter values as "path". Therefore, when calling a route fuction such as docuseal.getTemplate, it is important to note that passing in the id route parameter will look like this:
docuseal.getTemplate({ path: { id: 123 } });