Changelog

2025-12-02 - 3.1.0 - feat(TypedSocket)

Add SmartServe integration to TypedSocket, support SmartServe connections and tagging; update dependencies and docs; remove GitLab CI config

Add TypedSocket.fromSmartServe(smartServe, typedRouter) to bind TypedSocket to an existing SmartServe instance for native WebSocket handling.
Introduce ISmartServeConnectionWrapper and wrapSmartServePeer to provide tag compatibility between SmartServe (Set) and TypedSocket (id/payload). Tag payloads are stored in peer.data with 'typedsocket_tag' prefix.
Server-initiated requests in SmartServe mode use TypedRouter.fireEventInterestMap to correlate requests and responses asynchronously.
Extend createTypedRequest, findAllTargetConnections, findTargetConnection, findAllTargetConnectionsByTag and findTargetConnectionByTag to support both Smartsocket and SmartServe backends (via wrappers).
eventSubject: Emit a warning and return a new Subject in SmartServe mode (SmartServe lifecycle/events should be consumed via SmartServe hooks).
stop(): In SmartServe mode TypedSocket clears internal wrappers but does not stop SmartServe (SmartServe lifecycle is managed externally).
Add optional peer dependency @push.rocks/smartserve and expose type-only imports in ts/typedsocket.plugins.ts.
Bump several devDependencies and runtime dependencies to newer versions (tsbuild, tsbundle, tsrun, tstest, smartenv, smartserve, smartjson, smartrx, smartsocket, smartstring, smarturl).
Update README and readme.hints with SmartServe integration docs and examples.
Remove .gitlab-ci.yml (CI configuration removed).

Small patch release.

Major 3.0.0 release with core updates and documentation improvements.

Breaking change in core introduced in 2.0.28; important compatibility considerations.

BREAKING CHANGE(core): update — review integration points before upgrading.
This capstone release follows a series of patch releases addressing stability and core behavior.

Introduction of the 2.x stable line and subsequent patch series.

2.0.0 initial release of the 2.x series.
Follow-up patch releases (2.0.1 through 2.0.27) contain numerous "fix(core): update" changes — ongoing bug fixes, stability improvements, and small core adjustments across 2022–2023.
Users upgrading from 1.x should review 2.x changes and the 2.0.28 breaking change above.

Initial implemented functionality and the start of 1.x maintenance.

fix(core): implement basic functionality — initial usable feature set implemented in 1.0.2.
Subsequent 1.0.3 through 1.0.27 releases (2020–2022) included ongoing fixes and minor updates to stabilize the 1.x line.