Skip to content

Retheme <DataInspector> to match Node.js util.inspect() colors#1033

Merged
TooTallNate merged 1 commit into
mainfrom
02-12-retheme_datainspector_to_match_node.js_util.inspect_colors
Feb 13, 2026
Merged

Retheme <DataInspector> to match Node.js util.inspect() colors#1033
TooTallNate merged 1 commit into
mainfrom
02-12-retheme_datainspector_to_match_node.js_util.inspect_colors

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

Replaces the Chrome DevTools color scheme with one inspired by
Node.js util.inspect() ANSI stylizing: green strings, yellow
numbers/booleans, grey undefined, magenta dates, cyan functions,
and neutral property names. Adds an extended theme context to
color Date instances (react-inspector has no built-in theme key
for dates). Removes color-hash dependency which is no longer used.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 13, 2026

🦋 Changeset detected

Latest commit: b0df9df

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

🧪 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 104 43 9 156
✅ 📋 Other 126 0 21 147
Total 2247 133 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 (43 failed)

mongodb (1 failed):

  • webhookWorkflow

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 45 1 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, Open in v0 Feb 13, 2026 10:23pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
example-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-astro-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-express-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-fastify-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-hono-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-nitro-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-nuxt-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-sveltekit-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workbench-vite-workflow Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workflow-nest Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm
workflow-swc-playground Ready Ready Preview, Comment, Open in v0 Feb 13, 2026 10:23pm

Copy link
Copy Markdown
Member Author

TooTallNate commented Feb 13, 2026

@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
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 rethemes the <DataInspector> component to align its color scheme with Node.js util.inspect() ANSI styling, replacing the previous Chrome DevTools-inspired colors. It also removes the unused color-hash dependency.

Changes:

  • Redesigned color themes (light and dark) to match Node.js conventions (green strings, yellow numbers/booleans, grey undefined, magenta dates, cyan functions, neutral property names)
  • Added extended theme context to support Date instance coloring, which react-inspector doesn't natively support
  • Refactored theme structure to separate shared structural values from theme-specific colors

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
packages/web-shared/src/components/ui/inspector-theme.ts Implements new Node.js-inspired color schemes for light and dark themes, adds extended theme interface for Date colors
packages/web-shared/src/components/ui/data-inspector.tsx Integrates extended theme context and adds custom Date rendering with magenta color styling
.changeset/legal-ads-shave.md Documents the theme change in the changeset

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

Comment thread packages/web-shared/src/components/ui/data-inspector.tsx
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.

looks good as most changes are only applying new styles and colors.

Base automatically changed from 02-12-extract_reusable_datainspector_component_and_fix_class_instance_rendering to main February 13, 2026 22:20
Replaces the Chrome DevTools color scheme with one inspired by
Node.js util.inspect() ANSI stylizing: green strings, yellow
numbers/booleans, grey undefined, magenta dates, cyan functions,
and neutral property names. Adds an extended theme context to
color Date instances (react-inspector has no built-in theme key
for dates). Removes color-hash dependency which is no longer used.
@TooTallNate TooTallNate force-pushed the 02-12-retheme_datainspector_to_match_node.js_util.inspect_colors branch from bc74e97 to b0df9df Compare February 13, 2026 22:20
@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.033s (+3.1%) 1.005s (~) 0.972s 10 1.00x
💻 Local Nitro 0.037s (+12.2% 🔺) 1.006s (~) 0.969s 10 1.11x
💻 Local Next.js (Turbopack) 0.043s 1.005s 0.962s 10 1.28x
🌐 Redis Next.js (Turbopack) 0.050s (+35.2% 🔺) 1.005s (~) 0.955s 10 1.50x
🐘 Postgres Nitro 0.098s (-55.9% 🟢) 1.010s (-0.6%) 0.912s 10 2.95x
🌐 MongoDB Next.js (Turbopack) 0.098s (+1.7%) 1.008s (~) 0.909s 10 2.96x
🐘 Postgres Express 0.102s (-48.0% 🟢) 1.013s (~) 0.911s 10 3.08x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.607s (+4.3%) 1.738s (-15.4% 🟢) 1.130s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.609s (-5.2% 🟢) 1.704s (-9.2% 🟢) 1.095s 10 1.00x
▲ Vercel Express 0.643s (~) 2.003s (-4.3%) 1.359s 10 1.06x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.104s 2.006s 0.902s 10 1.00x
💻 Local Express 1.107s (~) 2.005s (~) 0.898s 10 1.00x
🌐 Redis Next.js (Turbopack) 1.109s (+2.1%) 2.007s (~) 0.898s 10 1.00x
💻 Local Nitro 1.119s (+1.1%) 2.005s (~) 0.886s 10 1.01x
🌐 MongoDB Next.js (Turbopack) 1.296s (-1.3%) 2.008s (~) 0.712s 10 1.17x
🐘 Postgres Express 2.474s (+42.7% 🔺) 3.013s (+30.3% 🔺) 0.539s 10 2.24x
🐘 Postgres Nitro 2.475s (+1.2%) 3.013s (~) 0.538s 10 2.24x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.280s (-11.1% 🟢) 3.048s (-11.7% 🟢) 0.768s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.360s (+1.7%) 3.000s (-3.9%) 0.640s 10 1.04x
▲ Vercel Express 2.624s (+6.3% 🔺) 3.495s (+6.0% 🔺) 0.871s 10 1.15x

🔍 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.738s 11.023s 0.286s 3 1.00x
🌐 Redis Next.js (Turbopack) 10.742s (+1.4%) 11.025s (~) 0.283s 3 1.00x
💻 Local Express 10.857s (~) 11.023s (~) 0.166s 3 1.01x
💻 Local Nitro 10.913s (+0.7%) 11.024s (~) 0.110s 3 1.02x
🌐 MongoDB Next.js (Turbopack) 12.301s (+0.7%) 13.024s (~) 0.723s 3 1.15x
🐘 Postgres Nitro 16.080s (-20.8% 🟢) 16.547s (-21.4% 🟢) 0.467s 2 1.50x
🐘 Postgres Express 20.351s (+31.3% 🔺) 21.056s (+31.3% 🔺) 0.706s 2 1.90x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 17.524s (-5.3% 🟢) 18.663s (-3.8%) 1.139s 2 1.00x
▲ Vercel Nitro 18.020s (+0.9%) 18.758s (-1.5%) 0.739s 2 1.03x
▲ Vercel Express 18.111s (~) 19.183s (+1.2%) 1.072s 2 1.03x

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

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 26.974s (+1.4%) 27.052s (~) 0.078s 3 1.00x
💻 Local Next.js (Turbopack) 27.225s 28.053s 0.828s 3 1.01x
💻 Local Express 27.514s (~) 28.051s (~) 0.537s 3 1.02x
💻 Local Nitro 27.712s (+0.6%) 28.054s (~) 0.342s 3 1.03x
🌐 MongoDB Next.js (Turbopack) 30.595s (~) 31.045s (~) 0.450s 2 1.13x
🐘 Postgres Nitro 39.398s (-21.7% 🟢) 40.102s (-21.6% 🟢) 0.704s 2 1.46x
🐘 Postgres Express 50.149s (+33.4% 🔺) 50.626s (+32.9% 🔺) 0.477s 2 1.86x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 44.117s (-6.9% 🟢) 45.224s (-7.3% 🟢) 1.106s 2 1.00x
▲ Vercel Next.js (Turbopack) 44.224s (-12.6% 🟢) 45.044s (-13.1% 🟢) 0.821s 2 1.00x
▲ Vercel Express 44.525s (-12.9% 🟢) 45.887s (-14.0% 🟢) 1.362s 2 1.01x

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

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 54.404s (+1.3%) 55.100s (+1.8%) 0.697s 2 1.00x
💻 Local Next.js (Turbopack) 56.844s 57.105s 0.261s 2 1.04x
💻 Local Express 57.347s (~) 58.102s (~) 0.755s 2 1.05x
💻 Local Nitro 57.857s (+0.6%) 58.109s (~) 0.252s 2 1.06x
🌐 MongoDB Next.js (Turbopack) 60.998s (~) 61.074s (-0.8%) 0.077s 2 1.12x
🐘 Postgres Nitro 75.570s (-24.6% 🟢) 76.179s (-24.0% 🟢) 0.609s 2 1.39x
🐘 Postgres Express 100.363s (+36.6% 🔺) 101.234s (+37.4% 🔺) 0.871s 1 1.84x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 87.852s (-5.3% 🟢) 89.127s (-4.9%) 1.275s 2 1.00x
▲ Vercel Express 88.648s (-3.3%) 89.819s (-3.4%) 1.171s 2 1.01x
▲ Vercel Next.js (Turbopack) 88.874s (-3.8%) 90.085s (-3.6%) 1.211s 2 1.01x

🔍 Observability: Nitro | Express | 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.258s (+5.4% 🔺) 2.007s (~) 0.749s 15 1.00x
💻 Local Next.js (Turbopack) 1.408s 2.006s 0.598s 15 1.12x
💻 Local Express 1.412s (~) 2.005s (~) 0.593s 15 1.12x
💻 Local Nitro 1.435s (-1.0%) 2.006s (~) 0.571s 15 1.14x
🌐 MongoDB Next.js (Turbopack) 2.190s (+2.2%) 3.008s (~) 0.818s 10 1.74x
🐘 Postgres Nitro 2.309s (+3.7%) 2.681s (-11.0% 🟢) 0.372s 12 1.84x
🐘 Postgres Express 2.410s (+24.6% 🔺) 3.013s (+19.9% 🔺) 0.603s 10 1.92x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.430s (-14.5% 🟢) 3.086s (-13.3% 🟢) 0.656s 10 1.00x
▲ Vercel Nitro 2.500s (-39.1% 🟢) 3.244s (-39.1% 🟢) 0.743s 10 1.03x
▲ Vercel Express 3.189s (+25.1% 🔺) 4.583s (+24.7% 🔺) 1.394s 7 1.31x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.487s 3.007s 0.520s 10 1.00x
🌐 Redis Next.js (Turbopack) 2.546s (+6.1% 🔺) 3.008s (~) 0.462s 10 1.02x
💻 Local Express 2.615s (-1.0%) 3.007s (~) 0.392s 10 1.05x
💻 Local Nitro 2.679s (~) 3.007s (~) 0.329s 10 1.08x
🌐 MongoDB Next.js (Turbopack) 4.717s (-2.1%) 5.178s (-3.1%) 0.461s 6 1.90x
🐘 Postgres Express 8.232s (-27.5% 🟢) 8.530s (-29.1% 🟢) 0.298s 4 3.31x
🐘 Postgres Nitro 10.454s (+20.5% 🔺) 10.699s (+18.3% 🔺) 0.245s 3 4.20x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 4.250s (+6.9% 🔺) 5.223s (+6.0% 🔺) 0.973s 6 1.00x
▲ Vercel Express 6.604s (+105.4% 🔺) 7.799s (+78.1% 🔺) 1.195s 5 1.55x
▲ Vercel Nitro 7.633s (+74.7% 🔺) 8.513s (+56.2% 🔺) 0.880s 4 1.80x

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

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.155s (+6.5% 🔺) 4.582s (+6.7% 🔺) 0.427s 7 1.00x
💻 Local Express 7.515s (~) 8.018s (~) 0.503s 4 1.81x
💻 Local Nitro 7.676s (-4.9%) 8.019s (-8.6% 🟢) 0.342s 4 1.85x
💻 Local Next.js (Turbopack) 7.885s 8.516s 0.631s 4 1.90x
🌐 MongoDB Next.js (Turbopack) 9.758s (-1.7%) 10.352s (~) 0.594s 3 2.35x
🐘 Postgres Nitro 45.104s (-6.8% 🟢) 45.127s (-8.2% 🟢) 0.023s 1 10.85x
🐘 Postgres Express 47.507s (-5.2% 🟢) 48.112s (-5.9% 🟢) 0.605s 1 11.43x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 8.949s (-35.7% 🟢) 10.046s (-33.5% 🟢) 1.097s 3 1.00x
▲ Vercel Next.js (Turbopack) 14.449s (+53.4% 🔺) 15.500s (+47.5% 🔺) 1.051s 2 1.61x
▲ Vercel Nitro 15.649s (+18.5% 🔺) 16.452s (+14.2% 🔺) 0.803s 2 1.75x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.253s (+4.0%) 2.006s (~) 0.753s 15 1.00x
💻 Local Express 1.451s (+0.6%) 2.005s (~) 0.554s 15 1.16x
💻 Local Nitro 1.453s (~) 2.005s (~) 0.552s 15 1.16x
💻 Local Next.js (Turbopack) 1.461s 2.005s 0.543s 15 1.17x
🐘 Postgres Express 1.969s (-5.5% 🟢) 2.514s (-6.2% 🟢) 0.545s 12 1.57x
🐘 Postgres Nitro 2.112s (+20.3% 🔺) 3.015s (+45.1% 🔺) 0.902s 10 1.69x
🌐 MongoDB Next.js (Turbopack) 2.154s (+1.1%) 3.008s (~) 0.854s 10 1.72x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.358s (-45.9% 🟢) 3.006s (-45.5% 🟢) 0.647s 10 1.00x
▲ Vercel Express 2.991s (-66.9% 🟢) 3.912s (-63.3% 🟢) 0.921s 8 1.27x
▲ Vercel Next.js (Turbopack) 4.001s (-12.7% 🟢) 4.800s (-11.4% 🟢) 0.799s 7 1.70x

🔍 Observability: Nitro | Express | 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.514s (+6.1% 🔺) 3.008s (~) 0.494s 10 1.00x
💻 Local Next.js (Turbopack) 2.601s 3.007s 0.406s 10 1.03x
💻 Local Express 2.699s (-1.9%) 3.008s (~) 0.309s 10 1.07x
💻 Local Nitro 2.792s (~) 3.009s (~) 0.218s 10 1.11x
🌐 MongoDB Next.js (Turbopack) 4.712s (~) 5.176s (~) 0.464s 6 1.87x
🐘 Postgres Nitro 11.753s (+18.3% 🔺) 12.370s (+19.3% 🔺) 0.617s 3 4.68x
🐘 Postgres Express 12.758s (-7.9% 🟢) 13.369s (-7.0% 🟢) 0.610s 3 5.08x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.492s (-35.2% 🟢) 3.393s (-32.5% 🟢) 0.901s 9 1.00x
▲ Vercel Express 3.408s (-31.2% 🟢) 4.358s (-27.2% 🟢) 0.950s 7 1.37x
▲ Vercel Next.js (Turbopack) 3.546s (+7.7% 🔺) 4.610s (+5.8% 🔺) 1.064s 7 1.42x

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

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.088s (+4.2%) 4.724s (+10.0% 🔺) 0.636s 7 1.00x
💻 Local Next.js (Turbopack) 8.284s 8.519s 0.235s 4 2.03x
💻 Local Express 8.328s (+3.6%) 9.018s (+5.9% 🔺) 0.690s 4 2.04x
💻 Local Nitro 8.425s (+0.8%) 9.021s (~) 0.596s 4 2.06x
🌐 MongoDB Next.js (Turbopack) 9.779s (~) 10.348s (~) 0.570s 3 2.39x
🐘 Postgres Nitro 51.112s (+7.1% 🔺) 52.128s (+8.3% 🔺) 1.016s 1 12.50x
🐘 Postgres Express 53.988s (-2.0%) 54.120s (-1.8%) 0.132s 1 13.21x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 7.954s (+79.6% 🔺) 9.025s (+66.1% 🔺) 1.071s 5 1.00x
▲ Vercel Nitro 14.709s (+165.5% 🔺) 15.524s (+125.6% 🔺) 0.815s 3 1.85x
▲ Vercel Express 17.387s (+172.5% 🔺) 18.719s (+147.1% 🔺) 1.332s 2 2.19x

🔍 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.145s 1.002s 0.011s 1.017s 0.872s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.155s (+34.8% 🔺) 1.000s (~) 0.002s (+45.5% 🔺) 1.007s (~) 0.853s 10 1.06x
💻 Local Express 0.178s (+3.0%) 1.002s (~) 0.011s (-2.7%) 1.016s (~) 0.838s 10 1.23x
💻 Local Nitro 0.189s (+7.8% 🔺) 1.003s (~) 0.011s (+0.9%) 1.018s (~) 0.829s 10 1.30x
🌐 MongoDB Next.js (Turbopack) 0.504s (+2.2%) 0.945s (-1.0%) 0.001s (-12.5% 🟢) 1.009s (~) 0.505s 10 3.46x
🐘 Postgres Nitro 1.385s (-39.9% 🟢) 1.655s (-39.6% 🟢) 0.001s (+16.7% 🔺) 2.012s (-33.3% 🟢) 0.628s 10 9.52x
🐘 Postgres Express 2.179s (+223.8% 🔺) 2.064s (+95.9% 🔺) 0.001s (~) 2.514s (+126.4% 🔺) 0.335s 10 14.99x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 1.973s (-6.6% 🟢) 2.446s (-1.6%) 0.199s (+26.7% 🔺) 3.107s (-3.1%) 1.134s 10 1.00x
▲ Vercel Nitro 2.028s (-28.4% 🟢) 2.456s (-23.9% 🟢) 0.611s (+207.7% 🔺) 3.545s (-17.6% 🟢) 1.517s 10 1.03x
▲ Vercel Express 2.164s (+5.2% 🔺) 2.643s (-10.3% 🟢) 0.197s (+41.0% 🔺) 3.429s (-7.6% 🟢) 1.265s 10 1.10x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 9/12
🐘 Postgres Nitro 9/12
▲ Vercel Nitro 6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 12/12
Next.js (Turbopack) 🌐 Redis 7/12
Nitro 💻 Local 11/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

@graphite-app
Copy link
Copy Markdown

graphite-app Bot commented Feb 13, 2026

Merge activity

  • Feb 13, 10:21 PM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.

@TooTallNate TooTallNate merged commit 260f77e into main Feb 13, 2026
28 of 43 checks passed
@TooTallNate TooTallNate deleted the 02-12-retheme_datainspector_to_match_node.js_util.inspect_colors branch February 13, 2026 22:21
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