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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@viatick/jarvis-apis-sdk

v2.3.1

Published

This package is generated by the monorepo custom SDK generator.

Readme

Jarvis APIs SDK

This package is generated by the monorepo custom SDK generator.

Generate the SDK from an exported OpenAPI JSON file only. Do not generate from a running local REST server endpoint.

Get The API JSON

# Export the OpenAPI JSON from main-rest-server
yarn workspace @viatick/jarvis-rest-server openapi:export

Default output:

packages/apis-sdk/fixtures/main-rest-server.openapi.json

Commands

# Generate the SDK from the exported API JSON file
yarn workspace @viatick/jarvis-apis-sdk generate --input fixtures/main-rest-server.openapi.json

# Refresh the temporary local schema allowlist from the same API JSON file
yarn workspace @viatick/jarvis-apis-sdk sync:local-schema-allowlist --input fixtures/main-rest-server.openapi.json

# Refresh the local enum allowlist after regeneration
yarn workspace @viatick/jarvis-apis-sdk sync:local-enum-allowlist

# Run generator tests
yarn workspace @viatick/jarvis-apis-sdk test:generator

# Build the published SDK output
yarn workspace @viatick/jarvis-apis-sdk build

# Recommended repo-level check
CI=1 yarn build:projects @viatick/jarvis-apis-sdk @viatick/jarvis-main-platform

# Stage a self-contained npm package under tmp/publish/apis-sdk
yarn apis-sdk:stage:npm

# Create an npm tarball from the staged package
yarn apis-sdk:pack:npm

# Publish the staged package to npm
yarn apis-sdk:publish:npm

Notes

  • If generation fails because a schema or enum should come from shared types, update src/generator-config/schema-type-map.ts.
  • Keep temporary local schema ownership in src/generator-config/local-schema-allowlist.ts.
  • Keep intentional local enums in src/generator-config/local-enum-allowlist.ts.
  • The npm publish flow stages a separate self-contained package under tmp/publish/apis-sdk and does not change the normal monorepo build output.

Roadmap

  • Keep moving shared enum ownership into @viatick/jarvis-shared-types when the contract is already stable.
  • Reduce compatibility wrappers to only the legacy cases that still need them.
  • Gradually move more request and response DTO ownership out of local generated SDK models where shared types are the source of truth.