Skip to content

👷 don't run @effectionx/watch in CI website build#1163

Merged
cowboyd merged 1 commit intov4from
ci/www-no-watch
May 4, 2026
Merged

👷 don't run @effectionx/watch in CI website build#1163
cowboyd merged 1 commit intov4from
ci/www-no-watch

Conversation

@cowboyd
Copy link
Copy Markdown
Member

@cowboyd cowboyd commented May 4, 2026

Motivation

The scheduled www workflow has been failing intermittently — a different URL returns 500 each time (/guides/v3/events, /docs/collections, /x/signals, /docs/tutorial), and the failed runs all bail in ~40s while successful ones take 2m+.

Theory: deno task dev wraps the server in @effectionx/watch. While Staticalize crawls pages, it writes output into www/built/. The watcher (running from www/) sees those writes, restarts the server, and in-flight requests get 500. Staticalize aborts on the first non-2xx.

(Locally the watcher should pick up .gitignore excludes including built/, so this could be a bug in @effectionx/watch, but either way, there's no reason to watch in CI.)

Approach

Replace deno task dev with deno run -A main.tsx in .github/workflows/www.yaml. No watcher in CI = no mid-crawl restarts.

The www workflow was running `deno task dev`, which wraps the server in
@effectionx/watch. That watcher restarts the server when files change in
the working directory — including `www/built/`, where Staticalize writes
crawled pages. A restart mid-crawl returned 500 to in-flight requests,
causing intermittent failures on a different URL each run.

Run the server directly in CI; no watcher needed.
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 4, 2026

Open in StackBlitz

npm i https://pkg.pr.new/effection@1163

commit: 8ecf6eb

@cowboyd cowboyd merged commit 667364a into v4 May 4, 2026
17 checks passed
@cowboyd cowboyd deleted the ci/www-no-watch branch May 4, 2026 18:58
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.

2 participants