Repository navigation
v0.1.1 — the packages actually run once installed
If you installed 0.1.0, it did not work. This release is the fix.
npx trainctl died on startup with ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING: 0.1.0 published its TypeScript sources with exports and bin pointing at .ts files, and Node deliberately refuses to strip types for anything under node_modules. That works in the repository and nowhere else. Every test ran from the source tree, so nothing caught it until the first npx after publishing.
Fixed
- Packages ship compiled JavaScript (
dist/) with type declarations and source maps, built bypnpm build; the TypeScript sources travel alongside, so a stack trace still lands on readable code. Development is unchanged — the repository still runs straight from TypeScript. - Export filenames dropped the Polish
ł:interwałybecameinterwa-y.fit, and a race called Bieg Wrocławski producedbieg-wroc-awski.ics. Letters Unicode does not decompose (ł ø đ ß æ œ) are transliterated now. - The MCP server reported a hard-coded
0.1.0in its handshake regardless of the package version. Both binaries read their own manifest.
Added
trainctl --version— the bug-report template asked for it before it existed.- Two guards so this class of bug cannot ship again:
packaging.test.tsasserts the published entry points are built files (and that versions match and descriptions are English), and CI packs all five tarballs, installs them into a clean directory, and runs the CLI and the MCP server fromnode_modules.
Changed
- Package descriptions on npm are English; they were Polish in 0.1.0.
0.1.0 is deprecated on npm. Full detail: CHANGELOG.md, and the reasoning is recorded as ADR-026 in SPEC.md.