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

@tealina/client

v1.0.2

Published

Parse tealina-server type for client.

Readme

Type-Safe API Client Utilities

A collection of functions for creating fully type-safe API request clients with seamless integration for both Fetch and Axios.

Overview

These utilities provide type-safe API client creation with two distinct styles:

  • RPC-style: Method-chain syntax for intuitive API calls
  • Traditional-style: Familiar HTTP method functions with endpoint paths

Installation

npm install @tealina/client

Defining API Types

First, define your API structure using TypeScript interfaces:

import type { ApiTypesRecord } from '@tealina/client'

type ApiTypesRecord = {
  // First level represents HTTP methods
  get: {
    // Second level defines endpoint URLs
    '/status': {  
      response: {} 
      // Optional request payload definitions
      params?: {}
      query?: {}
      headers?: {}
      body?: {}
    }
    '/user/:id': { // Named parameters are supported
      response: { name: string }
      params: { id: string }
      //... other request options
    }
    // ... other API endpoints
  }

  post: {
    // ... POST endpoints
  }
  
  // Support for other HTTP methods (put, delete, patch, etc.)
}

It's recommend using create-tealina to scaffold your project, which provides pre-configured ApiTypeRecord imports from the server - no manual setup required.

RPC Style (Method Chaining)

import { createFetchRPC } from '@tealina/client'
import type { ApiTypesRecord } from 'server/api/v1'

const rpc = createFetchRPC<ApiTypesRecord, RequestInit>(async (url, config) => {
  const response = await fetch(url, config)
  const data = await response.json()
  return data
})

// Usage examples
rpc.get.status().then(result => console.log(result))

rpc.get.user[':id']({ params: { id: 'user_id' } }).then(user => console.log(user.name))

Traditional Style

import axios, { type AxiosRequestConfig } from 'axios'
import { createAxiosReq } from '@tealina/client'
import type { ApiTypesRecord } from 'server/api/v1'

const instance = axios.create({
  baseURL: '/api/v1/',
})

export const req = createAxiosReq<ApiTypesRecord, AxiosRequestConfig>(c =>
  instance.request(c).then(v => v.data),
)

// Usage
req.get('/status').then(result => console.log(result))

How It Works

The createXX functions handle type adaptation and parameter conversion, returning a proxy object that ultimately invokes your provided handler function. This approach ensures:

  • Autocompletion for all endpoints and parameters
  • Flexible adapter pattern for any HTTP client library

Key Features

  • 🔒 Type Safety: Complete end-to-end type checking
  • 🎯 IntelliSense: Full autocompletion for API endpoints and parameters
  • 🔌 Adapter Support: Works with Fetch, Axios, or any custom HTTP client
  • 🏗️ Two Styles: Choose between RPC-style or traditional HTTP-style
  • 📦 Lightweight: Zero dependencies, minimal bundle impact