Or you could do @import '~src/themes/app.variables.styl' which goes up to the root and searches down. This way if you change your file`s position later on, you wont have to worry compared to when using “…/…/…/” syntax.

You should give an example how you achieved this, for future people searching of a similar issue

Ok. Just wanted to give a helping hand

As @rstoenescu said you can’t use Stylus variables inside you SASS, however, if you are not importing any specific css framework/tool you could use Stylus. For the most part its similar to SCSS, you can still use braces and what not, I for once use them, as without them my code gets freaky and looks messy to me
Having a separate _variables.scss is possible, but you have to manage it by your self

that is fine, it works fine with any vue 2.x version. I had an old CLI version along with the new one I just had installed. Going to try to do things now

Pretty much i was thinking of the same thing. vue-router-vuex sync could be used for this, to know on which route I am and stuff.

I think its in the future plans, currently they are pretty tightly coupled to the framework.

Its because the parent is set to have a align-items:stretch which stretches all the elements so they have the same position. You have to do a align-items:center or use the items-center class on the parent.

Use a slider component with your content in each slide. Then you can watch the @slide event emitted from the slider and change the tabs above. Problem is that you have to have a prop for the tab nav and the currentSlide in the slider and sync them altogether which can be a pain.
Currently the tabs component doesn’t support this out of the box. You can file an issue on github and who ever has time to do this first will try to do a PR.

A fix has been merged. Please update your Quasar CLI.

@reath I have made a PR to quasar cli that will fix the problem. Waiting on approval. Until then, tell me if the workaround above worked.

PR for reference - https://github.com/quasarframework/quasar-cli/pull/198

OK, I was wrong. This is a Quasar CLI issue, rather then an issue with my plugin. Will make a PR to Quasar, see if it gets merged. Essentially you could try the not ESM build, so instead of what you had do this - import VuelidateErrorExtractor from 'vuelidate-error-extractor/dist/vuelidate-error-extractor'

Problem comes from the fact. that there is a package, that uses an older version of a dependency the error extractor has. Because I do not bundle the deps in the ES module build, this happens. A properly configured webpack config should fix this

Found the issue. For some reason the bundled package for accessing deep object properties was returning undefined. Will fix it now and push a release.

that is fine, it works fine with any vue 2.x version. I had an old CLI version along with the new one I just had installed. Going to try to do things now

For some reason, Quasar is not loading my quasar.conf.js at all… I cannot setup the plugins.

I will look into it today. Didnt get notified for the reply. …

@reath From what I am seeing in the codesandbox you attached, it all works. Is there an issue with Quasal when using its CLI?

Ok. Just wanted to give a helping hand

Hey. Are there any plans to make the progressive loading buttons closer to the native ones, material having those round spinner etc. If not, do you need any help with that?
Also, and this is just an idea, could we at some point, have a start, done, error methods on the intermediate so it can go back to its default state after X amount of time? I know I could run a timeout on my “progress” prop and set it to 0, but it can get a pain, I would have to extend the quasar button with my own button to not write it everytime.
On a side project of mine I implemented pretty much the same because I couldn’t use quasar there and it is really useful for Ajax calls and what not.