Skip to the content

Tobiishi飛び石

Jump pegs on nine native boards, generate seeded solvable challenges and build a peg-solitaire player for your page.

Tobiishi is the Japanese word 飛び石 for stepping stones. About the name

Contents

Changelog

All notable changes to this project are written here. The format follows Keep a Changelog, and the project uses Semantic Versioning.

[Unreleased]

  • The README opens with the package's thumbnail, and the demo carries it as its link preview (og:image) and publishes the card, a dark card and an icon on Pages at thumbnail.png, thumbnail-dark.png and icon.png.

[0.3.1] - 2026-10-31

Changed

  • Biome replaces ESLint as the formatter and linter, with the family's shared settings in scripts/biome-family.json; pnpm lint checks formatting too, and pnpm format applies it. The code is formatted once to 120 columns. Nothing a user of the package sees has changed.
  • pnpm check also holds every source file to at most 500 lines of code (scripts/check-size.mjs; blank lines, comments, tests and data files are not counted). TypeScript targets ES2022 and refuses switch fallthrough and unmarked overrides.

[0.3.0] - 2026-10-14

The game is a custom element with the family's standard embed attributes and a shared builder, and the package has an English and Japanese documentation site with a checked example for every export. The board, the rules, the solver and saved games are unchanged.

Added

  • Add the bilingual documentation site, checked public examples, paired guides, local search and machine-readable pages.
  • Add the shared embed builder, validated iframe route, reflected settings and custom-tag helpers. Preserve the existing language/just-board aliases and game-shaped change event; events now cross shadow roots with JSON-safe detail. Add native player presentation updates so language, material and device theme changes keep progress.
  • Share a package-independent embed builder for option controls, preview adapters, code tabs and shareable links.

Changed

  • CI installs WebKit as well as Chromium for the demo's browser tests, which run in both.
  • The API link in the header reads "API" in English, so that the header takes the same number of rows in English and in Japanese on a phone, as the demo's test of a language change asks.
  • Synchronize documentation tooling for repository layouts, generated type references, Node entry points and repository-specific README links.
  • Keep complete resource catalogues on the documentation entry index and the active resource beside core navigation; render valid default imports in HTML and Markdown.
  • Preview and browser-test ports now default to 6901, with PORT/TEST_PORT overrides.
  • Group the package family by kind, alphabetize each group, and include the geography packages and REST in Pieces in the shared footer and README.
  • Update the shared family description for addresses in all seven supported countries, including France and Germany.

[0.2.3] - 2026-10-06

Nothing that was exported has changed.

Changed

  • The README takes the family's one layout, fully: a hero picture of the demo on a desk and on a phone in light and dark, a picture of every board and of the selected peg, the three materials and the short goal challenges, an Examples section of thirteen runnable examples, an Accessibility section, and the API summary with a link to the guide. Its pictures are in docs/images (WebP, light and dark) and are retaken with pnpm screenshots:readme; they are not in the tarball, and pnpm test:package fails if one is.
  • pnpm test:readme type-checks and runs every TypeScript and JavaScript example in the README against the built package, as a CI job of its own, and pnpm check holds the README to the family's lint (sections in order, a language on every fence, pictures with alt text, widths and captions, no marketing words).
  • The README said the element could be given seed="today". The package never reads the date: a challenge of the day is seed="2026-10-06", written by the page. The README now says so.
  • Repository only: the package and everything it exports are unchanged. CONTRIBUTING.md is the family's one text with a section of its own for Tobiishi, held to the master in johnmorrisdotca/.github by test/family.test.js; ci.yml and pages.yml are the family's one text (pnpm check, the demo, and the package on Linux, macOS and Windows), and any jobs of the package's own after them.
  • The demo's page titles read Tobiishi · pitch, like the rest of the family's.

Fixed

  • The API reference page wraps a long entry path instead of running about 2 px wider than a 360 px screen. Nothing the package exports has changed.

[0.2.2] - 2026-10-05

Nothing that was exported has changed.

Added

  • A test holds every @johnmorrisdotca/tobiishi@N version pin in the README to this package's major version.

Changed

  • The family's list, in the README and in the demo's footer, names all twenty-four packages, Karakuri and Houseki included.
  • The npm description is one sentence of 250 characters or fewer, so npm and its search show it whole; it is also the repository's About text. homepage is the demo site and author is "John Morris", the same in every package.
  • The GitHub Actions workflows use the current versions of the actions (checkout 7, setup-node 7, pnpm/action-setup 6; configure-pages 6, upload-pages-artifact 5 and deploy-pages 5 for Pages), which clears GitHub's Node 20 deprecation warning.
  • The README has the family's sections in the family's order (In 30 seconds, Features, Use it in your project, API, Theming, Limits, Browser support, Languages, Roadmap, Architecture, Where it comes from, Changes), the family list sits under "Where it comes from", and a test holds it to them.
  • ESLint joins the checks, as in the other packages (pnpm lint is part of pnpm check), the scripts run through pnpm rather than npm run, pnpm test:demo builds the demo and runs the browser tests, and Playwright is 1.63.

[0.2.1] - 2026-10-05

  • A started challenge no longer says its number of jumps twice ("Hard · 9 jumps · 9 jumps").
  • The pack, difficulty and target-hole selects are styled like the board and piece settings.
  • One CI workflow, not two, runs on a push to main and on a pull request; the release's notes are the changelog's section.
  • The demo, its README family list and its tests are the family's own: the shared header, footer and list of twenty-two, written from one template.
  • Complete package presentation: desktop and phone screenshots, badges, demo/API links, targeted keywords and linked MIT licence.
  • Source-derived API reference and public API comments, contribution/security files, and a package presentation gate.

[0.2.0] - 2026-10-05

  • Nine named board packs with three target holes and three short, witnessed challenge lengths per pack: 81 solvable starts.
  • English/Japanese target-hole selection and device-local progress for named challenge runs.

[0.1.0] - 2026-10-04

First release candidate: immutable peg solitaire engine, nine board shapes, seeded proof-carrying challenges, heart/star/hexagon outlines and configurable rectangles, bounded solver, SVG materials, accessible English/Japanese play, custom element, save/replay validation, and demo.

View sourceEdit on GitHubMade from the source of @johnmorrisdotca/tobiishi 0.3.1.