Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Debuger breakpoints dont work on V133

  • 1 èsì
  • 2 ní àwọn ìṣòro yìí
  • 105 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ marek.urban

So i am using ReseourceOverride AddOn to debug a js library on standard install of firefox. This works by using the site as normal but resource override has instruction to replace request for the library on server with one requesting it from localhost. This used to work without problems. However today i noticed that breakpoints aren't getting hit. I have downgraded to version 132.0.2 and breakpoints work once again. I think this has something to do with debug sources, since the load process adds 2 sources, webpack containing uncompiled code and where i set break points, and webpack-internal which i think is built js library before getting minified. Links to exceptions in console also dont work instead of linking to webpack seemlesly, the adress says webpack-internal and link open a new window and complains that the adress is nonsense (see attached images)

Thatnks for the help

So i am using ReseourceOverride AddOn to debug a js library on standard install of firefox. This works by using the site as normal but resource override has instruction to replace request for the library on server with one requesting it from localhost. This used to work without problems. However today i noticed that breakpoints aren't getting hit. I have downgraded to version 132.0.2 and breakpoints work once again. I think this has something to do with debug sources, since the load process adds 2 sources, webpack containing uncompiled code and where i set break points, and webpack-internal which i think is built js library before getting minified. Links to exceptions in console also dont work instead of linking to webpack seemlesly, the adress says webpack-internal and link open a new window and complains that the adress is nonsense (see attached images) Thatnks for the help
Ìsopọ̀ yíyà aṣàfihàn

Ọ̀nà àbáyọ tí a yàn

got fixed in v 134

Ka ìdáhùn ni ìṣètò kíkà 👍 0

All Replies (1)

Ọ̀nà àbáyọ Tí a Yàn

got fixed in v 134