You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source maps for Vue TodoMVC are using the full path instead of the relative path, causing fake file changes every time a new person builds it. E.g:
"\n\nimport exportComponent from \"/Users/thorstenk/Desktop/FlashDesignory/Speedometer/resources/todomvc/architecture-examples/vue/node_modules/vue-loader/dist/exportHelper.js\"\n
to
"\n\nimport exportComponent from \"/home/issackjohn/issack/Speedometer/resources/todomvc/architecture-examples/vue/node_modules/vue-loader/dist/exportHelper.js\"\n
One can see the webpack config used by vue like this:
./node_modules/.bin/vue-cli-service inspect --mode production 2>&1| less
Here we clearly see that the absolute directory is used everywhere. I'm not sure which of these impacts the source map generation.
Clearly in my other non-vue webpack-based project this isn't happening.
The source maps for Vue TodoMVC are using the full path instead of the relative path, causing fake file changes every time a new person builds it. E.g:
"\n\nimport exportComponent from \"/Users/thorstenk/Desktop/FlashDesignory/Speedometer/resources/todomvc/architecture-examples/vue/node_modules/vue-loader/dist/exportHelper.js\"\n
to
"\n\nimport exportComponent from \"/home/issackjohn/issack/Speedometer/resources/todomvc/architecture-examples/vue/node_modules/vue-loader/dist/exportHelper.js\"\n
in #376.
The text was updated successfully, but these errors were encountered: