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

@sdk-it/vite

v0.46.1

Published

Generate a TypeScript SDK during Vite development and builds.

Downloads

930

Readme

@sdk-it/vite

Generate a TypeScript SDK during Vite development and builds.

Install

npm install --save-dev @sdk-it/vite @sdk-it/spec @sdk-it/typescript

Use an OpenAPI file

import { defineConfig } from 'vite';

import sdkIt from '@sdk-it/vite';

export default defineConfig({
  plugins: [
    sdkIt('./openapi.yaml', {
      output: './src/sdk',
      name: 'Example',
      mode: 'minimal',
    }),
  ],
});

Relative paths are resolved from Vite's project root. Local specification files are watched during development, and generation also runs at build start. You can pass an OpenAPI object or a function that resolves to an OpenAPI object or local path instead.

Use a TypeScript backend project

First initialize the SDK-IT project workflow:

npx @sdk-it/cli@latest init

Then add the plugin without an OpenAPI argument:

import { defineConfig } from 'vite';

import sdkIt from '@sdk-it/vite';

export default defineConfig({
  plugins: [sdkIt()],
});

Project mode loads the SDK-IT project config and uses the same generation path as the CLI. Install @sdk-it/cli alongside the plugin for this mode. Pass sdkIt({ config: 'config/sdk-it.ts' }) to use a non-default config location.