Currently, I am in the process of debugging a Nuxt + Vue.js application and I find myself needing to examine the description of an object that is being passed to one of my components' methods. Additionally, I desire to step through this method to identify any issues present within it.
While utilizing WebStorm for this task, I came across some helpful information on how to work with Vue.js in WebStorm from this source.
https://i.sstatic.net/aiMGi.png
Following the instructions provided above, I proceeded to run "npm run dev" and then initiated the debug mode in WebStorm. Although the page successfully loaded in Chrome, I faced an issue where my set breakpoints were not being triggered.
Despite this setback, I am aware that my method is being executed as I can observe its flawed results within my Vue app running in Chrome.
In attempting to rectify this problem, I also experimented with using the Vue Devtools extension in Chrome; however, while it proved to be useful, it did not offer the specific step-through functionality that I am seeking.
Outlined below is the configuration of my Javascript debugger:
https://i.sstatic.net/Sxhy1.png
I have begun to wonder if the loading order of a Vue project in the browser could be contributing to this issue. As someone who is relatively new to Vue.js, any assistance or insights would be greatly appreciated.