No More Posting New Topics!

Maybe a problem of timezone and how dates are stored in thé database.

Thank you, friend, it worked out right here.

I have already updated the project as well, for the latest version of Quasar. Is that I was afraid to upgrade, because when I updated from 0.14. * To 0.15.2, my project was totally different, had to program again a 4 pages I had already done. I think that happened because it changed a lot from one version to another.

Well, I’m loving programming with Quasar, an exceptionally wonderful framework.

Regards,

André Peil Müller, Brazil.

same problem for me.
It seems that we can’t set a publicPath during development

There is no v18. So wich version do you use?
In the v0.15.x it asks you if you want to add ESLint. If you want to use it and choose no during initalization, just initialize a new project and compare

Didn’t need a plugin or any changes to babel.
Turns out for babel one either needs to use fat arrow syntax or bind/ autobind the functions to this

connect = async () => {

Inspecting this in more depth, and being a bit more open-minded I can understand that this is maybe a feature.
Looking at the bundles on more detail I can see that they are not of the same exact size, and if you look closer you can see that they do not include the same files. Being each bundle a different route maybe this makes sense. Each route has just the files they need. Because we don’t know how routes will be loaded (which order)because can navigate to any random one we have to include all the possible files they may require.

My only complain may be that some files are present both at the vendor bundle and the route bundle. Since the vendor bundle is loaded on every route, I don’t see why those files needs to be included on the route bundle too.

In any case, this is just an unnecessary optimization concern, since page loading is already very fast.

Ah sorry for misinterpreting your question, you are right the available alias are defined in that file. 😃

Hey, have you tried to edit the buildPath variable in config/index.js?
With this config you should be able to set your path correctly.

so what dependencies does the cli manage? Vue obviously, what else? Is there a way to list them and their version number?

Normally I’d upgrade my dependencies as I see fit…so now upgrading any of these can only be done when the cli upgrades?

You can make simple installer that is a self extracting archive, that just copies the files to the desired location. Anyways this falls out of the scope of quasar, and is a simply an electron issue

You can always clone the template folder of the template and use that. Npm install might still be an issue

I ran into the same issue, posted a bug report at: https://github.com/quasarframework/quasar-template-default/issues/47

Under the hood, “quasar dev” ends up calling “npm run dev”. It’s safe if you want to simply run “npm run dev” or “npm run build”.
Quasar CLI on the other hand does some extra work, checking if dev port is available (just to name one of those extra things).