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

@kajiyamavk/kajix-types

v1.0.0

Published

Shared TypeScript types for Kajix projects

Readme

Kajix Shared Types

This package contains shared TypeScript interfaces and types used across the Kajix monorepo projects.

Overview

The package is set up using TypeScript project references to enable type sharing between projects while maintaining strong typing and ensuring changes are properly propagated.

Directory Structure

packages/types/
├── src/
│   ├── index.ts        - Main export file
│   ├── user.ts         - User-related types
│   ├── llm.ts          - LLM-related types
│   ├── auth.ts         - Authentication-related types
│   └── dto.ts          - General DTO types
├── dist/               - Compiled output (generated)
├── package.json
├── tsconfig.json
└── README.md           - This file

Available Types

The package includes types for:

  • Users (User, CreateUserDto, UpdateUserDto, etc.)
  • LLM Companies and Models (LLMCompany, LLMModel, etc.)
  • Authentication (LoginDto, TokenPayload, LoginResponse, etc.)
  • General DTOs (PaginationParams, PaginatedResponse, ApiErrorResponse, etc.)

Usage

Building the Types Package

From the root of the monorepo:

# Build just the types package
npm run build:types

# Watch for changes during development
npm run watch:types

# Build all projects (types first, then dependent projects)
npm run build:all

Importing Types in Projects

You can import types in two ways:

  1. Direct named imports:
import { User, CreateUserDto, LoginDto } from "@types";

const user: User = {
  // ...
};
  1. Namespace imports:
import * as SharedTypes from "@types";

const user: SharedTypes.User = {
  // ...
};

Development

Adding New Types

  1. Create or modify type definitions in the appropriate file (or create a new file)
  2. Export the types from the file
  3. If you created a new file, make sure to export it from index.ts
  4. Build the types package (npm run build:types)
  5. The types will be available in other projects

Updating Existing Types

When you update types:

  1. Make your changes
  2. Build the types package with npm run build:types
  3. Rebuild dependent projects to ensure they use the updated types

Path Aliases

The monorepo is configured with TypeScript path aliases to make imports cleaner:

// Instead of:
import { User } from "../../../packages/types/src/user";

// You can use:
import { User } from "@types";
// Or
import { User } from "@types/user";