User Profile

I created a new Vue.js project with the latest vue-cli. After that I served that template project through webpack. Without any modifications, the source maps to the two components (App.vue and HelloWorld.vue) appear fine in Chrome and Firefox. They are located at webpack:///HelloWorld.vue?140d webpack:///App.vue?234e These source maps show up fine in Chrome and Firefox at their respective position, but are missing in Safari. Safari for some reason only shows files that are in some subfolder under webpack://. The source maps in these subfolders are available but they are next to useless, since they are not the original source. Those exist in the root. For example, webpack:///./src/components/HelloWorld.vue?f177 does show up.

Hello Everyone!I bumped into the following problem.The current implementation of disabling cache (via the network tab) does disable cache for almost everything, except for JavaScript files.As you know, most front-end frameworks use virtual DOMs (Vue.JS, React), and they basically store all info in JavaScript objects.It's a giant pain in the bottom that I have to manually empty the cache every time I modify the code to see the served results. This is the number one reason why I would need to turn off the cache, yet it affects everything except the only file where it actually matters.