fix(ts_web_inject): improve ReloadChecker resilience and TypedSocket handling
This commit is contained in:
11
changelog.md
11
changelog.md
@@ -1,5 +1,16 @@
|
||||
# Changelog
|
||||
|
||||
## 2026-03-03 - 8.4.2 - fix(ts_web_inject)
|
||||
improve ReloadChecker resilience and TypedSocket handling
|
||||
|
||||
- Added retry counters and limits for service worker subscription (MAX_SW_RETRIES) and traffic logging setup (MAX_TRAFFIC_LOGGING_RETRIES) to avoid infinite retry loops
|
||||
- Made TypedSocket connection non-blocking by connecting in the background (createClient().then(...).catch(...)) so HTTP polling isn't blocked
|
||||
- Introduced typedsocketConnected flag to track WS state and avoid double-connects; early-return if typedsocket exists
|
||||
- Adjusted connection lifecycle handling: only trigger reload check when reconnect completes; set backendConnectionLost/state appropriately
|
||||
- Adaptive polling interval: poll every 5s when WebSocket is not connected, otherwise 120s
|
||||
- Added safer failure handling for TypedSocket connection with warning logs on errors
|
||||
- Simplified/changed several logger levels/messages (info -> ok/warn) and removed some noisy info logs
|
||||
|
||||
## 2026-03-03 - 8.4.1 - fix(statuspill)
|
||||
wait for document.body before appending status pill when script loads before <body> is parsed; defer via DOMContentLoaded or requestAnimationFrame
|
||||
|
||||
|
||||
Reference in New Issue
Block a user