Thorsten Lünborg
Thorsten Lünborg
We experienced this as well upstream in the webpack template, back when when we upgraded to webpack 3. It turned out that it was related to the html-webpack-template and this...
No. Also I don't see how this could influence styling.
https://github.com/webpack-contrib/sass-loader#imports You have to use a tilde to make sass-loader interpret the path as a node module: ``` @import "~@material/theme/mdc-theme" ``` then you don't need any includePaths.
Alright, thanks for the info.
> The main issue I have with this, is that I need all those fields in my state, whereas previously I didn't, because I could just use the refs. @TheDutchCoder...
Would it be ok to rename the issue to something like: "$refs should be reactive to be able to use them in computed properties"?
Well, that use case would not even work if `$refs` was reactive, because no refs changed in any way, and neither did their data, only the DOM changed.
Can't recall if the focus event bubbles, but if it does, register an event listener in `created()` and save the target element in the component's data? That would be reactive,...
On second thought that could lead to unnecessary rerenders.
We currently focus all our efforts on bringing Vue 3 and its supor libs into RC stage. Please understand that we currently have less bandwidth for Vue 2, and improvements...