[DASH-1732] [templates] add build step to create javascript templates

.github/CODEOWNERS

@@ -0,0 +1,8 @@
+# When merging changes under these paths to `production`, require review from the
+# Dashboard team.
+/javascript/ @browserbase/dashboard
+/scripts/fetch-playground-typescript-dirs.mjs @browserbase/dashboard
+/scripts/validate-playground-templates.mjs @browserbase/dashboard
+/scripts/playground-ci.mjs @browserbase/dashboard
+/scripts/lib/playground-checks.mjs @browserbase/dashboard
+/.github/workflows/playground-production.yml @browserbase/dashboard

.github/workflows/playground-production.yml

@@ -0,0 +1,60 @@
+# Validates TypeScript → JavaScript builds for templates exposed by the public
+# templates API (playgroundRunnable). Intended for the `production` branch workflow
+# described in https://github.com/browserbase/templates (branch protection: require
+# this check + Dashboard team review before merge).
+#
+# Set TEMPLATES_API_URL to override the default public endpoint (e.g. staging).
+
+name: Playground templates (production)
+
+on:
+  pull_request:
+    branches:
+      - production
+  push:
+    branches:
+      - production
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  playground-templates:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Clean javascript output directory
+        run: rm -rf javascript && mkdir -p javascript
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: pnpm
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Build and validate playground TypeScript templates
+        env:
+          TEMPLATES_API_URL: ${{ vars.TEMPLATES_API_URL }}
+        run: pnpm run ci:playground
+
+      - name: Commit and push playground javascript (push to production only)
+        if: github.event_name == 'push'
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git add -A javascript/
+          if git diff --staged --quiet; then
+            echo "No javascript changes to commit."
+          else
+            git commit -m "chore: regenerate playground javascript templates"
+            git push
+          fi

.github/workflows/playground-test-production.yml

@@ -0,0 +1,60 @@
+# Validates TypeScript → JavaScript builds for templates exposed by the public
+# templates API (playgroundRunnable). Intended for the `test-production` branch workflow
+# described in https://github.com/browserbase/templates (branch protection: require
+# this check + Dashboard team review before merge).
+#
+# Set TEMPLATES_API_URL to override the default public endpoint (e.g. staging).
+
+name: Playground templates (test production)
+
+on:
+  pull_request:
+    branches:
+      - test-production
+  push:
+    branches:
+      - test-production
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  playground-templates:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Clean javascript output directory
+        run: rm -rf javascript && mkdir -p javascript
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: pnpm
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Build and validate playground TypeScript templates
+        env:
+          TEMPLATES_API_URL: ${{ vars.TEMPLATES_API_URL }}
+        run: pnpm run ci:playground
+
+      - name: Commit and push playground javascript (push to test-production only)
+        if: github.event_name == 'push'
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git add -A javascript/
+          if git diff --staged --quiet; then
+            echo "No javascript changes to commit."
+          else
+            git commit -m "chore: regenerate playground javascript templates"
+            git push
+          fi

README.md

@@ -67,6 +67,12 @@ Templates use the Model Gateway to route LLM requests -- you only need your `BRO
 
 Each template's README contains detailed installation steps, environment variable requirements, and troubleshooting guides.
 
+### TypeScript and generated JavaScript
+
+- **Source of truth:** edit templates under `typescript/`. The `javascript/` tree is generated output, not authored by hand for day-to-day changes.
+- **Local only:** run `pnpm run build:javascript` when you want a full mirror of `typescript/` into `javascript/` on your machine (for example to smoke-test the transpiler or compare JS output). There is **no** GitHub Actions workflow that builds the full tree into the repo anymore.
+- **Playground releases:** the `production` branch is updated by CI (`.github/workflows/playground-production.yml`), which builds and commits **only** templates that are playground-runnable per the public templates API, then validates them.
+
 ## Resources
 
 ### Documentation

javascript/amazon-global-price-comparison/.env.example

@@ -0,0 +1,2 @@
+# Browserbase credentials - get these from https://www.browserbase.com/settings
+BROWSERBASE_API_KEY=your_browserbase_api_key

javascript/amazon-global-price-comparison/README.md

@@ -0,0 +1,66 @@
+# Amazon Global Price Comparison
+
+## AT A GLANCE
+
+- Goal: compare Amazon product prices across multiple countries using geolocation proxies.
+- Uses Browserbase's managed proxy infrastructure to route traffic through different geographic locations (US, UK, Germany, France, Italy, Spain).
+- Extracts structured product data (name, price, rating, reviews) using Stagehand's extraction capabilities with Zod schema validation.
+- Sequential processing shows how different proxy locations return different pricing from the same Amazon search.
+- Docs → https://docs.browserbase.com/features/proxies
+
+## GLOSSARY
+
+- geolocation proxies: route traffic through specific geographic locations (city, country) to access location-specific content and pricing
+  Docs → https://docs.browserbase.com/features/proxies#set-proxy-geolocation
+- extract: extract structured data from web pages using natural language instructions and Zod schemas
+  Docs → https://docs.stagehand.dev/basics/extract
+- proxies: Browserbase's managed proxy infrastructure supporting 201+ countries for geolocation-based routing
+  Docs → https://docs.browserbase.com/features/proxies
+
+## QUICKSTART
+
+1. cd amazon-global-price-comparison
+2. pnpm install
+3. cp .env.example .env
+4. Add your Browserbase API key to .env
+5. pnpm start
+
+## EXPECTED OUTPUT
+
+- Creates Browserbase sessions with geolocation proxies for each country (US, UK, DE, FR, IT, ES)
+- Navigates to Amazon search results through location-specific proxies
+- Extracts product name, price, rating, and review count for each location
+- Displays formatted comparison table showing price differences across countries
+- Outputs JSON results for programmatic use
+
+## COMMON PITFALLS
+
+- Browserbase Developer plan or higher is required to use proxies
+- "Cannot find module": ensure all dependencies are installed (`pnpm install`)
+- Missing credentials: verify .env contains BROWSERBASE_API_KEY
+- Geolocation fields are case-insensitive (city, country can be any case)
+- Amazon may show different products in different regions - comparison works best for globally available products
+- ERR_TUNNEL_CONNECTION_FAILED: indicates either a temporary proxy hiccup or a site unsupported by built-in proxies
+
+## USE CASES
+
+• Price arbitrage: Find the best country to purchase products from for international shipping
+• Market research: Compare pricing strategies across different Amazon regions
+• Competitive analysis: Monitor how competitors price products globally
+• Travel shopping: Check prices before international trips to plan purchases
+
+## NEXT STEPS
+
+• Add more countries: Extend the COUNTRIES array with additional regions (Japan, Australia, Canada, etc.)
+• Currency conversion: Add real-time currency conversion to normalize prices for comparison
+• Price tracking: Store results over time to track price changes across regions
+• Email alerts: Send notifications when price drops below a threshold in any country
+
+## HELPFUL RESOURCES
+
+📚 Stagehand Docs: https://docs.stagehand.dev/v3/first-steps/introduction
+🎮 Browserbase: https://www.browserbase.com
+💡 Try it out: https://www.browserbase.com/playground
+🔧 Templates: https://www.browserbase.com/templates
+📧 Need help? support@browserbase.com
+💬 Discord: http://stagehand.dev/discord