Instead of relying on console.log, I want to start using the Chrome Developer Debug Tool more frequently. I recently came across a helpful article about debugging in general (such as setting breakpoints and executing line by line) here.
However, when attempting to apply this knowledge in a real-life scenario - specifically within a vue (nuxt) application that I am currently working on - I encountered difficulties.
All my files are merged into complex javascript files, making it challenging for me to debug them.
I then stumbled upon another article: Debugging .vue component in Chrome. Although I hoped it would provide some clarity, I still feel lost.
In an attempt to resolve this issue, I added the following code snippet to my nuxt.config.js:
configureWebpack: {
devtool: 'source-map'
},
Despite this, I could not locate any sourcemaps for my .js files in the debugger. It would be beneficial if I could easily access all js files related to each vue component, store file, and other utility scripts that I have created. While unsure if this is achievable, I believe there must be a way to identify and debug my Javascript code effectively within the debugger tool. Is this assumption incorrect?