egoist/poi

Breakpoints sometimes don't work in Chrome devtools until save

Open

#688 建立於 2020年5月3日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)JavaScript (5,251 star) (324 fork)batch import
help wantednot-staletype: bug

描述

I'm having an intermittent problem in Chrome DevTools.

I can set a breakpoint and it sometimes it will, and sometimes it won't work.

I know it's the right file, because when I go back to my IDE and hit save, the page will reload, and the breakpoint will get hit.

It feels like some kind of caching issue; I will have to resave the file I am setting the breakpoint in for it to be caught.

I don't think I'm doing anything special, in this case, it's just a TypeScript model that is consumed by a component tree.

I've had various situations when it wasn't working; I'll update this ticket as I discover them.

貢獻者指南

技術棧
javascripttypescript
領域
build systemtoolingdeveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
basic understanding of source mapsfamiliarity with Chrome DevTools debuggingbasic knowledge of webpack bundling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the source map generation and caching behavior in the poi bundler. Check if the issue is related to how webpack dev server handles hot module replacement (HMR) and source maps. Look for existing discussions or PRs about breakpoint reliability, and consider testing with different source map settings (e.g., 'cheap module source map' vs 'source map'). The issue mentions that saving the file in the IDE triggers a page reload and makes breakpoints work, so focus on understanding the caching mechanism and whether the bundler correctly updates source maps on file changes.