ai-world-sdk 1.5.11 → 1.5.13

package/pacakges/ai-sdk-provider/CLAUDE.md

@@ -1,79 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-OpenRouter Provider for Vercel AI SDK (`@openrouter/ai-sdk-provider`) - A TypeScript provider that integrates OpenRouter's API with the Vercel AI SDK, enabling access to 300+ language models through a unified interface.
-
-## Common Commands
-
-```bash
-pnpm build              # Build with tsup (ESM + CJS outputs)
-pnpm dev                # Watch mode development build
-pnpm test               # Run all tests (node + edge environments)
-pnpm test:node          # Run Node.js tests only
-pnpm test:edge          # Run Edge runtime tests only
-pnpm test:e2e           # Run E2E tests (requires OPENROUTER_API_KEY in .env.e2e)
-pnpm typecheck          # TypeScript type checking
-pnpm stylecheck         # Biome linting + formatting check
-pnpm format             # Auto-fix formatting issues
-pnpm changeset          # Create a changeset for release
-```
-
-### Running a Single Test
-
-```bash
-pnpm vitest run src/chat/index.test.ts              # Single test file (node)
-pnpm vitest run src/chat/index.test.ts -t "test name"  # Specific test by name
-```
-
-## Architecture
-
-### Source Structure
-
-```
-src/
-├── provider.ts              # Factory: createOpenRouter() and default openrouter instance
-├── facade.ts                # Deprecated OpenRouter class (legacy support)
-├── chat/index.ts            # OpenRouterChatLanguageModel - main chat implementation
-├── completion/index.ts      # OpenRouterCompletionLanguageModel - completions
-├── embedding/index.ts       # OpenRouterEmbeddingModel - embeddings
-├── types/                   # TypeScript interfaces for settings
-├── schemas/                 # Zod schemas for request/response validation
-└── internal/                # Conditional export: @openrouter/ai-sdk-provider/internal
-```
-
-### Key Patterns
-
-- **Provider Factory**: `createOpenRouter(options)` returns a provider with `.chat()`, `.completion()`, and `.textEmbeddingModel()` methods
-- **Message Conversion**: `convert-to-openrouter-chat-messages.ts` transforms AI SDK messages to OpenRouter format (handles images, files, cache control, tool results)
-- **Dual Build Output**: tsup generates both main (`dist/`) and internal (`dist/internal/`) exports
-
-### Test Environments
-
-Tests run in three environments via separate Vitest configs:
-- **Node.js** (`vitest.node.config.ts`) - Server-side tests
-- **Edge Runtime** (`vitest.edge.config.ts`) - Serverless compatibility
-- **E2E** (`vitest.e2e.config.ts`) - Real API integration (uses `.env.e2e`)
-
-Test files are co-located with source: `src/chat/index.test.ts` tests `src/chat/index.ts`.
-
-## Code Style
-
-- Biome for linting/formatting (2 spaces, single quotes, 80 char line width)
-- Tests may use explicit any and console (configured in biome.json overrides)
-- Import organization: type imports first, then regular imports, then aliases
-
-## Dev Workflow
-
-After completing any implementation task, automatically:
-
-1. Commit **all** changes (including `package.json`, `pnpm-lock.yaml`)
-2. Run `pnpm stylecheck && pnpm typecheck && pnpm test && pnpm build`
-3. Add changeset (`pnpm changeset --empty` for non-user-facing changes)
-4. Create PR on a `claude/` branch using the template in `.github/PULL_REQUEST_TEMPLATE.md`
-5. Wait for CI to pass, fix any issues
-6. Provide the PR link when complete
-
-**Key principle**: Always ensure git state is clean and CI passes before considering work complete. Local tests can pass with uncommitted dependency changes - CI is the source of truth.

package/pacakges/ai-sdk-provider/CONTRIBUTING.md

@@ -1,241 +0,0 @@
-# Contributing to the OpenRouter AI SDK Provider
-
-Thank you for your interest in contributing to the OpenRouter provider for the Vercel AI SDK! This guide will help you get started as a contributor.
-
-## Getting Started
-
-### Prerequisites
-
-- Node.js v18 or higher
-- pnpm v9.15.0 or higher (the project uses pnpm as its package manager)
-
-### Setting Up the Repository
-
-1. Fork the repository on GitHub
-2. Clone your fork locally:
-
-   ```bash
-   git clone https://github.com/YOUR-USERNAME/ai-sdk-provider.git
-   cd ai-sdk-provider
-   ```
-
-3. Install dependencies:
-
-   ```bash
-   pnpm install
-   ```
-
-4. Build the project:
-
-   ```bash
-   pnpm build
-   ```
-
-## Development Workflow
-
-### Building
-
-To build the package during development:
-
-```bash
-# Build once
-pnpm build
-
-# Build in watch mode for continuous development
-pnpm dev
-```
-
-### Code Style and Formatting
-
-We use Biome for code linting and formatting. Before submitting a PR, make sure your code passes all checks:
-
-```bash
-# Check both linting and formatting
-pnpm stylecheck
-
-# Fix formatting issues automatically
-pnpm format
-
-# Run linting and formatting checks
-pnpm stylecheck
-```
-
-### Type Checking
-
-Ensure your changes pass TypeScript type checking:
-
-```bash
-pnpm typecheck
-```
-
-## Testing
-
-The project includes tests for both Node.js and Edge environments. Make sure to run the tests before submitting a PR:
-
-```bash
-# Run all tests
-pnpm test
-
-# Run only Node.js tests
-pnpm test:node
-
-# Run only Edge environment tests
-pnpm test:edge
-```
-
-### Writing Tests
-
-When adding new features or fixing bugs, please include tests. Test files follow the naming convention of `*.test.ts` and are located in the same directory as the files they test.
-
-Examples of test files include:
-
-- `openrouter-chat-language-model.test.ts`
-- `openrouter-usage-accounting.test.ts`
-- `openrouter-stream-usage-accounting.test.ts`
-
-### Issue-Specific Regression Tests
-
-When fixing bugs reported in GitHub issues, add a regression test to the `e2e/issues/` directory. This ensures the issue doesn't recur and provides traceability back to the original report.
-
-**Running issue regression tests:**
-```bash
-# Run issue regression tests separately (not included in test:e2e)
-pnpm test:issues
-```
-
-> **Note:** Issue regression tests are excluded from `pnpm test:e2e` because they may hit different models/APIs that could be slow or rate-limited. Run them separately when needed.
-
-**File naming convention:** `issue-{number}-{brief-description}.test.ts`
-
-**Required test file structure:**
-```typescript
-/**
- * Regression test for GitHub issue #{number}
- * https://github.com/OpenRouterTeam/ai-sdk-provider/issues/{number}
- *
- * Reported error: {exact error message from the issue}
- * Model: {model ID if applicable}
- *
- * This test verifies that {what the test checks}.
- */
-import { ... } from 'ai';
-import { describe, expect, it, vi } from 'vitest';
-import { createOpenRouter } from '@/src';
-
-describe('Issue #{number}: {brief description}', () => {
-  // Test cases that verify the issue is resolved
-});
-```
-
-> **Note:** Only include known facts from the issue report (error message, model, SDK version). Do not include speculative root cause analysis.
-
-**When to add issue regression tests:**
-- Bug fixes that have a clear reproduction case
-- Issues that could potentially regress
-- API compatibility issues with specific models or features
-
-**When NOT to add issue regression tests:**
-- Documentation-only changes
-- Issues that were user configuration errors
-- Transient API issues that were fixed server-side (though you may still add one for monitoring)
-
-## Adding New Features
-
-When adding new features to the OpenRouter provider:
-
-1. Start by understanding the existing architecture in the `src` directory
-2. Update the relevant type definitions in `types.ts` if needed
-3. Implement the feature in the appropriate files
-4. Add tests to verify the functionality
-5. Update the README.md to document the new feature
-6. Update the CHANGELOG.md if applicable
-
-### Example: Usage Accounting Feature
-
-The usage accounting feature provides an example of how to add features to the provider:
-
-1. Added types in `types.ts` for usage accounting
-2. Enhanced response schemas to include usage data
-3. Updated the implementation in `openrouter-chat-language-model.ts`
-4. Added tests in `openrouter-usage-accounting.test.ts` and `openrouter-stream-usage-accounting.test.ts`
-5. Updated README.md with usage examples
-
-## Pull Request Process
-
-> **Important:** All PRs that should trigger a release must include a changeset. Run `pnpm changeset` before submitting your PR.
-
-1. Create a new branch for your changes
-2. Make your changes, including tests and documentation updates
-3. **Add a changeset** to describe your changes:
-   ```bash
-   pnpm changeset
-   ```
-   This will prompt you to select the type of change (patch/minor/major) and write a summary. The changeset will be used to automatically generate release notes and bump versions.
-   
-   - **patch**: Bug fixes and small changes that don't affect the API
-   - **minor**: New features that are backwards-compatible
-   - **major**: Breaking changes
-   
-   If your changes don't need a release (docs, tests, CI config), create an empty changeset:
-   ```bash
-   pnpm changeset --empty
-   ```
-
-4. Run all checks locally before submitting:
-   ```bash
-   pnpm stylecheck    # Check formatting
-   pnpm typecheck     # Check types
-   pnpm build         # Build the project
-   pnpm test          # Run all tests
-   ```
-5. Fix any issues found by the checks (use `pnpm format` for formatting)
-6. Commit with clear, descriptive messages (including the changeset file)
-7. Push to your fork and submit a pull request
-8. Update the PR description with any relevant information
-
-**Note:** Our CI will automatically run all these checks on your PR. PRs with failing checks cannot be merged.
-
-### PR Title Convention
-
-Use a descriptive title that explains the change:
-
-- `fix: <description>` for bug fixes
-- `feat: <description>` for new features
-- `docs: <description>` for documentation changes
-- `test: <description>` for test changes
-- `chore: <description>` for maintenance tasks
-
-## Release Process
-
-This project uses [Changesets](https://github.com/changesets/changesets) for automated release management.
-
-### How it works
-
-1. **Contributors add changesets**: When you submit a PR with changes that affect the public API or fix bugs, you include a changeset file (created with `pnpm changeset`) that describes your changes.
-
-2. **Automated version PR**: When PRs with changesets are merged to `main`, the Release workflow automatically creates or updates a "Version Packages" PR. This PR:
-   - Bumps the version in `package.json` based on all pending changesets
-   - Updates `CHANGELOG.md` with all changes since the last release
-   - Removes the changeset files that have been processed
-
-3. **Publish to npm**: When a maintainer merges the "Version Packages" PR, the package is automatically published to npm with provenance.
-
-### For Maintainers
-
-To release a new version:
-
-1. Review the automatically created "Version Packages" PR
-2. Verify the version bump is appropriate
-3. Verify the CHANGELOG entries are accurate
-4. Merge the PR
-5. The Release workflow will automatically publish to npm
-
-### Manual releases (emergency only)
-
-In case of emergency, a manual release can be triggered using the legacy `publish-manual.yaml` workflow by creating a GitHub Release. This should only be used when the automated process is unavailable.
-
-## Getting Help
-
-If you have questions about contributing, please open a GitHub issue in the repository.
-
-Thank you for contributing to the OpenRouter AI SDK Provider!

package/pacakges/ai-sdk-provider/LICENSE

@@ -1,201 +0,0 @@
-                              Apache License
-                        Version 2.0, January 2004
-                    http://www.apache.org/licenses/
-
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-  "License" shall mean the terms and conditions for use, reproduction,
-  and distribution as defined by Sections 1 through 9 of this document.
-
-  "Licensor" shall mean the copyright owner or entity authorized by
-  the copyright owner that is granting the License.
-
-  "Legal Entity" shall mean the union of the acting entity and all
-  other entities that control, are controlled by, or are under common
-  control with that entity. For the purposes of this definition,
-  "control" means (i) the power, direct or indirect, to cause the
-  direction or management of such entity, whether by contract or
-  otherwise, or (ii) ownership of fifty percent (50%) or more of the
-  outstanding shares, or (iii) beneficial ownership of such entity.
-
-  "You" (or "Your") shall mean an individual or Legal Entity
-  exercising permissions granted by this License.
-
-  "Source" form shall mean the preferred form for making modifications,
-  including but not limited to software source code, documentation
-  source, and configuration files.
-
-  "Object" form shall mean any form resulting from mechanical
-  transformation or translation of a Source form, including but
-  not limited to compiled object code, generated documentation,
-  and conversions to other media types.
-
-  "Work" shall mean the work of authorship, whether in Source or
-  Object form, made available under the License, as indicated by a
-  copyright notice that is included in or attached to the work
-  (an example is provided in the Appendix below).
-
-  "Derivative Works" shall mean any work, whether in Source or Object
-  form, that is based on (or derived from) the Work and for which the
-  editorial revisions, annotations, elaborations, or other modifications
-  represent, as a whole, an original work of authorship. For the purposes
-  of this License, Derivative Works shall not include works that remain
-  separable from, or merely link (or bind by name) to the interfaces of,
-  the Work and Derivative Works thereof.
-
-  "Contribution" shall mean any work of authorship, including
-  the original version of the Work and any modifications or additions
-  to that Work or Derivative Works thereof, that is intentionally
-  submitted to Licensor for inclusion in the Work by the copyright owner
-  or by an individual or Legal Entity authorized to submit on behalf of
-  the copyright owner. For the purposes of this definition, "submitted"
-  means any form of electronic, verbal, or written communication sent
-  to the Licensor or its representatives, including but not limited to
-  communication on electronic mailing lists, source code control systems,
-  and issue tracking systems that are managed by, or on behalf of, the
-  Licensor for the purpose of discussing and improving the Work, but
-  excluding communication that is conspicuously marked or otherwise
-  designated in writing by the copyright owner as "Not a Contribution."
-
-  "Contributor" shall mean Licensor and any individual or Legal Entity
-  on behalf of whom a Contribution has been received by Licensor and
-  subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of
-  this License, each Contributor hereby grants to You a perpetual,
-  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-  copyright license to reproduce, prepare Derivative Works of,
-  publicly display, publicly perform, sublicense, and distribute the
-  Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of
-  this License, each Contributor hereby grants to You a perpetual,
-  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-  (except as stated in this section) patent license to make, have made,
-  use, offer to sell, sell, import, and otherwise transfer the Work,
-  where such license applies only to those patent claims licensable
-  by such Contributor that are necessarily infringed by their
-  Contribution(s) alone or by combination of their Contribution(s)
-  with the Work to which such Contribution(s) was submitted. If You
-  institute patent litigation against any entity (including a
-  cross-claim or counterclaim in a lawsuit) alleging that the Work
-  or a Contribution incorporated within the Work constitutes direct
-  or contributory patent infringement, then any patent licenses
-  granted to You under this License for that Work shall terminate
-  as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the
-  Work or Derivative Works thereof in any medium, with or without
-  modifications, and in Source or Object form, provided that You
-  meet the following conditions:
-
-  (a) You must give any other recipients of the Work or
-      Derivative Works a copy of this License; and
-
-  (b) You must cause any modified files to carry prominent notices
-      stating that You changed the files; and
-
-  (c) You must retain, in the Source form of any Derivative Works
-      that You distribute, all copyright, patent, trademark, and
-      attribution notices from the Source form of the Work,
-      excluding those notices that do not pertain to any part of
-      the Derivative Works; and
-
-  (d) If the Work includes a "NOTICE" text file as part of its
-      distribution, then any Derivative Works that You distribute must
-      include a readable copy of the attribution notices contained
-      within such NOTICE file, excluding those notices that do not
-      pertain to any part of the Derivative Works, in at least one
-      of the following places: within a NOTICE text file distributed
-      as part of the Derivative Works; within the Source form or
-      documentation, if provided along with the Derivative Works; or,
-      within a display generated by the Derivative Works, if and
-      wherever such third-party notices normally appear. The contents
-      of the NOTICE file are for informational purposes only and
-      do not modify the License. You may add Your own attribution
-      notices within Derivative Works that You distribute, alongside
-      or as an addendum to the NOTICE text from the Work, provided
-      that such additional attribution notices cannot be construed
-      as modifying the License.
-
-  You may add Your own copyright statement to Your modifications and
-  may provide additional or different license terms and conditions
-  for use, reproduction, or distribution of Your modifications, or
-  for any such Derivative Works as a whole, provided Your use,
-  reproduction, and distribution of the Work otherwise complies with
-  the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise,
-  any Contribution intentionally submitted for inclusion in the Work
-  by You to the Licensor shall be under the terms and conditions of
-  this License, without any additional terms or conditions.
-  Notwithstanding the above, nothing herein shall supersede or modify
-  the terms of any separate license agreement you may have executed
-  with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade
-  names, trademarks, service marks, or product names of the Licensor,
-  except as required for reasonable and customary use in describing the
-  origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or
-  agreed to in writing, Licensor provides the Work (and each
-  Contributor provides its Contributions) on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-  implied, including, without limitation, any warranties or conditions
-  of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-  PARTICULAR PURPOSE. You are solely responsible for determining the
-  appropriateness of using or redistributing the Work and assume any
-  risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory,
-  whether in tort (including negligence), contract, or otherwise,
-  unless required by applicable law (such as deliberate and grossly
-  negligent acts) or agreed to in writing, shall any Contributor be
-  liable to You for damages, including any direct, indirect, special,
-  incidental, or consequential damages of any character arising as a
-  result of this License or out of the use or inability to use the
-  Work (including but not limited to damages for loss of goodwill,
-  work stoppage, computer failure or malfunction, or any and all
-  other commercial damages or losses), even if such Contributor
-  has been advised of the possibility of such damages.
-
-9. Accepting Warranty or Additional Liability. While redistributing
-  the Work or Derivative Works thereof, You may choose to offer,
-  and charge a fee for, acceptance of support, warranty, indemnity,
-  or other liability obligations and/or rights consistent with this
-  License. However, in accepting such obligations, You may act only
-  on Your own behalf and on Your sole responsibility, not on behalf
-  of any other Contributor, and only if You agree to indemnify,
-  defend, and hold each Contributor harmless for any liability
-  incurred by, or claims asserted against, such Contributor by reason
-  of your accepting any such warranty or additional liability.
-
-END OF TERMS AND CONDITIONS
-
-APPENDIX: How to apply the Apache License to your work.
-
-  To apply the Apache License to your work, attach the following
-  boilerplate notice, with the fields enclosed by brackets "[]"
-  replaced with your own identifying information. (Don't include
-  the brackets!)  The text should be enclosed in the appropriate
-  comment syntax for the file format. We also recommend that a
-  file or class name and description of purpose be included on the
-  same "printed page" as the copyright notice for easier
-  identification within third-party archives.
-
-   Copyright 2025 OpenRouter Inc,
-
-  Licensed under the Apache License, Version 2.0 (the "License");
-  you may not use this file except in compliance with the License.
-  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License.