◉CLAUDE LABJP
●VERSION — v2.1.227 landed on August 10 with no new features, just fixes around plan detection and CI behavior●AUTO — Two days remain until August 14, when auto mode becomes the default in Claude Code for Pro, Max, and Team●CI — Bash commands no longer fail across the board under claude-code-action with allowed_non_write_users on GitHub-hosted runners●BILLING — Sessions started with an expired token could misread your plan and nudge Max users toward usage credits; that is now fixed●SUNSET — The legacy Workbench and the experimental prompt tool APIs retire on August 17, five days out●PRICE — Sonnet 5 promo pricing at $2/$10 per Mtok runs through August 31, moving to $3/$15 on September 1●VERSION — v2.1.227 landed on August 10 with no new features, just fixes around plan detection and CI behavior●AUTO — Two days remain until August 14, when auto mode becomes the default in Claude Code for Pro, Max, and Team●CI — Bash commands no longer fail across the board under claude-code-action with allowed_non_write_users on GitHub-hosted runners●BILLING — Sessions started with an expired token could misread your plan and nudge Max users toward usage credits; that is now fixed●SUNSET — The legacy Workbench and the experimental prompt tool APIs retire on August 17, five days out●PRICE — Sonnet 5 promo pricing at $2/$10 per Mtok runs through August 31, moving to $3/$15 on September 1
TAG

error boundary

1 articles
← Back to all tags
Related:
Next.js1Cloudflare Workers1ChunkLoadError1troubleshooting1
⟐ Claude Code/2026-06-17Intermediate

It Says '500' in the Browser but curl Returns 200 — When a Next.js Error Boundary Misreads a ChunkLoadError

A production Next.js article page shows '500 Internal Server Error' in the browser, yet curl returns 200. The culprit was not the server but a ChunkLoadError surfacing through error.tsx. Here is the diagnosis and a fix with built-in auto-reload.