List the build tool and every bundle on the skill page
Merged
AL
18h ago+57+57+01234567890123456789-9-9-0123456789
Closes #17.
/h5p/skill/ wrote out the full address of each of the h5p-author skill's files, but none of the files its step 3 fetches where npm cannot be reached. A chat with the skill's text alone had to put a bundle's address together from its type, and a fetch tool may refuse that: an outside review of the skill had …/bundles/H5P.Blanks.zip refused so. missing-elements/h5p-offline-player#180 sends such a chat to this page for every address.
What changes
- The page lists the build tool and every bundle, each at its full address as its link and its text, in a section of its own after the type files.
src/_data/skill.jsnames them by the author package'scontentTypes, the list itswriteBundleswrites from, so the page, written before Vite writes the bundles, keeps no copy of the rule. Both are public exports of h5p-author 0.9.0: this needs no release and can merge first. - The SKILL.md test takes either release's addresses. It no longer expects
/h5p/build/types/<Type>.md, which 0.9.0 names and the next release does not; it still fetches every address SKILL.md gives. So the pin can move without changing the test. - The comment in
vite.config.tssays the page names the bundles.
Tested
pnpm build,pnpm typecheck,pnpm e2e: 16 pass. The new test holds the page's bundle links to/h5p/bundles/index.json, which Vite wrote: a page missing a bundle, or writing an address that is not whole, fails it (both tried).- With the next release's SKILL.md served in its place, the SKILL.md test passes.
- On Haiku, in a stand-in for a chat whose fetch tool opens only addresses seen whole, with npm cut off and this build of the site, given the next release's SKILL.md: all six runs opened this page and took every address from it, nothing refused, and the two given the build tool as served that kept to the bundle built a package that plays (details in missing-elements/h5p-offline-player#180's pull request).
Summary by cubic
The skill page now lists the build tool and every bundle it serves at their full addresses, so a chat that cannot reach npm can fetch the files step 3 of SKILL.md names without assembling bundle addresses from type names.
- The page lists
h5p-author.mjsand every bundle after the type files, each at its full address as its link and its text, named from the author package'scontentTypes— the same listwriteBundleswrites from — so the page keeps no copy of the rule and this needs no release. - The SKILL.md test accepts either release's addresses: it no longer expects
/h5p/build/types/<Type>.md, which h5p-author 0.9.0 names and the next release does not, and it holds the skill to a way to a type's file — 0.9.0's address or this page, which writes each one out — so the pin can move without changing the test.
Closes #17.