TypeScript Support

LogicStamp Context is built with TypeScript in mind and provides comprehensive support for TypeScript features, type extraction, and type-safe patterns.

Works alongside tsc: LogicStamp uses the TypeScript compiler API (via ts-morph) to extract contracts. It complements tsc --noEmit (or equivalent) in CI—extraction does not mirror your full-project tsconfig typecheck. Strict compare/watch modes detect contract breaking changes vs a baseline, not every TS error. See Known limitations.

Extends beyond .d.ts surfaces: .d.ts files describe type surfaces for consumers. LogicStamp adds semantic contracts, dependency graphs (graph.nodes/graph.edges), and diffable change hashes (semanticHash/bundleHash) for LLM workflows. Prop types from third-party .d.ts in node_modules are partially supported (Phase 2 pending).

TypeScript Detection

LogicStamp automatically works with TypeScript projects:

File extensions: .ts and .tsx files
Parsing: Each file is loaded with ts-morph using fixed compiler options (ESNext target, JSX enabled for .tsx). Your repo’s full tsconfig is not loaded into the extraction project, so options like strict or custom jsx mode are not fully mirrored during extraction.
Type system: Uses TypeScript’s AST (and the type checker within that isolated project) for extraction
Type definitions: Extracts interfaces, types, and type aliases from the parsed source

What Gets Extracted

Type Definitions

All TypeScript type definitions are extracted:

// types/user.ts
export interface User {
  id: string;
  name: string;
  email: string;
  role: 'admin' | 'user' | 'guest';
  metadata?: {
    createdAt: Date;
    lastLogin?: Date;
  };
}

export type UserId = string;
export type UserRole = User['role'];

Extracted:

Interface definitions with all properties
Type aliases
Union types
Optional properties (?)
Nested types and objects
Index signatures

Component Props Types

TypeScript prop types are fully extracted:

// components/Button.tsx
interface ButtonProps {
  label: string;
  onClick: () => void;
  variant?: 'primary' | 'secondary' | 'danger';
  disabled?: boolean;
  size?: 'sm' | 'md' | 'lg';
}

export function Button({ 
  label, 
  onClick, 
  variant = 'primary',
  disabled = false,
  size = 'md'
}: ButtonProps) {
  // ...
}

Extracted props:

label: string (required)
onClick: () => void (required)
variant: 'primary' | 'secondary' | 'danger' (optional, default: 'primary')
disabled: boolean (optional, default: false)
size: 'sm' | 'md' | 'lg' (optional, default: 'md')

Generic Types

TypeScript generics are captured:

interface ListProps<T> {
  items: T[];
  renderItem: (item: T) => React.ReactNode;
  keyExtractor: (item: T) => string;
}

function List<T>({ items, renderItem, keyExtractor }: ListProps<T>) {
  return (
    <ul>
      {items.map(item => (
        <li key={keyExtractor(item)}>{renderItem(item)}</li>
      ))}
    </ul>
  );
}

Extracted:

Generic type parameters
Generic constraints
Generic usage in props and functions

Utility Types

TypeScript utility types are recognized:

type PartialUser = Partial<User>;
type RequiredUser = Required<User>;
type UserEmail = Pick<User, 'email'>;
type UserWithoutId = Omit<User, 'id'>;
type ReadonlyUser = Readonly<User>;

Extracted:

Utility type usage
Transformed types
Type composition

Enums

TypeScript enums are extracted:

enum Status {
  Pending = 'pending',
  Active = 'active',
  Inactive = 'inactive',
}

enum Direction {
  Up,
  Down,
  Left,
  Right,
}

Extracted:

Enum names and values
String enums
Numeric enums

TypeScript-Specific Features

Type Inference

LogicStamp extracts inferred types where possible:

const users = [
  { id: '1', name: 'Alice' },
  { id: '2', name: 'Bob' },
];

// Inferred type: { id: string; name: string }[]

Type Guards

Type guards are detected:

function isUser(obj: unknown): obj is User {
  return (
    typeof obj === 'object' &&
    obj !== null &&
    'id' in obj &&
    'name' in obj
  );
}

Discriminated Unions

Discriminated union types are extracted:

type Result<T> =
  | { success: true; data: T }
  | { success: false; error: string };

Mapped Types

Mapped types are recognized:

type Optional<T> = {
  [K in keyof T]?: T[K];
};

Type Extraction Quality

LogicStamp uses TypeScript's compiler API (ts-morph) for accurate type extraction:

Accurate types: Uses TypeScript's type checker when possible
Type resolution: Resolves type aliases and imports
Generic inference: Understands generic type parameters
Union types: Fully extracts union and intersection types

Usage

TypeScript projects work out of the box:

# Scan TypeScript project
stamp context

# With type information included
stamp context --include-code full

TypeScript configuration

LogicStamp does not currently merge your project’s full tsconfig.json into the parser Project. That means:

compilerOptions.paths / baseUrl: Used for internal dependency edge resolution in manifests/bundles (including monorepos), but extraction/typechecking still does not fully mirror tsc project behavior.
Strictness and JSX: Extraction uses a built-in option set, not your repo’s strict or jsx compiler choice.

Your tsconfig.json remains important for building and editing the app; it just is not the source of truth for how LogicStamp configures ts-morph today.

Best Practices

Use explicit types: Explicit prop types improve extraction quality
Type your exports: Export types and interfaces for better context
Use TypeScript strict mode: Enables better type checking and extraction
Organize types: Keep types in dedicated files or colocated with components
Avoid any: Use unknown or proper types for better extraction

Limitations

Complex conditional types may not be fully resolved
Type-level computations are not executed
Some advanced TypeScript features may have limited extraction
Circular type references may not be fully resolved
Project tsconfig options are not fully applied to the extraction Project (even though paths / baseUrl are used for dependency edge resolution)

TypeScript Detection

What Gets Extracted

Type Definitions

Component Props Types

Generic Types

Utility Types

Enums

TypeScript-Specific Features

Type Inference

Type Guards

Discriminated Unions

Mapped Types

Type Extraction Quality

Usage

TypeScript configuration

Best Practices

Limitations

Related Documentation

Next Steps

Product

Resources

Organization

Legal