yceffort
20 POSTS

Debugging 1

  • #web-performance#debugging#blogging

    Which Element Caused This Blog's CLS

    Two causes found through the shifted elements recorded alongside CLS values: a decorative element that follows the cursor and was counted as a layout shift, and a home page list that pushed the footer down while the overall p75 stayed at 0.000. Both were confirmed with field data and lab reproductions.

    20 min read
  • ◆ Page Preservation in Next.js Part 2
    #nextjs#memory#web-performance

    Why Did Next.js's Last Three Leave Nine Posts Behind?

    Next.js is said to preserve the last three pages, yet nine posts remained on this blog. A sequential navigation experiment measures how far preservation reaches, then looks at managing memory by separating work to stop when hidden from state worth keeping.

    16 min read
  • #react#debugging#nextjs

    Why Does the Body of a Static Page Wrapped in Suspense End Up in a Hidden div?

    Since React 19.2, content wrapped in Suspense can be moved into a hidden element even on a static page whose render has already finished. I traced how the post bodies on this blog shipped that way from May to early November, using the React source, version-by-version reproductions, and the HTML left in the Wayback Machine.

    20 min read
  • ◆ Improving number-flow Part 4
    #web-performance#animation#debugging

    How Far Will Agents Fix number-flow?

    I compared number-flow as fixed by five coding agents against my fork v0.2.1 once more. Performance reports changed with the font, the code went through a review with the authors hidden, and a follow-up experiment ended with keeping the mask default.

    Updated 31 min read
  • ◆ Improving number-flow Part 3
    #web-performance#browser#debugging

    Reducing Forced Synchronous Layout in the number-flow Update Path

    Every time the value of number-flow changed, style and layout were being recalculated several times over. This post records the performance change observed after 0.2.1 reordered how the library reads and writes the DOM, and the costs that remain.

    Updated 26 min read
  • ◆ Core Web Vitals 직접 수집하기 Part 4
    #web-performance#devops#debugging

    Self-Hosting Core Web Vitals Collection for a Quiet Blog

    Moved a Core Web Vitals collection setup designed for shared observability infrastructure to my personal blog. Fixed a dashboard left empty by sparse traffic and changed when metrics are collected for ordinary browsers. Along the way I found why some query results went missing, and worked out how much five days of data can support.

    32 min read
  • ◆ Core Web Vitals 직접 수집하기 Part 3
    #web-performance#devops#debugging

    Sending the Core Web Vitals of an App Webview to a Shared Observability Platform

    Sent the Core Web Vitals measured in an app webview to an observability platform shared by many teams. The webview gave no signal on leaving, and tail sampling, delta-to-cumulative conversion and Tempo queries each dropped values in their own way without raising an error. For every setting that could not be changed, re-measured what was lost in a reproduction environment.

    Updated 37 min read
  • ◆ Core Web Vitals 직접 수집하기 Part 2
    #web-performance#debugging#browser

    Sending Core Web Vitals at the Moment of Leaving the Page

    Traced why CLS and INP go missing when the page is left, through the transport of OTel JS and the order in which flush runs.

    Updated 22 min read
  • ◆ Core Web Vitals 직접 수집하기 Part 1
    #web-performance#debugging#browser

    When Does web-vitals Report Core Web Vitals

    Checked the conditions under which web-vitals 6.2.3 reports each metric, and why INP goes missing when the page is left right after a click.

    Updated 33 min read
  • ◆ Building coldpath Part 4
    #bundler#debugging#compiler

    How Bundlers Remember Imports

    Tracing a coldpath misclassification that read every synchronous dependency in the Turbopack analysis file as a static import. This post compares the graph information and build output of webpack, Turbopack, Vite, and esbuild, and looks at which clues reveal the original syntax and which cases cannot be recovered.

    29 min read
  • ◆ Page Preservation in Next.js Part 1
    #nextjs#react#debugging

    Pages You Leave Don't Die, They Hide: Next.js cacheComponents and React Activity

    Next.js 16's cacheComponents hides the pages you leave with React Activity instead of unmounting them. Following a three.js canvas that went blank after a back navigation, I read the router, React, and react-three-fiber source and reproduced it in a browser.

    34 min read
  • ◆ Building coldpath Part 3
    #debugging#web-performance

    Tracing Toss Securities JavaScript Without Source Maps

    Chuseok side quest, part 3: with love, to Toss Securities

    26 min read
  • ◆ Building coldpath Part 2
    #web-performance#bundler#debugging

    Building a Bundle Analyzer with V8 Coverage and Source Maps

    Chuseok side quest, part 2: building a V8 coverage analyzer, one dead end after another.

    Updated 24 min read
  • ◆ Building coldpath Part 1
    #web-performance#bundler#blogging

    Tracing When This Blog's JavaScript Actually Runs

    Chuseok side quest, part 1: starting with my own blog

    20 min read
  • #bundler#web-performance#debugging

    Tearing Apart a Third-Party SDK and Rebuilding It My Way: Without Touching a Single Line of Logic

    I imported one constant and 97.7% of the bundle came along with it. The vendor had no timeline for a fix, so I recovered over 400 TypeScript files from the published source maps, rebuilt the build, entry points, and dependencies while leaving the logic alone, and cut the raw size of /send by 77.5%. All 1,932 tests passed, but a few of them were checking nothing at all, so I had to work out again how far I could confirm that the rebuilt SDK behaves the same as the original.

    41 min read
  • ◆ Service Worker Caching Deep Dive Part 3
    #service-worker#web-performance#caching

    Measuring the Cost of Going Through a Service Worker: Building in the Lab the Control Group GA4 Could Not Give Me

    I set out to confirm the 500 ms that part 2 left as the cost of going through the worker, but the hard reloads that would form the control group arrive at under one a day. With a control group built from Playwright and a shaping proxy, going through the worker cost 2 ms on a navigation. Most of the extra time on a post click came from the worker saving the post HTML in the background over the same connection, and the gap between lab and field data was a measurement definition difference caused by 103 Early Hints.

    Updated 50 min read
  • #debugging#bundler#nextjs

    Next.js Turbopack Turned One Singleton into Two: A Scope Hoisting Bug and a Circular Import

    In a Next.js 16 Turbopack production build, a module-scope singleton became two live instances at runtime. Inside the same synchronous block, one condition contradicted the other, and responses that arrived in 30ms still timed out. I found the cause by following a partial scope hoisting merge and a circular import through the bundle output, and confirmed the same bug had already been fixed upstream.

    16 min read
  • #animation#web-performance#debugging

    Killing Frame Drops in a framer-motion Banner: Two Wrong Turns and One Easing Function

    A banner built with framer-motion made the entire home screen stutter for the 0.6 seconds it took to open. My guess at the cause from reading the code was overturned twice by measurement, and in the end a single easing function removed the reflow.

    30 min read
  • #typescript#blogging#npm

    What Happens When You Install typescript@7: A Blog Monorepo Migration Log

    I dropped typescript 7.0.2 into a monorepo where pnpm lint took 12 minutes 32 seconds. Type checking passed, but next build broke and lint crashed, so I spent a day swapping eslint and prettier for oxlint and oxfmt. Lint now finishes in 1.9 seconds even with type-aware rules, and the build takes as long as before.

    11 min read
  • ◆ Kubernetes for Frontend Developers Part 4
    #kubernetes#devops#debugging

    How Do Pods Terminate? Measuring the Causes and Fixes of Deploy-Time Errors

    Even a deploy that changes not a single line of code still fails requests. I tagged every failed request during rolling deploys by type and timestamp, found four causes, and added fixes one at a time until failures reached zero. The post also checks the actual Next.js shutdown code and the real CrashLoopBackOff restart intervals.

    Updated 20 min read