Matt Isenhower aa71bf2eda
Some checks failed
Build frontend / build (24.x) (push) Has been cancelled
Lint / lint (push) Has been cancelled
Tests / test (24.x) (push) Has been cancelled
Hold a lane run while an earlier one may still be going; log data changes
Cloudflare replaced the fast lane's Durable Object during the 00:00 UTC run.
The alarm restarted on a new instance while the old one carried on posting,
and the old run's results were lost because it could no longer write to its
own storage. Like the old cron, a run now takes a lock in the private R2
bucket (which a replaced instance can still write), refreshes it every 10
seconds and deletes it at the end; a run that finds a fresh lock waits and
checks again in 15 seconds. A scheduled run that never saved its results is
recorded as cut off.

Each updater now reports whether its published file changed, in its log
line and in the run's results, to see when fresh data really arrives at the
top of the hour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 16:23:40 -08:00
…
…
…

Splatoon3.ink

Splatoon3.ink features Splatoon 3 map rotations, Salmon Run schedules, SplatNet gear, and more.

Acknowledgements

Many thanks to the following projects for making Nintendo Switch Online automated logins possible:

Project Setup

npm install

Compile and Hot-Reload for Development

npm run dev

Compile and Minify for Production

npm run build

Screenshot Generation

Cloudflare screenshots use the Worker's BROWSER binding directly. No Browser Run API token or account ID is needed. The Cloudflare driver receives the binding explicitly:

const driver = new CloudflareScreenshotDriver({ browser: env.BROWSER, env });

SITE_URL selects the frontend to render. Screenshots wait for the page's explicit readiness marker after its data, fonts, images, and layout settle. Like Splatoon 2, Browser Run uses 10-second navigation, readiness, and action timeouts, with up to three retries after the first attempt (0.5/1/2-second backoff). Timeouts, network errors, and HTTP 5xx are retried; authentication, rate-limit, and other validation errors fail immediately. Exhausted retries surface the error to the caller.

For a capture-only test against dev.splatoon3.ink:

npm run screenshot:cloudflare

Then save a PNG from another terminal:

curl --fail-with-body --get 'http://127.0.0.1:8789/' \
  --data-urlencode 'route=schedules' \
  --output /tmp/splatoon3-schedules.png

The route parameter is the screenshot page's hash, including any query parameters (for example, schedules?time=1789531200000). It defaults to schedules. This local preview Worker captures images only; it does not update data, write posting checkpoints, or send social posts. It is for local testing, not deployment.

Wrangler runs the endpoint on loopback with a remote Browser binding. Sign in with npx wrangler login if needed. The browser must be able to reach the rendering site, and captures use the account's Browser Run allowance. See Cloudflare Quick Actions.

To capture an unpublished frontend, build and serve it, expose it through a tunnel, and override the preview Worker's site URL:

npm run build
npm run preview
# In another terminal:
npx wrangler tunnel quick-start http://localhost:5050
# Use the printed tunnel URL:
npm run screenshot:cloudflare -- --var SITE_URL:https://example.trycloudflare.com

Local screenshots use puppeteer-core with an installed Chrome or Chromium (found automatically on macOS and common Linux paths; otherwise set CHROME_PATH). They always capture the built site in dist/ through a temporary loopback server, regardless of SITE_URL.

npm run build
npm run screenshot -- --route schedules --output /tmp/splatoon3-local.png

The --route argument accepts a screenshot hash including its query parameters, just like the Cloudflare preview's route parameter. Built-site captures need the usual data and assets in dist/, or a build configured with VITE_DATA_FROM.

For Node social commands, set SCREENSHOT_PROVIDER=local. The binding-based cloudflare provider runs through Workers tooling. Both providers wait for the page-ready marker; the local driver also fails fast when the page reports a screenshot error (for example, missing translations).

Lint with ESLint

npm run lint
Description
🦑 Splatoon 3 map rotations, Salmon Run schedules, SplatNet gear, and more
Readme 29 MiB
Languages
Vue 56.5%
JavaScript 42.9%
CSS 0.4%
HTML 0.2%