WebSocket reconnection and heartbeat mechanisms are being adopted more and more widely in frontend development. Drawing on real-world projects, this article takes a deep dive into their core principles and best practices.
Basic Usage
Here is a complete example:
import { useState, useEffect, useCallback } from 'react'
function DataList({ endpoint, pageSize = 20 }) {
const [data, setData] = useState([])
const [page, setPage] = useState(1)
const [loading, setLoading] = useState(false)
const fetchData = useCallback(async () => {
setLoading(true)
try {
const res = await fetch(`${endpoint}?page=${page}&size=${pageSize}`)
setData(await res.json())
} finally { setLoading(false) }
}, [endpoint, page, pageSize])
useEffect(() => { fetchData() }, [fetchData])
return <div>{loading ? <Spinner /> : <List items={data} />}</div>
}
Mind edge-case handling — it is critical in production.
Advanced Usage
The key is understanding the core logic:
type DeepPartial<T> = T extends object ? { [P in keyof T]?: DeepPartial<T[P]> } : T
interface AppConfig {
api: { baseUrl: string; timeout: number; retries: number }
ui: { theme: 'light' | 'dark'; language: string; pageSize: number }
}
type PartialConfig = DeepPartial<AppConfig>
function mergeConfig(defaults: AppConfig, overrides: PartialConfig): AppConfig {
const result = { ...defaults }
for (const key of Object.keys(overrides) as (keyof AppConfig)[]) {
if (overrides[key] && typeof overrides[key] === 'object') {
result[key] = { ...defaults[key], ...overrides[key] } as any
}
}
return result
}
Performance optimization always depends on the specific context — not every case calls for aggressive tuning.
Practical Cases
Here are a few ways we can improve on this:
:root {
--bg: light-dark(#fff, #1a1a2e);
--text: light-dark(#333, #e0e0e0);
--accent: light-dark(#2563eb, #60a5fa);
color-scheme: light dark;
}
.carousel {
display: flex; gap: 1rem; overflow-x: auto;
scroll-snap-type: x mandatory;
scroll-padding: 1rem;
}
.carousel__item {
flex: 0 0 80%; scroll-snap-align: start;
border-radius: 12px; transition: scale 0.3s ease;
}
This approach has been running stably in production for over six months and has proven itself in real use.
Performance Optimization
Let's start with the basic implementation:
import { useState, useEffect, useCallback } from 'react'
function DataList({ endpoint, pageSize = 20 }) {
const [data, setData] = useState([])
const [page, setPage] = useState(1)
const [loading, setLoading] = useState(false)
const fetchData = useCallback(async () => {
setLoading(true)
try {
const res = await fetch(`${endpoint}?page=${page}&size=${pageSize}`)
setData(await res.json())
} finally { setLoading(false) }
}, [endpoint, page, pageSize])
useEffect(() => { fetchData() }, [fetchData])
return <div>{loading ? <Spinner /> : <List items={data} />}</div>
}
This snippet shows the basic usage. In a real project you'll also need to account for error handling and edge cases.
Common Traps
Building on this, we can optimize further:
type DeepPartial<T> = T extends object ? { [P in keyof T]?: DeepPartial<T[P]> } : T
interface AppConfig {
api: { baseUrl: string; timeout: number; retries: number }
ui: { theme: 'light' | 'dark'; language: string; pageSize: number }
}
type PartialConfig = DeepPartial<AppConfig>
function mergeConfig(defaults: AppConfig, overrides: PartialConfig): AppConfig {
const result = { ...defaults }
for (const key of Object.keys(overrides) as (keyof AppConfig)[]) {
if (overrides[key] && typeof overrides[key] === 'object') {
result[key] = { ...defaults[key], ...overrides[key] } as any
}
}
return result
}
This pattern is especially useful in large projects and can significantly lower maintenance costs.
Summary
- Understanding the underlying principles matters more than memorizing APIs.
- Always verify compatibility before shipping to production.
- In team collaboration, conventions and documentation matter more than the technology itself.
