I’d suggest migrating your app to Quasar. I’m not sure what will work within Nuxt and as long as you are working within Nuxt, you won’t get support here worthwhile. There will always be the Nuxt cloud hanging over your head.

Scott

Thanks for the nice words @pg !!! - and with Vue 3.0. The argument about TypeScript and large teams will also be part of Vue’s (and Quasar’s) sales pitch. In fact, currently an app extension for Quasar is being worked on, so devs can add TypeScript support. But, until the cores of Vue and Quasar are built with TypeScript, the app extension is temporary help.

Scott

Override the stylus variable $tooltip-color in the /css/quasar.variables.styl file.

https://v1.quasar-framework.org/style/stylus-variables

Scott

Basically upgrading the Quasar dependencies of the project (the devland app) will also upgrade the CLI at the same time. That way, changes that occur to the core software, which also need the Node code improvements in the CLI, will get them automatically. Without this setup, devland would constantly need to update the global CLI too. This change in v1.0 reduces once more developer effort.

@quasar/app holds things like extension addition and removal commands, describe for the API, inspect, mode, etc. You’ll notice with the CLI, that if you are in a project directory, you get a lot more commands. If you are outside a project, you only get help, info and create.

Did that make any sense?

Scott

You can try that, but you can and probably should just use the slot available for QTd. Sorry, I should have asked earlier, but which version are you using?

Scott

Can you explain your problem in a bit more detail please?

Scott

Are you using v1.0? If yes, you can use the prepend slot of QInput and basically design that area as you’d like.

Scott

.q-textarea .q-field__native {
  font-size: 24px;
}

Change the font size to whatever you’d like.
Scott

Quasar’s “-t” option for the “dev” command in 0.17 was for switching between the two available themes. Material or iOS. It wasn’t built to offer a blank theme to customize with. The component system offers the customization for theming, by overriding the “styles” given.

In fact v1.0, the “-t” option is no longer available, since v1.0 only supports a Material theme, which is also customizable over the component system.

Scott

Can you explain your use case some to understand your need for asynchronous confirmation or cancellation of qdialog? And not even knowing your use case, could you build a custom dialog component for whatever async dialog needs you have?

Scott