[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$flvbjeba5fj7t":3},{"code":4,"message":5,"data":6,"timestamp":26},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":22,"homepage":23,"updated_at":24,"history":25},"SukkaW\u002Fspeed.skk.moe",23,"The source code of the https:\u002F\u002Fspeed.skk.moe","TypeScript",96,11,40,2,[],"Source for a static, build-time-configured network speed test page aimed at developers who want to self-host one.","This is the source behind the [speed.skk.moe](https:\u002F\u002Fspeed.skk.moe) network speed test site. It works best as a starting point for someone building their own static speed test page, not as a packaged product with step-by-step setup.\n\n## The problem\n\nPutting a speed test on your own domain usually means embedding a third-party widget or assembling a frontend, endpoint list and host yourself. Here, endpoints are supplied at build time via the `SPEEDTEST_TARGETS` environment variable, the build writes static files to `out\u002F`, and any static host can serve them. The result is a page whose targets the operator chooses.\n\n## What's different\n\nTargets are fixed at build time rather than chosen in a settings menu. That keeps the frontend static and the deployed site reproducible, but changing an endpoint means rebuilding and redeploying, and multiple target sets require separate builds. The build also expects a `\u002F_sukka\u002Fapi\u002Fgeo` endpoint that is not in the repo and must be served separately; the [README](https:\u002F\u002Fgithub.com\u002FSukkaW\u002Fspeed.skk.moe\u002Fblob\u002Fmaster\u002FREADME.md) gives no replacement or response shape, so the source alone does not describe a complete deployment.\n\n## Who should try it\n\nThis suits developers comfortable reading a TypeScript frontend project who want a reference implementation or a base to adapt, and who can supply endpoints and the missing geo API. It is a poor fit for anyone wanting a ready-made speed test appliance: there is no packaged release, little documented configuration beyond the environment variable, and no described maintenance path. If you only want to measure your own connection, use the hosted site.\n\n## Requirements and limitations\n\nConstraints come from the README: `pnpm` for dependencies, a `SPEEDTEST_TARGETS` value at build time (copy `.env.example` locally), and a separate `\u002F_sukka\u002Fapi\u002Fgeo` implementation before the production build is complete. Because that API's request and response are undocumented, adopting the project means designing it. Upkeep also matters: test endpoint hosts change independently of this code, so a deployed page needs its target list reviewed when endpoints move. Build-time targets are a deliberate constraint, not a runtime switch in this source.\n\n## HotRepo's take\n\nHotRepo first records the repository at 2 days old, with 96 total stars and #24 on the NEW-REPOSITORY board (not the overall Trending board) for TypeScript, observed 2026-10-25. The sample spans only 2026-10-24 to 2026-10-25 with no daily-board history, so persistence cannot yet be judged. Before investing time, check whether you can implement or obtain the `\u002F_sukka\u002Fapi\u002Fgeo` endpoint, since the build does not ship it.",{"slug":19,"name":20},"developer-tools","Developer Tools",[],"Apache-2.0","https:\u002F\u002Fspeed.skk.moe","2026-10-25T03:02:14Z",[],1792915312]