3 ms·

Why can’t you debug?

• ramraj07 4y ago
  Because it doesn’t throw an error, and it hands deep inside the vue code when an even to add one more nested component is triggered.
  • skybrian 4y ago
    Maybe try console logging?
    • aabhay 4y ago
      But what if the component is a recursively nested logging tool?
      • sgt 4y ago
        They might even become part of the next YC batch. A recursively nested logging platform - quite a novel idea. Possibly even possible to patent.
  • whizzter 4y ago
    iirc Chrome sometimes handles stack-overflows and/or out of memory conditions badly. If you have any function there that is called try making an entry/exit counter and log/throw if it goes above some threshold.
  • __ryan__ 4y ago
    Why not just debug on component creation? Or maybe on DOM subtree modification [0]? Or maybe modify the compiled JS to add log or trace statements? It’s all in your browser. You have a debugger at your fingertips. Why doesn’t Vue stop this from happening? Because it assumes whatever you’re telling it to do is what you want it to do. 0: https://developer.chrome.com/docs/devtools/javascript/breakpoints/#dom https://developer.chrome.com/docs/devtools/javascript/breakp...