HxH Status
hxhstatus.com
A minimal, sourced HUNTER×HUNTER publication and production tracker.
The tracker keeps these milestones separate:
- officially published;
- scheduled for publication;
- delivered to Weekly Shonen Jump;
- background specifications complete;
- character inking complete;
- no confirmed production update.
Pages
Every question the data answers has its own URL, in every published language
(/ for English, /{locale} for the rest):
| Path | Answers |
|---|
/ | Is HUNTER×HUNTER on hiatus right now, and what is confirmed? |
/chapter/{n} | One page per chapter the tracker knows something about: stage, confirmation date, Jump issue, source, prev/next. |
/predictions | Pick Chapter 421’s publication date and compare guesses with other fans. |
/history | The complete publication chart since 1998 and interactive arc comparisons. |
/hiatus | The current break plus every hiatus of ten Jump issues or more since 1998. |
/statistics | Publication pace, presence rate and run lengths. |
/updates and /updates/{postId} | Yoshihiro Togashi's posts, translated, with the Jump submission sheets transcribed. |
/arcs/succession-war | How the Succession War compares with every other arc, by chapters and by years. |
/where-to-read | The official readers, by language. |
/about | What is tracked, from which sources, and how corrections work. |
/api | The public API, documented. |
app/_pages/ holds the body of each page; the route files under app/ and
app/[locale]/ are thin wrappers so English and the six other languages render
from one component. The history and predictions pages keep their interactive components and framework runtime. The other content
pages carry no interactive component, so
scripts/strip-page-scripts.mjs removes the framework runtime from them after
the export: they ship HTML and CSS only.
Run locally
npm install
npm run dev
Open http://localhost:3000.
Update the tracker
Current production data is in app/data/status-data.json. The adjacent
app/data/status.ts module validates it and derives the dashboard values.
Each chapter can include a
status, confirmation date, source URL, Jump issue, note, and a releaseAt
timestamp for its official Japanese digital release (for example
"2026-09-07T00:00:00+09:00").
Everything on the page is derived from that file: the four headline numbers, the
"currently publishing / on hiatus" state, and the latest-update panel. Adding a
chapter or moving one to published is enough — nothing needs to be changed in
the components.
Publication-history data is in app/data/publication-history.json. Add a
Weekly Shonen Jump issue only after its official release. Double-numbered
physical issues count as one issue.
After editing data, update lastUpdated in app/data/status-data.json and run:
npm run share:build
This command first builds the site, then renders the two tracker sections with
the same React components and CSS used by the site, replaces the interactive
actions with hxhstatus.com, and captures them as
out/share/production.png and
out/share/publication-history.png. The same files are kept in
public/share/ so Share and Copy also work during local development. These
PNGs are generated once, committed with the data update, and then served as
static assets cached for five minutes and revalidated; site traffic never launches a browser or regenerates
them. The regular npm run build deliberately reuses the committed PNGs so
Cloudflare does not need Playwright or Chromium system libraries.
Togashi update automation
The separate togashi-events Cloudflare Worker watches Togashi through signed X events and a scheduled fallback
and dispatch a serialized GitHub Action. Gemini is treated only as a
conservative extractor: a production status changes automatically only when
Gemini and deterministic Japanese text rules agree. Dates, Jump issues,
publication state, and publication history remain protected.
Automation is enabled in the checked-in configuration; its secrets and repository
permissions must be configured before deployment. See AUTOMATION.md for the
architecture, safety rules, setup, tests, and the parts that still require an
official source.
Translate the site
English interface text lives in messages/en.json. English, French, Japanese,
Spanish, Brazilian Portuguese, Simplified Chinese, and Arabic are published.
Their routes, selector entries, metadata, service-worker copy, and text
direction all come from lib/locales.json.
See TRANSLATING.md for the contributor workflow and run
npm run translations:check before opening a pull request. A maintainer does
the one-time locale registration; translators then edit only their assigned
messages/{locale}.json values. Publishing a reviewed locale automatically
adds it to language detection, the selector, the sitemap, and hreflang metadata.
Public API
The build publishes versioned, CORS-enabled JSON for the tracker and Togashi's
validated posts. Each new post is translated once during ingestion and stored
by post ID; API reads are static Cloudflare asset requests and never invoke
Gemini or X. Localized endpoints cover all seven published languages.
Bots can get chart 1 directly from GET /share/{locale}/production.png and
chart 2 from GET /share/{locale}/publication-history.png. Both return PNG
bytes. /api/v1/index.json lists these operations and supplies revisioned
image URLs for each language, also described in OpenAPI.
See API.md for endpoints, response examples, translation fallbacks,
and the five-minute polling contract for bots. /status.json remains available
for existing integrations, while new consumers should use /api/v1/status.json.
Embed status badge
Embed an always-up-to-date status badge in your repository README, website, or forum:
[](https://hxhstatus.com)
Available variants
| Variant | URL | Markdown snippet |
|---|
| Status overview | https://hxhstatus.com/badge/status.svg | [](https://hxhstatus.com) |
| Latest published | https://hxhstatus.com/badge/latest.svg | [](https://hxhstatus.com) |
| Confirmed progress | https://hxhstatus.com/badge/progress.svg | [](https://hxhstatus.com) |
| Next chapter | https://hxhstatus.com/badge/next.svg | [](https://hxhstatus.com) |
For localized badges, replace /badge/ with /badge/{locale}/ (ar, en, es, fr, ja, pt, zh).
Deploy
next.config.ts sets output: "export", so npm run build emits the site
to out/. Cloudflare serves matching files directly as static assets; a very
small Worker handles the push API and unmatched HTTP requests. The separate
togashi-events Worker owns scheduled jobs and X webhooks.
No Next.js server or framework adapter is needed.
wrangler.jsonc declares the static assets and public push Worker.
The scheduled event Worker is configured in wrangler.x-activity.jsonc.
Static asset requests bypass Worker execution by default. Keep this file in the
repository so Wrangler does not infer a server-rendered OpenNext deployment.
Cloudflare Workers build settings:
| Setting | Value |
|---|
| Build command | npm run build |
| Deploy command | npx wrangler deploy |
Wrangler is installed locally, so the same CLI version is used on every
machine. These commands cover the usual deployment checks:
npm run cf:dev # build and preview with the Cloudflare runtime
npm run cf:check # build and validate without publishing
npm run cf:deployments # list active production deployments
npm run cf:logs # stream production logs
Run npx wrangler login once before using commands that access the Cloudflare
account.
Any other static host can serve out/; the optional monitoring automation
would need an equivalent scheduler.
Contributing
Contributions are welcome! Whether you are reporting an issue, updating verified chapter data, or contributing translations, please review our CONTRIBUTING.md guide.
For translations specifically, refer to TRANSLATING.md.
Sources
app/data/publication-history.json is derived from the
HUNTER×HUNTER Hiatus Chart,
copyright its contributors and distributed under the MIT License. The 2026
chapter 419 entry and current production-status data were added separately.
This is an unofficial fan-made tracker. HUNTER×HUNTER and its related marks
belong to their respective rights holders.
License
The application code is available under the MIT License.
Geist is copyright Vercel and licensed under the SIL Open Font License 1.1.
Lucide icons are licensed under the ISC License.
Statistical estimates and post archive
The next unpublished chapter page includes two explicitly labelled Bayesian
models: a conjugate log-normal survival reference and a Gamma-Poisson production
scenario informed by Togashi's sourced manuscript reports. Both integrate
parameter uncertainty and expose assumptions, predictive intervals and sensitivity.
The production scenario has only one observed editorial cycle; it is not validated.
See the mathematical specification for equations, priors,
chronological backtests, numerical checks and limitations. Reproduce the report
with npm run forecast:report -- 2026-09-12. Neither model writes official dates.
To backfill Togashi's original posts without replaying notifications or changing
tracker state, run node scripts/import-togashi-archive.mjs --originals-only.
Omit --originals-only to reuse the existing Gemini translation and image-text
pipeline (requires GEMINI_API_KEY; respects a minimum 13-second request spacing).
The X endpoint requires X_BEARER_TOKEN. Optional --since YYYY-MM-DD,
--limit 1..100, and --input path-to-saved-x-response.json bound the import.
The default import covers up to 50 posts from 2026 onwards in the most recent API
page, excluding replies/reposts, and does not claim exhaustive coverage.
Re-running skips translated posts and resumes missing translations.
The repository archive preserves old article URLs; the public polling API keeps
its 50-post limit. Missing translations are explicitly labelled in the UI.
The home page now keeps publication status, production progress and the newest
Togashi post in focus. Shared navigation leads to the tweet archive, publication
history and official reading options. The next-chapter forecast starts with a
clearly unofficial central date, an 80% model interval and the five most probable
calendar months. Detailed models, assumptions and validation remain expandable.
Reading-service descriptions cite publisher pages; unverified availability is
labelled rather than inferred from the interface language.
Le jeu communautaire sans compte (D1, liens privés de récupération et défis entre amis) est documenté dans PREDICTION-GAME.md. Pour suivre les changements en direct avec la D1 Cloudflare hxh-predictions, lancer npm run dev, npm run game:dev et npm run game:live, puis ouvrir uniquement http://localhost:3001/predictions. Les votes de cet aperçu sont enregistrés dans Cloudflare D1. Turnstile utilise un widget propre à l’aperçu ; l’email reste indisponible jusqu’à la configuration de Resend.
For disposable local votes and friend challenges, run npm run dev and npm run game:preview, then open http://localhost:3002/predictions. This preview stores data only in memory and never calls the production game API.
