Daniel Schäfer

If it was my lib then I'd replace the `filename` with `path` and simply bump to a new major version to signal breaking API changes. Because having both `path` AND...

Thank you!! Works like a charm 👏 😃

So what you're basically saying is, that the `@import '~@/assets/styles/...'` is not working?

Ah, no, the imports are working, but the files don't see the vars from the `sass-vars-loader`, right?

Basically what the `sass-vars-loader` is doing, is converting this: ``` @import '~@/assets/styles/vars'; @import '~@/assets/styles/util'; @import '~@/assets/styles/func'; @import '~@/assets/styles/mixins'; @import '~@/assets/styles/colors'; ``` to this: ``` $var1=value1 $var2=value2 ... @import '~@/assets/styles/vars'; @import...

I'm not really familiar with the chainWebpack method. Could it be that the `css` command is actually overwriting the results from `sass-vars-loader`?

What about putting the @imports in a .sass file and load it as part of the `sass-vars-loader`? ``` const path = require('path'); module.exports = { chainWebpack: (config) => { const...

Hm, this would actually not work, since the sass files always come first. That's a stupid design! 🙈 😆  I could change that. It's...

@dschox unfortunately I'm really busy lately and won't have the time to work on this currently. But I'm happy to merge any incoming PR :)

> Is it possible you can do this this year? ;) oh yeah, absolutely 👍