Repository navigation
v1.2.2
Nothing that was exported has changed.
Changed
- The README takes the family's one layout, fully: a hero picture of the explorer on a desk and on a phone in light and dark, a picture of each part of the explorer (a stream, a shuffle, the day's seed in UTC and in a zone, parts, and a position kept as JSON), an Install section, an Examples section of twelve examples whose output is what they print, and the sections the standard asks for. Its pictures are in
docs/images(WebP, light and dark) and are retaken withpnpm screenshots:readme(it replacespnpm pictures,docs/desktop.jpganddocs/phone.jpg); they are not in the tarball, andpnpm test:packagefails if one is. docs/spec.md,docs/spec-vectors.jsonanddocs/strings-ja.mdare no longer in the tarball: the family's standard keepsdocs/out of what npm installs, and the README links the specification on GitHub, where it is read. The specification itself is unchanged, and so is every number the package draws.- The README's CSV and help blocks name their language (
text), and the API section's sub-headings read "Stream calls" and "Draw calls", so that every heading in the README is its own anchor. pnpm test:readmetype-checks and runs every TypeScript and JavaScript example in the README against the built package, as a CI job of its own, andpnpm checkholds the README to the family's lint.- Repository only: the package and everything it exports are unchanged.
CONTRIBUTING.mdis the family's one text with a section of its own for Tane, held to the master in johnmorrisdotca/.github bysrc/family.test.js;ci.ymlandpages.ymlare 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 own stylesheet is
demo/tane.css, named for the package like 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.