Links & resources

Bookmark this page: npm install target, these guides, TypeDoc, MCP, changelog, and source in one place.

The version below comes from packages/play-u1/package.json at build time—the same value published to npm.

Current package version (this docs build): v0.0.0same version field npm uses from packages/play-u1/package.json.

If you are building an app

WhatLink
Install@interfaces-technology/play-u1 on npm
Guides/docs on this site
API reference/reference/index.html (TypeDoc)
ChangelogCHANGELOG.md on main
Issues & sourcegithub.com/interfaces-technology/play-u1
MCP for assistantsMCP setup — endpoint https://play-u1.vercel.app/api/mcp
Vercel + Next.js appsusing-this-package-on-vercel.md

How this site fits together

  • @interfaces-technology/play-u1 — Published library (Gamepad API wrapper). Source: packages/play-u1 in the repo.
  • This site (play-u1.vercel.app) — MDX guides, TypeDoc under /reference/, Streamable HTTP MCP at /api/mcp.
  • play-u1-mcp workspace package — Optional standalone MCP server (HTTP or stdio) for self-hosting; not on npm. MCP setup, play-u1-mcp README, container on ghcr.io when main pushes.

MCP URLs

  • This deployment: https://play-u1.vercel.app/api/mcp · Local: http://localhost:3000/api/mcp after npm run docs:dev. Tools: list_guides, read_guide, search_docs.
  • Container: default HTTP path /mcp on your host—see MCP setup and the play-u1-mcp README.

If you maintain the library

Add a changeset (npx changeset from the monorepo root) when packages/play-u1 needs a release. After your PR merges to main, merge the Version packages PR to bump the library version and changelog; automation then creates the GitHub Release and CI publishes to npm. Use the skip-changeset label or npx changeset add --empty when no release is needed. Run npm test and npm run docs:build before merging risky changes. Full checklist: CONTRIBUTING.md. Short local reference: doc.md.