For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Copy to LLMGithubGo to App
DocumentationIntegrationsAgent OptimizationSelf-hosting OpikSDK & API referenceOpik University
DocumentationIntegrationsAgent OptimizationSelf-hosting OpikSDK & API referenceOpik University
  • Getting Started
    • Home
    • Quickstart
    • Quickstart notebook
    • Roadmap
    • FAQ
    • Changelog
  • Observability
    • Concepts
    • Log traces
    • Log conversations
    • Log user feedback
    • Log media & attachments
    • Cost tracking
    • Opik Assist
  • Evaluation
    • Overview
    • Concepts
    • Manage datasets
    • Evaluate single prompts
    • Evaluate your agent
    • Evaluate agent trajectories
    • Evaluate multimodal traces
    • Evaluate multi-turn agents
    • Manually logging experiments
    • Re-running an existing experiment
    • Annotation Queues
  • Prompt engineering
    • Prompt management
    • Prompt Playground
    • Prompt Generator and Improver
    • Opik's MCP server
  • Testing
    • Pytest integration
  • Production
    • Production monitoring
    • Online Evaluation rules
    • Gateway
    • Guardrails
    • Anonymizers
    • Alerts
    • Dashboards
  • Administration
    • Overview
    • Roles and Permissions
  • Contributing
    • Contribution Overview
      • Documentation
      • Local Development Setup
      • Python SDK
      • TypeScript SDK
      • Opik Optimizer
      • Frontend
      • Backend
LogoLogo
Copy to LLMGithubGo to App
On this page
  • Contributing to the TypeScript SDK
  • Project Structure
  • Setup
  • Development Workflow
  • Testing
  • Building
  • Documentation
  • Code Style
  • Pull Request Process
  • Need Help?
ContributingSpecific Contribution Guides

TypeScript SDK

Was this page helpful?
Previous

Opik Optimizer

Next
Built with

Contributing to the TypeScript SDK

This guide will help you get started with contributing to the Opik TypeScript SDK.

Before you start, please review our general Contribution Overview and the Contributor License Agreement (CLA).

Project Structure

The TypeScript SDK is located in the sdks/typescript directory. Here’s an overview of the key files and directories:

  • src/: Contains the main source code
  • tests/: Contains test files
  • examples/: Contains example usage of the SDK
  • package.json: Project dependencies and scripts
  • tsconfig.json: TypeScript configuration
  • tsup.config.ts: Build configuration
  • vitest.config.ts: Test configuration

Setup

1

Set up Opik Locally

To develop and test TypeScript SDK features, you’ll need a local Opik instance running:

Linux/Mac
Windows
$# From the root of the repository
$./opik.sh --port-mapping

Note: The --port-mapping flag exposes all service ports (including MySQL on 3306, ClickHouse on 8123, Redis on 6379) which is useful for debugging. The TypeScript SDK routes traffic through the API gateway (nginx) in the frontend service.

Your local Opik server will be accessible at http://localhost:5173.

2

Install dependencies

bash cd sdks/typescript npm install
3

Build the SDK

bash npm run build
4

Run tests

bash npm test

Development Workflow

1

Create a new branch

Create a new branch for your changes
2

Make your changes

Implement your changes
3

Add tests

Add tests for new functionality
4

Run test suite

Run the test suite to ensure everything works
5

Build the SDK

Build the SDK to ensure it compiles correctly
6

Submit PR

Submit a pull request

Testing

We use Vitest for testing. Tests are located in the tests/ directory. When adding new features:

1

Write unit tests

Write unit tests for your changes
2

Run tests

Ensure all tests pass with npm test
3

Check coverage

Maintain or improve test coverage

Building

The SDK is built using tsup. To build:

$npm run build

This will create the distribution files in the dist/ directory.

Documentation

When adding new features or making changes:

1

Update README

Update the README.md if necessary
2

Add JSDoc

Add JSDoc comments for new functions and classes
3

Add examples

Include examples in the examples/ directory
4

Update docs

Update the main documentation if necessary. See the Documentation Guide for details.

Code Style

We use ESLint for code style enforcement. The configuration is in eslint.config.js. Before submitting a PR:

1

Run linter

Run npm run lint to check for style issues
2

Fix issues

Fix any linting errors
3

Check style

Ensure your code follows the project’s style guidelines

Pull Request Process

1

Fork repository

Fork the repository
2

Create branch

Create your feature branch
3

Make changes

Make your changes
4

Run checks

Run tests and linting
5

Submit PR

Submit a pull request

Your PR should:

  • Have a clear description of the changes
  • Include tests for new functionality
  • Pass all CI checks
  • Follow the project’s coding standards

Need Help?

If you need help or have questions:

  • Open an issue on GitHub
  • Join our Comet Chat community
  • Check the existing documentation

Remember to review our Contributor License Agreement (CLA) before contributing.