https://macworks.dev/tags/html5-canvas/Recent content in Html5 Canvas on MacWorksHugoenhttps://macworks.dev/docs/archives/blogs/engineer-blogs-2026-05-02/Mon, 01 Jan 0001 00:00:00 +0000https://macworks.dev/docs/archives/blogs/engineer-blogs-2026-05-02/<h1 id="engineering-reads--2026-05-02">Engineering Reads — 2026-05-02<a class="anchor" href="#engineering-reads--2026-05-02">#</a></h1> <h2 id="the-big-idea">The Big Idea<a class="anchor" href="#the-big-idea">#</a></h2> <p>The most valuable technical insights often come from returning to raw browser primitives and bypassing heavy orchestration layers. Whether you are stripping away Node-based test runners to verify UI behavior directly, or relying on native HTML5 to build interactive mathematical concepts, stepping outside complex build pipelines yields faster feedback loops and a deeper understanding of underlying mechanics.</p> <h2 id="deep-reads">Deep Reads<a class="anchor" href="#deep-reads">#</a></h2> <p><strong>Testing Vue components in the browser</strong> · Julia Evans · <a href="https://jvns.ca/blog/2026/05/02/testing-vue-components-in-the-browser/">Source</a> This article explores how to write end-to-end integration tests for Vue components without relying on Node, Deno, or unwieldy orchestration tools like Playwright. The technical approach involves mounting components to invisible, off-screen DOM elements and executing the QUnit testing framework directly within a browser tab, utilizing a server endpoint to reset SQL database fixtures to a known state. The author candidly details the complexities of this raw approach, particularly the architectural friction of polling the DOM for readiness rather than relying on flaky sleep commands, and the nuance required to manually dispatch events to simulate form inputs. Engineers suffering from frontend build-tool fatigue should read this for a refreshing, lightweight perspective on verifying UI behavior using native capabilities, including Chrome&rsquo;s built-in code coverage tools.</p>