Skip to content

fix(chronos): launch the dev server from a script so Windows can star… - #455

Closed
Dasa122 wants to merge 1 commit into
mainfrom
fix/windows-dev-max-http-header-size
Closed

Dasa122 wants to merge 1 commit into
mainfrom
fix/windows-dev-max-http-header-size

Conversation

@Dasa122

@Dasa122 Dasa122 commented Nov 12, 2026

Copy link
Copy Markdown
Member

Summary

bun dev failed on Windows before Chronos could start: the dev command asked the shell for an optional setting, and the Windows shell doesn't understand that syntax, so the backend exited immediately with an "invalid value" error. The dev command now works out that value itself, so it behaves the same on Windows, Linux and macOS.

Changes

  • Chronos starts through a small launcher script instead of a one-line command, so the request-header limit is no longer computed by the shell.
  • CHRONOS_MAX_HTTP_HEADER_SIZE still overrides it; the default stays 65536.
  • Stopping the dev server still stops the backend, so the port isn't left busy.
  • Doc paragraph updated to match.

Verification

  • bun run lint
  • bun run typecheck
  • bun run build — if bundler config, routers, or server entrypoints changed

…t it

Windows runs package.json scripts in Bun Shell, which expands `$VAR` but has
no `${VAR:-default}` syntax, so the literal placeholder reached bun and `bun
dev` died with "Invalid value for --max-http-header-size". Bun accepts the cap
only as a launch flag, so the launch moves into scripts/dev.ts, which reads
CHRONOS_MAX_HTTP_HEADER_SIZE (default 65536) and forwards SIGINT/SIGTERM to
the server so a killed dev task cannot leave an orphan on port 3001.
@Dasa122 Dasa122 closed this Nov 12, 2026
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Filc Issue Tracker Nov 12, 2026
@Dasa122
Dasa122 deleted the fix/windows-dev-max-http-header-size branch November 12, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant