Category posts
The point is simple: place error boundaries on feature boundaries so UX survives failures. In Next.js, combine segment boundaries (error.js) with feature-level boundaries to localize crashes.
E2E tests replay critical user journeys in a real browser, catching breaks between pieces that unit and integration tests don’t cover alone.
One takeaway: Browsers load ESM by URL. Without a product-grade specifier-to-URL resolution path, bundlers become a practical dependency-resolution layer.
Client-side STT (speech-to-text) becomes practical not by "deploying models" but by designing "memory, loading, and streaming UI" from the start. Practical design for running 4B-scale speech recognition in browsers with WebGPU + WASM.
Bundle multiple files into a single ZIP archive directly in the browser. JSZip enables efficient client-side resource management and provides a seamless download experience for complex data.
Handling dates in Next.js requires care to avoid hydration mismatches. Use Moment.js for robust formatting and ensured consistency between server and client rendering.
Instead of creating the same method for every instance, share it on the Prototype, and close the scope with an IIFE for values that need to be hidden.
If yield is "yielding a value once," then yield* is "delegating the entire iteration of another iterable." It enables clean hierarchy in complex logic.
For tasks where "only the result is needed," such as deduplication and condition checking, the key is an API combination that reduces unnecessary iteration/copying.
By creating "classes that only change values" using CSS custom properties, CSS does not grow even if style combinations increase.
Maintenance becomes easier when callback-based asynchronous APIs are wrapped in Promises and sequential tasks are flattened with async/await + loops.
Learn various techniques for implementing file downloads in the browser using JavaScript.