2026-05-30 00:39:39 +01:00
|
|
|
{
|
|
|
|
|
"name": "cultnet-ts",
|
2026-08-18 17:21:58 +02:00
|
|
|
"version": "0.2.0",
|
2026-05-30 00:39:39 +01:00
|
|
|
"description": "CultNet-style typed direct-pipe messaging and state replication for TypeScript runtimes.",
|
|
|
|
|
"main": "dist/index.js",
|
|
|
|
|
"types": "dist/index.d.ts",
|
2026-07-13 23:47:38 +01:00
|
|
|
"exports": {
|
|
|
|
|
".": {
|
|
|
|
|
"types": "./dist/index.d.ts",
|
|
|
|
|
"require": "./dist/index.js",
|
|
|
|
|
"default": "./dist/index.js"
|
2026-08-18 00:05:57 +02:00
|
|
|
},
|
|
|
|
|
"./contracts": {
|
|
|
|
|
"types": "./dist/contracts.d.ts",
|
|
|
|
|
"require": "./dist/contracts.js",
|
|
|
|
|
"default": "./dist/contracts.js"
|
2026-07-13 23:47:38 +01:00
|
|
|
}
|
|
|
|
|
},
|
2026-05-30 00:39:39 +01:00
|
|
|
"files": [
|
|
|
|
|
"dist",
|
|
|
|
|
"contracts"
|
|
|
|
|
],
|
|
|
|
|
"scripts": {
|
|
|
|
|
"contracts:generate": "node tools/generate-swarm-contracts.mjs",
|
2026-07-13 23:47:38 +01:00
|
|
|
"build": "node tools/generate-swarm-contracts.mjs && node ../../node_modules/typescript/bin/tsc -p tsconfig.json",
|
|
|
|
|
"prepack": "node tools/generate-swarm-contracts.mjs && node ../../node_modules/typescript/bin/tsc -p tsconfig.json",
|
|
|
|
|
"typecheck": "node tools/generate-swarm-contracts.mjs && node ../../node_modules/typescript/bin/tsc -p tsconfig.json --pretty false",
|
|
|
|
|
"test": "node tools/generate-swarm-contracts.mjs && node ../../node_modules/typescript/bin/tsc -p tsconfig.json && node ../../node_modules/typescript/bin/tsc -p tsconfig.test.json && node --test dist-test/test/*.test.js",
|
Stop the interop harness leaking peers and hanging after it passes
The suite finished its work in about 60 seconds and then never exited. Four runs
were left alive for hours, holding 11 node and 2 dotnet peers, and a stranded
peer holding cultnet_interop_peer.exe is what made two unrelated cargo builds
fail with LNK1104. In CI this is a job that burns its whole timeout on green
tests.
Two real defects, found by asking the stuck process what it was waiting on
rather than by guessing. process.getActiveResourcesInfo reported four UDPWraps
and two PipeWraps still held after the last test.
The four UDP sockets: eight tests bind a server socket with bindUdpSocket and
close only the transport wrapper in their finally, never the socket itself. Four
leaked per run, matching the four Python lanes that fail on a machine without
msgpack -- the wrapper is built inside the try, so when the peer's readiness
rejects it never exists to be closed, and the raw socket is orphaned. Now closed
through a guarded helper that tolerates a transport having adopted it.
The teardown registration: t.after was registered after every `await ready`, so
a peer whose readiness rejected skipped the registration entirely and stranded
every peer already spawned. Moved ahead of the spawns at all four sites.
With those fixed the suite still does not drain on its own, so test:interop now
passes --test-force-exit. That is safe only because cleanup demonstrably
completes first: a forced run now leaves zero peers behind, where before it left
nine. Forcing the exit without the fixes above would have guaranteed orphans
rather than prevented them.
Verified: 65 seconds, exit 1, the expected 15 pass and 12 fail, no surviving
processes. The 12 failures are the Python lanes, which cannot run on this
machine and are unrelated.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-04 16:32:10 +02:00
|
|
|
"test:interop": "node tools/generate-swarm-contracts.mjs && node ../../node_modules/typescript/bin/tsc -p tsconfig.json && node ../../node_modules/typescript/bin/tsc -p tsconfig.test.json && node --test --test-force-exit dist-test/test/interop/*.test.js"
|
2026-05-30 00:39:39 +01:00
|
|
|
},
|
|
|
|
|
"keywords": [
|
|
|
|
|
"messagepack",
|
|
|
|
|
"networking",
|
|
|
|
|
"pipes",
|
|
|
|
|
"cultcache",
|
|
|
|
|
"gamecult",
|
|
|
|
|
"typescript"
|
|
|
|
|
],
|
|
|
|
|
"author": "metacratic",
|
|
|
|
|
"license": "MIT",
|
2026-07-13 23:47:38 +01:00
|
|
|
"repository": {
|
|
|
|
|
"type": "git",
|
|
|
|
|
"url": "git+https://github.com/GameCult/CultLib.git",
|
|
|
|
|
"directory": "packages/cultnet-ts"
|
|
|
|
|
},
|
|
|
|
|
"bugs": {
|
|
|
|
|
"url": "https://github.com/GameCult/CultLib/issues"
|
|
|
|
|
},
|
|
|
|
|
"homepage": "https://github.com/GameCult/CultLib/tree/main/packages/cultnet-ts#readme",
|
|
|
|
|
"engines": {
|
|
|
|
|
"node": ">=18"
|
|
|
|
|
},
|
2026-05-30 00:39:39 +01:00
|
|
|
"dependencies": {
|
|
|
|
|
"@msgpack/msgpack": "^3.1.3",
|
|
|
|
|
"ajv": "^8.17.1",
|
Give every cultcache-ts document type one home store
Cut 5 (TypeScript). The cache no longer mirrors: StoreRoute and its mirrors
list are gone, #resolveRoute returns the single home store (the store that
claims the type, else the generic store), and put, putEnvelope and delete write
exactly one store.
addBackingStore now refuses a second generic store and a type already claimed
by another store, attaching nothing when it refuses, matching C#. No bytes
change; nothing in CultLib attached more than one store.
Tests: rejects a second generic backing store, rejects a type registered to
two stores, routes each type to its home store. The writer-by-reader interop
test now runs the C# write-routed mode and checks that catalog.cc and run.cc
are each a complete v1 snapshot holding only their own record, and that every
reader (TS, Rust, C#, Python) reads the routed catalog store.
Version 0.13.5 -> 0.14.0; cultnet-ts and cultmesh-ts depend on ^0.14.0 so the
workspace link still satisfies their range.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-14 00:37:31 +02:00
|
|
|
"@gamecult/cultcache-ts": "^0.14.0"
|
2026-05-30 00:39:39 +01:00
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
|
|
|
|
"@types/node": "^24.0.0",
|
|
|
|
|
"json-schema-to-typescript": "^15.0.4",
|
|
|
|
|
"typescript": "^5.9.0",
|
|
|
|
|
"zod": "^3.25.76"
|
|
|
|
|
}
|
|
|
|
|
}
|