Skip to content

Extract reusable <DataInspector> component and fix class instance rendering#1032

Merged
TooTallNate merged 1 commit into
mainfrom
02-12-extract_reusable_datainspector_component_and_fix_class_instance_rendering
Feb 13, 2026
Merged

Extract reusable <DataInspector> component and fix class instance rendering#1032
TooTallNate merged 1 commit into
mainfrom
02-12-extract_reusable_datainspector_component_and_fix_class_instance_rendering

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

Consolidate all ObjectInspector usage into a single DataInspector component
with shared theming, custom nodeRenderer for StreamRef/ClassInstanceRef, and
stream click context. Update all consumers (attribute-panel, events-list,
event-list-view, stream-viewer, conversation-view) to use DataInspector
instead of direct ObjectInspector or JSON.stringify. Fix class instance
hydration to create objects with dynamically-named constructors so
react-inspector shows proper class names via constructor.name.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 13, 2026

🦋 Changeset detected

Latest commit: 5493314

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@workflow/web-shared Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 13, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 0.031s (+13.4% 🔺) 1.005s (~) 0.973s 10 1.00x
💻 Local Nitro 0.032s (~) 1.005s (~) 0.973s 10 1.04x
💻 Local Next.js (Turbopack) 0.040s 1.005s 0.965s 10 1.27x
🌐 Redis Next.js (Turbopack) 0.048s 1.005s 0.957s 10 1.53x
🌐 MongoDB Next.js (Turbopack) 0.084s 1.007s 0.923s 10 2.69x
🐘 Postgres Express 0.154s (+68.9% 🔺) 1.010s (~) 0.855s 10 4.93x
🐘 Postgres Nitro 0.218s (+3.7%) 1.010s (~) 0.791s 10 6.98x
🐘 Postgres Next.js (Turbopack) 0.385s 1.009s 0.625s 10 12.29x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.540s (-28.2% 🟢) 1.812s (-11.1% 🟢) 1.272s 10 1.00x
▲ Vercel Nitro 0.599s (~) 1.804s (-9.5% 🟢) 1.205s 10 1.11x
▲ Vercel Next.js (Turbopack) 0.606s (-12.3% 🟢) 2.009s (-6.1% 🟢) 1.404s 10 1.12x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.099s 2.006s 0.907s 10 1.00x
💻 Local Next.js (Turbopack) 1.099s 2.006s 0.907s 10 1.00x
💻 Local Express 1.101s (+2.0%) 2.005s (~) 0.903s 10 1.00x
💻 Local Nitro 1.108s (~) 2.006s (~) 0.898s 10 1.01x
🌐 MongoDB Next.js (Turbopack) 1.293s 2.007s 0.714s 10 1.18x
🐘 Postgres Next.js (Turbopack) 1.769s 2.012s 0.243s 10 1.61x
🐘 Postgres Express 2.327s (-5.7% 🟢) 3.013s (~) 0.686s 10 2.12x
🐘 Postgres Nitro 2.445s (~) 3.014s (~) 0.570s 10 2.22x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.276s (-8.2% 🟢) 3.027s (-13.2% 🟢) 0.751s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.383s (-8.3% 🟢) 3.339s (-2.7%) 0.956s 10 1.05x
▲ Vercel Express 2.388s (-0.7%) 3.284s (+4.4%) 0.897s 10 1.05x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.709s 11.021s 0.312s 3 1.00x
🌐 Redis Next.js (Turbopack) 10.710s 11.022s 0.312s 3 1.00x
💻 Local Express 10.821s (+2.2%) 11.022s (~) 0.201s 3 1.01x
💻 Local Nitro 10.854s (~) 11.022s (~) 0.169s 3 1.01x
🌐 MongoDB Next.js (Turbopack) 12.180s 13.018s 0.839s 3 1.14x
🐘 Postgres Next.js (Turbopack) 15.152s 16.044s 0.892s 2 1.41x
🐘 Postgres Nitro 20.304s (~) 21.059s (~) 0.755s 2 1.90x
🐘 Postgres Express 20.395s (~) 21.057s (~) 0.662s 2 1.90x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 17.712s (-3.6%) 18.512s (-6.4% 🟢) 0.800s 2 1.00x
▲ Vercel Nitro 17.951s (-2.2%) 18.481s (-5.7% 🟢) 0.530s 2 1.01x
▲ Vercel Next.js (Turbopack) 18.189s (-4.0%) 19.514s (-3.6%) 1.325s 2 1.03x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 26.878s 27.048s 0.170s 3 1.00x
💻 Local Next.js (Turbopack) 27.188s 28.048s 0.860s 3 1.01x
💻 Local Express 27.469s (+2.2%) 28.049s (+3.7%) 0.580s 3 1.02x
💻 Local Nitro 27.536s (~) 28.051s (~) 0.515s 3 1.02x
🌐 MongoDB Next.js (Turbopack) 30.520s 31.046s 0.525s 2 1.14x
🐘 Postgres Next.js (Turbopack) 37.746s 38.083s 0.336s 2 1.40x
🐘 Postgres Express 50.167s (~) 50.629s (~) 0.462s 2 1.87x
🐘 Postgres Nitro 50.321s (~) 51.134s (~) 0.813s 2 1.87x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 43.294s (-3.4%) 43.794s (-4.9%) 0.500s 2 1.00x
▲ Vercel Nitro 44.376s (+0.8%) 45.648s (~) 1.273s 2 1.02x
▲ Vercel Next.js (Turbopack) 45.399s (~) 46.761s (+1.2%) 1.362s 2 1.05x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 54.221s 55.098s 0.877s 2 1.00x
💻 Local Next.js (Turbopack) 56.653s 57.097s 0.445s 2 1.04x
💻 Local Express 57.297s (+2.3%) 58.100s (+3.6%) 0.803s 2 1.06x
💻 Local Nitro 57.531s (~) 58.107s (~) 0.576s 2 1.06x
🌐 MongoDB Next.js (Turbopack) 60.987s 61.060s 0.073s 2 1.12x
🐘 Postgres Next.js (Turbopack) 74.263s 74.666s 0.403s 2 1.37x
🐘 Postgres Nitro 100.154s (~) 100.233s (-1.0%) 0.079s 1 1.85x
🐘 Postgres Express 100.297s (~) 101.242s (+1.0%) 0.945s 1 1.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 98.388s (+9.5% 🔺) 99.196s (+8.9% 🔺) 0.808s 1 1.00x
▲ Vercel Nitro 100.391s (+11.4% 🔺) 101.539s (+10.7% 🔺) 1.148s 1 1.02x
▲ Vercel Next.js (Turbopack) 103.333s (+11.8% 🔺) 104.518s (+12.0% 🔺) 1.185s 1 1.05x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.240s 2.006s 0.766s 15 1.00x
💻 Local Next.js (Turbopack) 1.399s 2.005s 0.607s 15 1.13x
💻 Local Express 1.404s (+2.4%) 2.006s (~) 0.602s 15 1.13x
💻 Local Nitro 1.420s (+0.5%) 2.006s (~) 0.586s 15 1.14x
🐘 Postgres Next.js (Turbopack) 1.667s 2.011s 0.344s 15 1.34x
🐘 Postgres Nitro 2.129s (-11.8% 🟢) 3.014s (~) 0.885s 10 1.72x
🌐 MongoDB Next.js (Turbopack) 2.136s 3.008s 0.872s 10 1.72x
🐘 Postgres Express 2.320s (+3.9%) 3.014s (~) 0.694s 10 1.87x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 5.537s (+115.3% 🔺) 6.298s (+84.0% 🔺) 0.762s 5 1.00x
▲ Vercel Express 7.255s (+182.6% 🔺) 8.329s (+141.0% 🔺) 1.074s 4 1.31x
▲ Vercel Next.js (Turbopack) 11.340s (+268.7% 🔺) 12.371s (+197.7% 🔺) 1.030s 3 2.05x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.458s 3.007s 0.549s 10 1.00x
🌐 Redis Next.js (Turbopack) 2.515s 3.008s 0.493s 10 1.02x
💻 Local Express 2.604s (+11.0% 🔺) 3.007s (~) 0.403s 10 1.06x
💻 Local Nitro 2.682s (+2.5%) 3.007s (~) 0.325s 10 1.09x
🌐 MongoDB Next.js (Turbopack) 4.750s 5.177s 0.427s 6 1.93x
🐘 Postgres Nitro 8.368s (-12.4% 🟢) 8.786s (-12.5% 🟢) 0.418s 4 3.40x
🐘 Postgres Express 8.518s (-3.0%) 9.029s (-2.8%) 0.511s 4 3.47x
🐘 Postgres Next.js (Turbopack) 10.819s 11.365s 0.546s 3 4.40x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 8.387s (+205.7% 🔺) 9.471s (+160.6% 🔺) 1.083s 4 1.00x
▲ Vercel Nitro 10.415s (+157.9% 🔺) 11.292s (+111.0% 🔺) 0.877s 3 1.24x
▲ Vercel Express 11.236s (+284.8% 🔺) 12.359s (+216.2% 🔺) 1.123s 3 1.34x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.070s 4.724s 0.654s 7 1.00x
💻 Local Next.js (Turbopack) 6.934s 7.515s 0.581s 4 1.70x
💻 Local Nitro 7.692s (+3.4%) 8.023s (~) 0.331s 4 1.89x
💻 Local Express 7.701s (+18.9% 🔺) 8.020s (+14.3% 🔺) 0.319s 4 1.89x
🌐 MongoDB Next.js (Turbopack) 9.747s 10.351s 0.605s 3 2.39x
🐘 Postgres Nitro 45.870s (~) 46.111s (~) 0.241s 1 11.27x
🐘 Postgres Express 48.503s (+3.4%) 49.110s (+4.2%) 0.607s 1 11.92x
🐘 Postgres Next.js (Turbopack) 53.990s 54.123s 0.133s 1 13.26x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 13.436s (+229.8% 🔺) 14.341s (+178.2% 🔺) 0.906s 3 1.00x
▲ Vercel Express 13.813s (+278.9% 🔺) 15.064s (+223.2% 🔺) 1.252s 2 1.03x
▲ Vercel Next.js (Turbopack) 17.209s (+311.0% 🔺) 18.764s (+259.4% 🔺) 1.554s 2 1.28x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.232s 2.006s 0.774s 15 1.00x
💻 Local Next.js (Turbopack) 1.426s 2.005s 0.578s 15 1.16x
💻 Local Express 1.427s (+4.1%) 2.005s (~) 0.578s 15 1.16x
💻 Local Nitro 1.455s (+3.5%) 2.005s (~) 0.550s 15 1.18x
🐘 Postgres Next.js (Turbopack) 1.995s 2.513s 0.519s 12 1.62x
🐘 Postgres Express 2.072s (-4.9%) 2.741s (~) 0.669s 11 1.68x
🌐 MongoDB Next.js (Turbopack) 2.162s 3.008s 0.845s 10 1.76x
🐘 Postgres Nitro 2.296s (+26.9% 🔺) 2.741s (+14.1% 🔺) 0.445s 11 1.86x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 5.344s (+83.7% 🔺) 7.011s (+83.7% 🔺) 1.667s 5 1.00x
▲ Vercel Nitro 7.650s (+219.5% 🔺) 8.563s (+153.8% 🔺) 0.914s 5 1.43x
▲ Vercel Next.js (Turbopack) 8.076s (+229.8% 🔺) 9.242s (+164.9% 🔺) 1.166s 4 1.51x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.494s 3.008s 0.513s 10 1.00x
💻 Local Next.js (Turbopack) 2.626s 3.008s 0.382s 10 1.05x
💻 Local Express 2.687s (+8.2% 🔺) 3.008s (~) 0.321s 10 1.08x
💻 Local Nitro 2.779s (+3.1%) 3.009s (~) 0.230s 10 1.11x
🌐 MongoDB Next.js (Turbopack) 4.665s 5.175s 0.511s 6 1.87x
🐘 Postgres Nitro 11.132s (-2.1%) 11.701s (-2.8%) 0.569s 3 4.46x
🐘 Postgres Next.js (Turbopack) 12.691s 13.369s 0.678s 3 5.09x
🐘 Postgres Express 12.758s (+3.9%) 13.036s (+5.4% 🔺) 0.278s 3 5.11x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 5.393s (+86.8% 🔺) 6.280s (+63.6% 🔺) 0.888s 6 1.00x
▲ Vercel Nitro 9.447s (+287.2% 🔺) 10.153s (+208.7% 🔺) 0.706s 3 1.75x
▲ Vercel Express 10.498s (+250.4% 🔺) 11.188s (+194.8% 🔺) 0.690s 3 1.95x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.086s 4.725s 0.639s 7 1.00x
💻 Local Next.js (Turbopack) 7.295s 7.767s 0.472s 4 1.79x
💻 Local Express 7.965s (+9.8% 🔺) 8.518s (+6.3% 🔺) 0.553s 4 1.95x
💻 Local Nitro 8.389s (+5.6% 🔺) 9.019s (+9.1% 🔺) 0.630s 4 2.05x
🌐 MongoDB Next.js (Turbopack) 9.858s 10.346s 0.488s 3 2.41x
🐘 Postgres Nitro 50.033s (+1.9%) 50.128s (~) 0.095s 1 12.24x
🐘 Postgres Next.js (Turbopack) 50.671s 51.104s 0.433s 1 12.40x
🐘 Postgres Express 53.449s (+8.5% 🔺) 54.117s (+8.0% 🔺) 0.668s 1 13.08x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 4.250s (-41.1% 🟢) 5.441s (-36.5% 🟢) 1.191s 6 1.00x
▲ Vercel Nitro 11.497s (+59.8% 🔺) 12.463s (+45.8% 🔺) 0.966s 3 2.71x
▲ Vercel Express 12.772s (+192.0% 🔺) 13.921s (+154.1% 🔺) 1.149s 3 3.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.144s 1.001s 0.011s 1.016s 0.872s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.147s 1.000s 0.001s 1.007s 0.860s 10 1.02x
💻 Local Express 0.171s (+48.9% 🔺) 1.002s (~) 0.012s (+9.3% 🔺) 1.017s (~) 0.845s 10 1.19x
💻 Local Nitro 0.180s (+4.0%) 1.002s (~) 0.012s (+9.3% 🔺) 1.017s (~) 0.837s 10 1.25x
🌐 MongoDB Next.js (Turbopack) 0.515s 0.929s 0.001s 1.008s 0.493s 10 3.58x
🐘 Postgres Next.js (Turbopack) 0.951s 1.040s 0.001s 1.311s 0.361s 10 6.61x
🐘 Postgres Nitro 2.249s (-8.2% 🟢) 2.795s (+7.9% 🔺) 0.002s (+15.4% 🔺) 3.016s (~) 0.766s 10 15.64x
🐘 Postgres Express 2.397s (+4.6%) 2.650s (-3.7%) 0.001s (-14.3% 🟢) 3.015s (~) 0.618s 10 16.67x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.052s (-3.9%) 2.500s (-5.2% 🟢) 0.242s (-4.8%) 3.270s (-5.0% 🟢) 1.219s 10 1.00x
▲ Vercel Express 2.163s (-0.6%) 2.539s (-9.1% 🟢) 0.191s (-31.0% 🟢) 3.459s (-6.0% 🟢) 1.296s 10 1.05x
▲ Vercel Next.js (Turbopack) 7.939s (+236.0% 🔺) 7.465s (+180.3% 🔺) 0.202s (-25.1% 🟢) 9.445s (+162.9% 🔺) 1.506s 10 3.87x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 11/12
🐘 Postgres Next.js (Turbopack) 7/12
▲ Vercel Express 5/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 12/12
Next.js (Turbopack) 🌐 Redis 8/12
Nitro 💻 Local 12/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

@TooTallNate TooTallNate marked this pull request as ready for review February 13, 2026 02:32
Copilot AI review requested due to automatic review settings February 13, 2026 02:32
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 13, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 501 0 38 539
✅ 💻 Local Development 520 0 68 588
❌ 📦 Local Production 475 45 68 588
❌ 🐘 Local Postgres 475 45 68 588
✅ 🪟 Windows 46 0 3 49
❌ 🌍 Community Worlds 105 42 9 156
✅ 📋 Other 126 0 21 147
Total 2248 132 275 2655

❌ Failed Tests

📦 Local Production (45 failed)

nextjs-turbopack-canary (45 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • webhook route with invalid token
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling retry behavior workflow completes despite transient 5xx on step_completed
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check endpoint (HTTP) - workflow and step endpoints respond to __health query parameter
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
🐘 Local Postgres (45 failed)

nextjs-turbopack-canary (45 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • webhook route with invalid token
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling retry behavior workflow completes despite transient 5xx on step_completed
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check endpoint (HTTP) - workflow and step endpoints respond to __health query parameter
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
🌍 Community Worlds (42 failed)

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling retry behavior workflow completes despite transient 5xx on step_completed
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 45 0 4
✅ example 45 0 4
✅ express 45 0 4
✅ fastify 45 0 4
✅ hono 45 0 4
✅ nextjs-turbopack 48 0 1
✅ nextjs-webpack 48 0 1
✅ nitro 45 0 4
✅ nuxt 45 0 4
✅ sveltekit 45 0 4
✅ vite 45 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 42 0 7
✅ express-stable 42 0 7
✅ fastify-stable 42 0 7
✅ hono-stable 42 0 7
✅ nextjs-turbopack-canary 46 0 3
✅ nextjs-turbopack-stable 46 0 3
✅ nextjs-webpack-canary 46 0 3
✅ nextjs-webpack-stable 46 0 3
✅ nitro-stable 42 0 7
✅ nuxt-stable 42 0 7
✅ sveltekit-stable 42 0 7
✅ vite-stable 42 0 7
❌ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 42 0 7
✅ express-stable 42 0 7
✅ fastify-stable 42 0 7
✅ hono-stable 42 0 7
❌ nextjs-turbopack-canary 1 45 3
✅ nextjs-turbopack-stable 46 0 3
✅ nextjs-webpack-canary 46 0 3
✅ nextjs-webpack-stable 46 0 3
✅ nitro-stable 42 0 7
✅ nuxt-stable 42 0 7
✅ sveltekit-stable 42 0 7
✅ vite-stable 42 0 7
❌ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 42 0 7
✅ express-stable 42 0 7
✅ fastify-stable 42 0 7
✅ hono-stable 42 0 7
❌ nextjs-turbopack-canary 1 45 3
✅ nextjs-turbopack-stable 46 0 3
✅ nextjs-webpack-canary 46 0 3
✅ nextjs-webpack-stable 46 0 3
✅ nitro-stable 42 0 7
✅ nuxt-stable 42 0 7
✅ sveltekit-stable 42 0 7
✅ vite-stable 42 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 46 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
✅ mongodb 46 0 3
✅ redis-dev 3 0 0
✅ redis 46 0 3
✅ turso-dev 3 0 0
❌ turso 4 42 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 42 0 7
✅ e2e-local-postgres-nest-stable 42 0 7
✅ e2e-local-prod-nest-stable 42 0 7

📋 View full workflow run


Some E2E test jobs failed:

  • Vercel Prod: success
  • Local Dev: success
  • Local Prod: failure
  • Local Postgres: failure
  • Windows: success

Check the workflow run for details.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Feb 13, 2026 9:46pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Feb 13, 2026 9:46pm
example-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-astro-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-express-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-fastify-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-hono-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-nitro-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-nuxt-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workbench-vite-workflow Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 9:46pm
workflow-nest Ready Ready Preview, Comment Feb 13, 2026 9:46pm
workflow-swc-playground Ready Ready Preview, Comment Feb 13, 2026 9:46pm

Copy link
Copy Markdown
Member Author

TooTallNate commented Feb 13, 2026

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR consolidates data inspection functionality by extracting a reusable <DataInspector> component and improving class instance rendering. The changes replace direct ObjectInspector usage across multiple components with a unified component that provides consistent theming, custom type handling for StreamRef and ClassInstanceRef, and improved class name display in the inspector.

Changes:

  • Created a new <DataInspector> component with custom node rendering and theme support
  • Updated class instance hydration to use dynamically-named constructors for proper display
  • Replaced all ObjectInspector usage across 5 components with the new DataInspector

Reviewed changes

Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
packages/web-shared/src/lib/hydration.ts Modified Instance reviver to create objects with dynamically-named constructors instead of ClassInstanceRef objects
packages/web-shared/src/components/ui/data-inspector.tsx New reusable component consolidating ObjectInspector with custom rendering and theming
packages/web-shared/src/components/stream-viewer.tsx Replaced ObjectInspector with DataInspector
packages/web-shared/src/components/sidebar/events-list.tsx Replaced ObjectInspector with DataInspector
packages/web-shared/src/components/sidebar/conversation-view.tsx Replaced JSON.stringify with DataInspector for tool inputs/outputs
packages/web-shared/src/components/sidebar/attribute-panel.tsx Removed local StreamRef/ClassInstanceRef handling and adopted DataInspector
packages/web-shared/src/components/index.ts Exported DataInspector component
packages/web-shared/src/components/event-list-view.tsx Replaced ObjectInspector with DataInspector
packages/web-shared/package.json Removed unused color-hash dependencies
.changeset/new-oranges-joke.md Added changeset for this patch
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread packages/web-shared/src/lib/hydration.ts
Comment thread packages/web-shared/src/components/ui/data-inspector.tsx
Comment thread packages/web-shared/src/components/sidebar/conversation-view.tsx
…endering

Consolidate all ObjectInspector usage into a single DataInspector component
with shared theming, custom nodeRenderer for StreamRef/ClassInstanceRef, and
stream click context. Update all consumers (attribute-panel, events-list,
event-list-view, stream-viewer, conversation-view) to use DataInspector
instead of direct ObjectInspector or JSON.stringify. Fix class instance
hydration to create objects with dynamically-named constructors so
react-inspector shows proper class names via constructor.name.
@TooTallNate TooTallNate force-pushed the 02-12-extract_reusable_datainspector_component_and_fix_class_instance_rendering branch from b1a1c05 to 5493314 Compare February 13, 2026 21:43
Copy link
Copy Markdown
Contributor

@karthikscale3 karthikscale3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested it locally and everything looks good.

@TooTallNate TooTallNate merged commit dbf8434 into main Feb 13, 2026
163 of 170 checks passed
@TooTallNate TooTallNate deleted the 02-12-extract_reusable_datainspector_component_and_fix_class_instance_rendering branch February 13, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants