Fix build:ts: one text-only error factory in cultnet-ts (6 TS2345 in cultmesh-ts) #29
Loading…
Reference in a new issue
No description provided.
Delete branch "libby/cultmesh-ts-error-message-sites"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
npm run build:tswas red on main: PR #20 maderoutingHint,code,detailsrequired onCultNetErrorMessage, and six cultmesh-ts call sites (src/index.ts) still built{ schemaVersion, error }. Types are not loosened. cultnet-ts now ownscultNetTextError(error)(exported from the package root); the legacy-union decode incontracts.tsuses it (one place spelling the nulls), the six sites call it, and two test expectations incultmesh.test.tscompare against it. CHANGELOG Added entry in cultnet-ts.Local run (no scripts skipped)
npm run build:ts: clean.--test-force-exit): 277 run, 276 pass; the one failure is the esbuild-browser case (reads an emptypackage.jsonabove the checkout, env-specific, same on main).npm run test:pack:ts: closure smoke passes (4 scoped tarballs). The declared-ranges step after it still fails, unchanged (below).Not changed: declared-ranges
cultmesh-ts declares
@gamecult/cultcache-ts ^0.14.0, which admits tagcultcache-ts-v0.14.0; that tag lacksSchemaConflictError,schemaIdentityOfand four payload exports. They sit under cultcache-ts's Unreleased CHANGELOG, after 0.14.2, so bumping to ^0.14.1/^0.14.2 would be wrong (neither has them) and would only pass because those versions carry no tag. The fix is to release cultcache-ts (tag it) and then raise cultmesh-ts to that version.🤖 Generated with Claude Code