Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Debuger breakpoints dont work on V133

  • 1 réponse
  • 0 a ce problème
  • 1 vue
  • Dernière réponse par marek.urban

more options

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
Captures d’écran jointes

Solution choisie

got fixed in v 134

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

more options

Solution choisie

got fixed in v 134

Cela vous a-t-il été utile ?

Poser une question

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.