No More Posting New Topics!

Just so everyoine knows, we recently were using node-sass (a C++ node binder) which is now deprecated. Instead, we are now using sass (javascript). The sass version does better checking (linting) and therefore, if you have errors, these will show up.

One thing I have noticed though, is if you are missing the colon (:) completely, you get a warning and it keeps on trucking (instead of failing), but it gives you a message about no descripter so won’t be used. For the line number it gives you, look up 1 higher for the issue.

I have created a feature request, see https://github.com/vue-styleguidist/vue-styleguidist/issues/1016

@ssuess That is just what I needed…thank you!

Thanks @metalsadman I tried quasar with the CLI yesterday. That’s not the road I wonna go down. Can I still use quasar as a plugin with vue3 and the vue cli? Thanks for the help!

Do any of you get a ERR_NAME_NOT_RESOLVED error when running an Android dev build after changing the host parameter? It’s working fine in my browser and on iOS …

@peppered You are actually calling the global @quasar/cli, which in turn looks for @quasar/app in your node_modules, so it can pass project-oriented work to it. The global @quasar/cli is not finding the local @quasar/app, so you are getting that message. Another reason for getting that message, when you feel it is correct, if that node_modules has not been populated yet (like when you get your code from a repo, then forget to run yarn/npm on it).

Thanks, I will ask there

thank you all problem solved successfully

$ npm link @quasar/cli

@dobbel other thread, same topic.
The cors header must be missing, otherwise the CORS Unblock extension wouldn’t solve it for me.

Could you give any insight on how to actually and specifically enable cors on the server (webpack devServer)?

@madansingh18 So when you you get this error? During build or in xcode? Can you paste some outputs of the command that gives the error like:

quasar build -m cordova -T ios --debug some ouput.. error ect...

Ok thanks.

https://github.com/quasarframework/quasar/issues/7694

@lopu

Yes that’s how nodejs app’s work with packages. Actually when using npm( yarn has a different lock file) will look at the package-lock.json for the exact version it will use:

https://stackoverflow.com/questions/44297803/what-is-the-role-of-the-package-lock-json

@Christal

https://quasar.dev/options/app-internationalization#Add-new-language

have you added a different locale?

Looks like this was fixed in quasar/app v1.7. Updated to latest and now working.

@Akayy inside q-app is already vue, it’s the same as using it within other components. you can even test that in your codepen, move it out of the q-app div, or copy paste the inline-template multiple times. i dunno what you are trying to do at this point, so yep goodluck.