@braze/sanity-plugin-ai-translation 0.2.7 → 0.2.22

package/README.md

@@ -1,499 +1,334 @@
 # @braze/sanity-plugin-ai-translation
 
-A Sanity Studio plugin that adds an AI-powered **Translate** document action for internationalized content.
-
-- **Default provider:** Sanity Agent Actions (`client.agent.action.translate()`)
-- **Optional provider:** OpenAI GPT-5 (direct API) for large documents / long style guides
-- **Output:** Translations are created as **versioned documents inside Content Releases** (staged publishing)
-- **Extras:** translate referenced documents, glossary terms, protected phrases, debug logging, field exclusion, and field transforms (Portable Text + captions)
-
-**For editors:** see the standalone user guide at `docs/user-guide.md`.
-
----
-
-## Table of contents
-
-- [What this plugin does](#what-this-plugin-does)
-- [Prerequisites](#prerequisites)
-- [Install](#install)
-- [Configure (Studio)](#configure-studio)
-  - [1) Configure document internationalization](#1-configure-document-internationalization)
-  - [2) Add the AI translation plugin](#2-add-the-ai-translation-plugin)
-  - [3) Add translation history metadata](#3-add-translation-history-metadata)
-  - [4) Deploy schema for Agent Actions](#4-deploy-schema-for-agent-actions)
-- [Optional: OpenAI mode](#optional-openai-mode)
-- [User guide (for editors)](#user-guide-for-editors)
-  - [Translate a document](#translate-a-document)
-  - [Choose a Content Release](#choose-a-content-release)
-  - [Translation options](#translation-options)
-  - [Translate referenced documents](#translate-referenced-documents)
-  - [What gets created](#what-gets-created)
-- [Content configuration (settings + glossary)](#content-configuration-settings--glossary)
-  - [`translationSettings`](#translationsettings)
-  - [`translationGlossaryTerm`](#translationglossaryterm)
-- [Advanced configuration](#advanced-configuration)
-  - [Exclude fields from translation](#exclude-fields-from-translation)
-  - [Field transforms](#field-transforms)
-  - [Concurrency and depth](#concurrency-and-depth)
-- [Debugging & troubleshooting](#debugging--troubleshooting)
-- [Development (this repo)](#development-this-repo)
-- [License](#license)
-
----
-
-## What this plugin does
-
-When you open a document in Sanity Studio (for a configured schema type), the plugin adds a **Translate** action. You can:
-
-1. Select one or more **target languages**
-2. Choose whether to:
-   - overwrite existing translations
-   - translate only diffs (when applicable)
-   - translate referenced documents (with depth control)
-3. Run translation using:
-   - **Sanity Agent Actions** (default), or
-   - **OpenAI** (optional)
-
-Translations are written as **version documents** in a **Content Release**, so you can review and publish them on your schedule.
-
----
+> A Sanity Studio v3 plugin that provides AI-powered translation capabilities for internationalized content using Sanity Agent Actions.
 
-## Prerequisites
-
-Your Studio must already support internationalized documents.
-
-Required:
-
-- **Sanity Studio v4** (plugin is built for Sanity Studio v4)
-- `@sanity/document-internationalization` configured
-- `sanity-plugin-internationalized-array` installed and configured (used for glossary term translations)
-- `@sanity/client` **7.1.0+** (required for Agent Actions)
+## Features
 
-Also required for Agent Actions:
+- 🤖 **AI-Powered Translation** - Uses Sanity Agent Actions to translate documents between languages
+- 🔄 **Smart Translation Strategies** - Automatically detects translation freshness (fresh/stale/drifted) and applies appropriate strategy
+- 🔗 **Reference Translation** - Optionally translate referenced documents recursively with configurable depth
+- 🎯 **Custom Translation Prompts** - Configure global and locale-specific translation instructions
+- 📚 **Translation Glossary** - Define term-specific translations to ensure consistency
+- 🛡️ **Protected Phrases** - Specify terms that should never be translated (e.g., brand names, product names)
+- 💬 **Feedback System** - AI-powered feedback analysis that automatically improves translation settings
+- ⚙️ **Flexible Configuration** - Control concurrent translation jobs, reference depth, and translation behavior
+- 🔍 **Debug Mode** - Comprehensive logging for troubleshooting translation issues
 
-- Your schema must be deployed to Sanity so Agent Actions can access it (see [Deploy schema](#4-deploy-schema-for-agent-actions))
-- **Important API version requirement:** the client must use `apiVersion: 'vX'` (not date-based versions). Date-based versions can cause Agent Actions to fail.
-
----
-
-## Install
-
-Use your Studio package manager (examples use `pnpm`):
+## Installation
 
 ```sh
 pnpm add @braze/sanity-plugin-ai-translation
 ```
 
-You’ll also need the prerequisites if you haven’t installed them yet:
-
-```sh
-pnpm add @sanity/document-internationalization sanity-plugin-internationalized-array
-pnpm add @sanity/client@^7.1.0
-```
-
----
-
-## Configure (Studio)
-
-### 1) Configure document internationalization
-
-This plugin is designed to work with `@sanity/document-internationalization`. Configure it first.
-
-You’ll typically define your supported languages as:
+## Prerequisites
 
-```typescript
-const SUPPORTED_LANGUAGES = [
-  { id: "en-us", title: "English" },
-  { id: "es", title: "Spanish" },
-  { id: "fr", title: "French" },
-];
-```
+This plugin requires:
 
-Then enable internationalization for the schema types you want to translate:
+1. **Sanity Studio v4** - Version 4.9.0 or later
+2. **@sanity/client** - Version 7.1.0 or later (for Agent Actions)
+3. **@sanity/document-internationalization** - Plugin must be installed and configured
+4. **sanity-plugin-internationalized-array** - Version 3.1.5 or later
 
-```typescript
-documentInternationalization({
-  supportedLanguages: SUPPORTED_LANGUAGES,
-  schemaTypes: ["post", "page"],
-  languageField: "language", // your language field name (example)
-});
-```
+## Configuration
 
-### 2) Add the AI translation plugin
+### Basic Setup
 
-Add `aiTranslationPlugin()` after `documentInternationalization()`:
+Add the plugin to your `sanity.config.ts` file:
 
 ```typescript
-import { defineConfig } from "sanity";
-import { documentInternationalization } from "@sanity/document-internationalization";
-import { aiTranslationPlugin } from "@braze/sanity-plugin-ai-translation";
+import { defineConfig } from 'sanity'
+import { documentInternationalization } from '@sanity/document-internationalization'
+import { aiTranslationPlugin } from '@braze/sanity-plugin-ai-translation'
 
 const SUPPORTED_LANGUAGES = [
-  { id: "en", title: "English" },
-  { id: "es", title: "Spanish" },
-  { id: "fr", title: "French" },
-];
+  { id: 'en', title: 'English' },
+  { id: 'es', title: 'Spanish' },
+  { id: 'fr', title: 'French' },
+  { id: 'de', title: 'German' },
+]
 
 export default defineConfig({
-  // ...your config...
+  // ... other config
   plugins: [
+    // Document internationalization must be configured first
     documentInternationalization({
       supportedLanguages: SUPPORTED_LANGUAGES,
-      schemaTypes: ["post", "page"],
-      languageField: "language",
+      schemaTypes: ['post', 'page', 'product'],
     }),
 
+    // Then add the AI translation plugin
     aiTranslationPlugin({
+      // Required: Array of supported languages
       supportedLanguages: SUPPORTED_LANGUAGES,
-      translatableSchemaTypes: ["post", "page"],
-      languageFieldName: "language",
-      schemaId: "_.schemas.default",
-      maxConcurrentTranslationJobs: 5,
-      maxReferenceDepth: 3,
-    }),
-  ],
-});
-```
-
-**Notes**
-
-- `schemaId` is usually `'_.schemas.default'` for most projects.
-- `languageFieldName` must match the field your documents use (often `language`).
-
-### 3) Add translation history metadata
 
-This plugin can store translation history via a metadata schema you attach to `documentInternationalization`.
+      // Required: Document types that can be translated
+      translatableSchemaTypes: ['post', 'page', 'product'],
 
-Add `translationHistorySchema`:
+      // Required: Field name containing the language identifier
+      languageFieldName: 'language',
 
-```typescript
-import { translationHistorySchema } from "@braze/sanity-plugin-ai-translation";
-
-documentInternationalization({
-  supportedLanguages: SUPPORTED_LANGUAGES,
-  schemaTypes: ["post", "page"],
-  languageField: "language",
-  metadataFields: [translationHistorySchema],
-});
-```
-
-### 4) Deploy schema for Agent Actions
-
-Agent Actions need access to your deployed schema.
+      // Required: Schema ID for Agent Actions (usually '_.schemas.default')
+      schemaId: '_.schemas.default',
 
-From your Studio project directory:
-
-```sh
-npx sanity deploy
+      // Optional: Maximum concurrent translation jobs (default: 5)
+      maxConcurrentTranslationJobs: 5,
+    }),
+  ],
+})
 ```
 
-If Agent Actions fail with schema-related errors, re-check:
-
-- schema deployment
-- `schemaId`
-- client `apiVersion` is set to `'vX'` (not date-based)
+### Configuration Options
 
----
+| Option | Type | Required | Description |
+|--------|------|----------|-------------|
+| `supportedLanguages` | `Array<{id: string, title: string}>` | **Yes** | List of supported languages for translation |
+| `translatableSchemaTypes` | `string[]` | **Yes** | Document types that should have translation actions |
+| `languageFieldName` | `string` | **Yes** | Field name containing the language identifier in documents |
+| `schemaId` | `string` | **Yes** | Schema ID for Sanity Agent Actions (typically `'_.schemas.default'`) |
+| `maxConcurrentTranslationJobs` | `number` | No | Maximum number of concurrent translations (default: 5) |
+| `openai` | `OpenAIConfig` | No | Optional OpenAI integration configuration (see below) |
 
-## Optional: OpenAI mode
+### OpenAI Integration (Optional)
 
-OpenAI mode is optional. If enabled, users can choose **OpenAI** as the translation provider inside the translation dialog.
+The plugin supports optional OpenAI integration for enhanced translation capabilities, including review of Sanity translations and direct GPT-5 translation with no character limits.
 
-Example configuration:
+#### Setup
 
 ```typescript
 aiTranslationPlugin({
-  supportedLanguages: SUPPORTED_LANGUAGES,
-  translatableSchemaTypes: ["post", "page"],
-  languageFieldName: "language",
-  schemaId: "_.schemas.default",
-
+  // ... other required config
   openai: {
-    enabled: true,
-    apiKey: process.env.OPENAI_API_KEY!,
-    model: "gpt-5",
-    reasoningEffort: "medium", // 'minimal' | 'low' | 'medium' | 'high'
-    verbosity: "medium", // 'low' | 'medium' | 'high' (if supported by model)
-    defaultMode: "openai-only", // 'sanity-only' | 'openai-only'
-  },
-});
+    apiKey: process.env.OPENAI_API_KEY!,  // Required
+    model: 'gpt-5',                        // Optional, defaults to 'gpt-5'
+    reasoningEffort: 'medium',             // Optional: 'minimal' | 'low' | 'medium' | 'high'
+    verbosity: 'medium',                   // Optional: 'low' | 'medium' | 'high'
+    enabled: true,                         // Optional, defaults to false
+    defaultMode: 'sanity-with-review',     // Optional, defaults to 'sanity-only'
+  }
+})
 ```
 
-**Security**
-
-- Do not hardcode API keys.
-- Use environment variables (e.g. `.env` / `.env.local`) and your deployment platform’s secret manager.
-
-**Why use OpenAI mode?**
-
-- Larger effective context window for long documents and long style guides
-- Deterministic serialization/deserialization to preserve structure
-- Strict structure validation to prevent data corruption
-
-**Costs**
-
-- OpenAI calls incur API costs based on token usage.
-
----
+**⚠️ Security Note:** Never commit API keys to version control. Always use environment variables:
 
-## User guide (for editors)
+```bash
+# .env.local
+OPENAI_API_KEY=sk-...your-key-here...
+```
 
-### Translate a document
+#### Translation Modes
 
-1. Open a document in Studio whose type is included in `translatableSchemaTypes`.
-2. Open the document actions menu and click **Translate**.
-3. Select one or more target languages.
-4. Configure translation options (see below).
-5. Click **Translate** to start.
+When OpenAI is enabled, users can select from three translation modes:
 
-While translation runs, you’ll see job statuses for each target language (and for any referenced documents, if enabled).
+1. **Sanity Agent Only** (Default)
+   - Uses Sanity's built-in translation agent
+   - Fast and reliable
+   - No additional API costs
+   - 2000 character style guide limit
 
-### Choose a Content Release
+2. **GPT-5 Only** (Beta)
+   - Direct translation via GPT-5
+   - 1 million token context window
+   - Full style guide capacity
+   - Incurs OpenAI API costs
 
-Translations are always created inside a **Content Release**.
+3. **Sanity + GPT-5 Review** (Highest Quality)
+   - Sanity translation reviewed and refined by GPT-5
+   - Best quality results
+   - Approximately 2x processing time
+   - Incurs OpenAI API costs
 
-In the dialog you can typically:
+#### GPT-5 Features
 
-- create a new release, or
-- add the translations to an existing active release
+GPT-5 (released August 2025) provides:
+- **1M token context window** - Handle very large documents and style guides
+- **Advanced reasoning** - Configurable reasoning effort for quality vs. speed tradeoff
+- **Verbosity control** - Adjust response length to optimize token usage
+- **Structure preservation** - Deterministic serialization ensures all document metadata and structure is preserved
 
-Use releases when you want:
+#### Cost Considerations
 
-- staged review
-- coordinated publishing of multiple translations at once
+OpenAI modes incur API costs based on token usage:
+- **GPT-5**: ~$0.002 per 1k input tokens, ~$0.010 per 1k output tokens, ~$0.005 per 1k reasoning tokens
+- **Typical article** (2000 words): ~$0.05-0.15 per translation
+- The plugin shows real-time cost estimates and usage summaries
 
-### Translation options
+#### OpenAI Configuration Options
 
-The exact UI labels may vary, but the workflow supports:
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `apiKey` | `string` | - | OpenAI API key (required if OpenAI enabled) |
+| `model` | `'gpt-5' \| 'gpt-4o' \| 'gpt-4-turbo' \| 'gpt-4'` | `'gpt-5'` | Model to use for translation/review |
+| `reasoningEffort` | `'minimal' \| 'low' \| 'medium' \| 'high'` | `'medium'` | GPT-5 reasoning effort (affects speed and quality) |
+| `verbosity` | `'low' \| 'medium' \| 'high'` | `'medium'` | GPT-5 response verbosity |
+| `enabled` | `boolean` | `false` | Enable OpenAI features |
+| `defaultMode` | `TranslationMode` | `'sanity-only'` | Default translation mode when dialog opens |
 
-- **Overwrite fresh translations**
-  - Forces re-translation even if the existing translation is considered up-to-date.
-- **Translate only diffs**
-  - For stale translations, translate only the changed fields where supported.
-- **Translate references**
-  - Also translate referenced documents and update references to point at the localized versions.
-- **Max reference depth**
-  - How far to traverse reference graphs (depth `0` means no traversal).
+### Schema Setup
 
-### Translate referenced documents
+The plugin requires you to add the `translationHistory` schema to your document internationalization configuration:
 
-If you enable reference translation:
+```typescript
+import { documentInternationalization } from '@sanity/document-internationalization'
+import { translationHistorySchema } from '@braze/sanity-plugin-ai-translation'
 
-- The plugin traverses references (up to the configured depth).
-- It translates referenced documents that are eligible (type is included in `translatableSchemaTypes`).
-- It updates references in the translated document to point to localized versions.
+// In your sanity.config.ts
+documentInternationalization({
+  supportedLanguages: SUPPORTED_LANGUAGES,
+  schemaTypes: ['post', 'page'],
+  // Add translation history to metadata
+  metadataFields: [translationHistorySchema],
+})
+```
 
-This is useful for content like:
+### Deploy Schema
 
-- posts referencing authors
-- pages referencing shared sections
-- documents referencing related content
+After configuration, deploy your schema so Agent Actions can access it:
 
-### What gets created
+```bash
+cd your-sanity-project
+npx sanity deploy
+```
 
-For each selected target language, the plugin creates a **versioned document** inside the selected Content Release.
+## Usage
 
-You can then:
+### Translation Action
 
-- review and edit translated versions
-- publish the release when ready
+Once configured, a "Translate" action will appear on all documents of types listed in `translatableSchemaTypes`.
 
----
+1. Open a document in Sanity Studio
+2. Click the "Translate" action in the document menu
+3. Select target languages
+4. Configure translation options:
+   - **Overwrite fresh translations** - Re-translate even if translation is up-to-date
+   - **Translate only diffs** - For stale translations, only translate changed fields
+   - **Translate references** - Include referenced documents in translation
+   - **Max reference depth** - How deep to traverse references (if enabled)
+5. Click "Translate" to start
 
-## Content configuration (settings + glossary)
+### Translation States
 
-The plugin introduces two document types for configuration:
+The plugin tracks three translation states:
 
-### `translationSettings`
+- **Fresh** ✅ - Translation is up-to-date with source
+- **Stale** ⚠️ - Source document revision changed (trivial changes)
+- **Drifted** 🔴 - Source document content changed significantly
 
-Create a document with `_id == "translation-settings"` to configure:
+Based on state:
+- **Fresh** translations are skipped (unless "Overwrite fresh" is enabled)
+- **Stale** translations can use diff-based translation (if "Translate only diffs" is enabled)
+- **Drifted** translations are fully re-translated
 
-- **Global prompt** (applies to all translations)
-- **Locale prompts** (per-target-language instructions)
-- **Protected phrases** (never translate these terms; e.g. brand names)
+### Translation Settings
 
-Example shape:
+Create a `translationSettings` document to customize translation behavior:
 
 ```typescript
 {
   _type: 'translationSettings',
   _id: 'translation-settings',
+
+  // Global prompt applied to all translations
   globalPrompt: 'Maintain a professional tone. Preserve formatting and links.',
+
+  // Locale-specific prompts
   localePrompts: [
-    {_key: 'es', value: 'Use formal Spanish (usted).'},
-    {_key: 'fr', value: 'Use formal French.'},
+    {
+      locale: 'es',
+      prompt: 'Use formal Spanish (usted). Avoid Latin American regionalisms.'
+    },
+    {
+      locale: 'fr',
+      prompt: 'Use formal French. Maintain gender agreement for all terms.'
+    }
   ],
+
+  // Terms that should never be translated
   protectedPhrases: ['Braze', 'iOS', 'Android', 'SDK']
 }
 ```
 
-Notes:
-
-- `localePrompts` uses `_key` for the locale id (must match your `supportedLanguages[].id`).
-- Protected phrases may be filtered to only those that appear in the source document (to keep prompts smaller).
+### Translation Glossary
 
-### `translationGlossaryTerm`
-
-Create glossary term documents to enforce consistent translations of key terms.
-
-This schema uses `internationalizedArrayString` so you can provide one value per locale.
-
-Conceptual example:
+Create `translationGlossaryTerm` documents for specific term mappings:
 
 ```typescript
 {
   _type: 'translationGlossaryTerm',
   translations: [
-    {_key: 'en', value: 'dashboard'},
-    {_key: 'es', value: 'panel de control'},
-    {_key: 'fr', value: 'tableau de bord'},
+    { locale: 'en', value: 'dashboard' },
+    { locale: 'es', value: 'panel de control' },
+    { locale: 'fr', value: 'tableau de bord' },
+    { locale: 'de', value: 'Dashboard' }
   ]
 }
 ```
 
-Glossary terms are used to build locale-specific translation instructions.
-
----
-
-## Advanced configuration
-
-### Exclude fields from translation
-
-Use `excludeFields` to prevent certain fields from being translated (slugs, enums, flags, etc.).
-
-Supports:
-
-- field name matches anywhere (e.g. `'status'`)
-- exact paths (e.g. `'seo.title'`)
-- array paths / wildcards (e.g. `'body[*].imageType'`)
-
-Example:
-
-```typescript
-aiTranslationPlugin({
-  // ...
-  excludeFields: ["slug", "status", "seo.canonicalUrl", "body[*].variant"],
-});
-```
-
-Important behavior:
+### Give Translation Feedback
 
-- The plugin will **not** allow the `languageFieldName` to be excluded. If you include it, it will be removed to prevent translation errors.
+The plugin includes an AI-powered feedback system that learns from corrections:
 
-### Field transforms
+1. Open a translated document
+2. Click "Give Translation Feedback" action
+3. Provide feedback and/or enable "Include edits" to analyze changes
+4. Review AI-generated suggestions:
+   - Global prompt updates
+   - Locale-specific prompt updates
+   - Protected phrases to add
+   - Glossary terms to add
+5. Approve suggestions to apply
 
-Some fields (like Portable Text or caption formats) benefit from transformation before translation.
+The AI analyzes your feedback and automatically updates translation settings to improve future translations.
 
-Transforms run in this sequence:
+## Translation Workflow
 
-1. Filter excluded fields
-2. Apply transforms (to produce a translatable representation)
-3. Translate (Sanity Agent or OpenAI)
-4. Restore transforms (back into original structure)
-5. Restore excluded fields (except language)
-6. Create version document in the release
+### How It Works
 
-Built-in transforms include:
+1. **Fetch Metadata** - Retrieves translation history and existing translations
+2. **Determine Strategy** - Checks freshness state (fresh/stale/drifted)
+3. **Prepare Translation**:
+   - For **drifted** or **fresh (overwrite)**: Full document translation
+   - For **stale (translate diffs)**: Diff-based translation of changed fields only
+4. **Translate** - Uses Sanity Agent Actions with configured prompts
+5. **Localize References** - Optionally translates referenced documents
+6. **Update Metadata** - Stores translation history with snapshots
 
-- `richTextTransform` for Portable Text
-- `vttCaptionTransform` for VTT captions
-- `wistiaCaptionTransform` for Wistia captions (if used by your schema)
+### Reference Translation
 
-Example setup:
+When "Translate references" is enabled:
 
 ```typescript
-import {
-  aiTranslationPlugin,
-  richTextTransform,
-  vttCaptionTransform,
-  wistiaCaptionTransform,
-} from "@braze/sanity-plugin-ai-translation";
-
-aiTranslationPlugin({
-  // ...
-  fieldTransforms: [
-    {
-      ...vttCaptionTransform,
-      matcher: { schemaType: "video", fieldName: "captions" },
-    },
-    {
-      ...wistiaCaptionTransform,
-      matcher: { schemaType: "videoDoc", fieldName: "wistiaCaptions" },
-    },
-    richTextTransform,
-  ],
-});
-```
-
-**Order matters:** first match wins.
-
-### Concurrency and depth
-
-- `maxConcurrentTranslationJobs` controls how many translations run at the same time (default behavior is conservative).
-- `maxReferenceDepth` controls how deeply references are traversed (set to `0` to disable traversal).
-
----
-
-## Debugging & troubleshooting
-
-### Enable debug logging
-
-This plugin uses a centralized debug logger. To enable debug output in your browser:
-
-```js
-localStorage.setItem("sanity-ai-translation:debug", "true");
-```
-
-To disable:
+// Example: Post with author reference
+{
+  _type: 'post',
+  title: 'My Post',
+  author: { _ref: 'author-en' } // Original English author
+}
 
-```js
-localStorage.removeItem("sanity-ai-translation:debug");
+// After translation with references enabled:
+{
+  _type: 'post',
+  language: 'es',
+  title: 'Mi Publicación',
+  author: { _ref: 'author-es' } // Now points to Spanish author
+}
 ```
 
-### Common issues
+The plugin:
+- Recursively traverses references up to configured depth
+- Translates referenced documents if they don't exist
+- Updates references to point to localized versions
+- Uses semaphore to control concurrent jobs
 
-**Agent Actions fail immediately**
+## Publishing
 
-- Confirm `@sanity/client` is **7.1.0+**
-- Confirm your client API version is `apiVersion: 'vX'` (not date-based)
-- Confirm schema is deployed: `npx sanity deploy`
-- Confirm `schemaId` matches your deployed schema (commonly `'_.schemas.default'`)
+This package is configured for internal publishing to the Braze npm registry.
 
-**Translation completes but content didn’t change**
-
-- Ensure the document type is included in `translatableSchemaTypes`
-- Check whether excluded fields or transforms are preventing updates
-- If using OpenAI mode, structure validation can reject translations that modify non-text fields
-
-**Reference translation is slow**
-
-- Reduce `maxReferenceDepth`
-- Reduce `maxConcurrentTranslationJobs`
-- Ensure you’re not translating large reference graphs unnecessarily
-
----
-
-## Development (this repo)
-
-This repository is a pnpm monorepo with:
-
-- `package/` — the plugin package
-- `demo-nextjs/` — demo Next.js app with embedded Studio
-
-Common commands:
-
-```sh
-pnpm dev
-pnpm build
+```bash
+# Login to registry
+npm login --scope=@braze --registry=https://registry.npmjs.org/
 
+# Build and publish
 cd package
-pnpm test
-pnpm typecheck
-pnpm lint
+pnpm build
+npm publish
 ```
-
----
-
-## License
-
-MIT