No More Posting New Topics!

@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.

How did you install Quasar CLI? Can you post what output you get, when you run quasar info ?

Scott

@chlembi Error found. I had already created a Project on some folder levels above by mistake. After I deleted the files it worked. Thanks for the hint.

Okay, now I found out that this is the very reason why you should install Node.js and NPM via NVM. I have no idea what NVM really is, but this worked:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash

And after relaunch of Terminal:

nvm install stable npm install -g @quasar/cli

So I think those are the steps that you should have in your instructions instead of just

npm install -g @quasar/cli

Maybe this will help:

https://github.com/quasarframework/quasar-starter-kit-umd

Sorted it. this is how to generate icon and splash screen using two different files:

icongenie generate -i app-icon.png -b app-splashscreen.png --splashscreen-icon-ratio=0

@metalsadman You’re right. I’m losing track of what’s what anymore.

importStrategy: “all” is a temp work around to get your source maps working for dev; we’re not suggesting you release a production app with it. Wait for the update next week for that 🙂

I’m not sure what you mean about “restore the template”, however, the fix is in place and will stand as it’s the correct fix for this issue. If there is something else that needs changing please file a feature request on GH issues with a detailed explanation of what and why.

running quasar create inside the target folder seemed to work

Here is my routes.js file:

const routes = [ { path: '/', component: () => import('layouts/MainLayout.vue'), children: [ { path: '', component: () => import('pages/Index.vue') }, { path: '/hosts', component: () => import('pages/Hosts.vue') }, { path: '/privacy', component: () => import('pages/Privacy.vue') }, { path: '/terms', component: () => import('pages/Terms.vue') }, { path: '/contact', component: () => import('pages/Contact.vue') }, { path: '/livestream', component: () => import('pages/Livestream.vue') }, { path: '/youtube', component: () => import('pages/YouTube.vue') }, { path: '/book', component: () => import('pages/Book.vue') }, { path: '/zoom', component: () => import('pages/Zoom.vue') }, { path: '/grass', component: () => import('pages/TheGrassIsGreener.vue') }, { path: '/loatoday', component: () => import('pages/LOAToday.vue') } ] } ] // Always leave this as last one routes.push({ path: '*', component: () => import('pages/Error404.vue') }) export default routes

@s-molinari said in Quasar + Vagrant:

And now that WSL2 is out, there are no reasons left to stick with Vagrant on Windows 10. 🙂

oh, good days of Vagrant, I remember running 38 vms with three separate networks, dmz, bunch of software server clusters (db, web, app, queue, mail, search etc.). And all of that on a single developer machine. It felt like a magic 🙂 Till the deployment, which was hell mixed with nightmare.

Now everything is just simpler, and with Quasar clean architecture most of those ancient tasks are non-existent. Build, deploy, sync configuration, voila.

hot reload/rebuild works out of the box in v1.x if you run Quasar in dev mode.

@DarkLite1 did you managed?

I’d say you have one too many “<” (opening tags) in your code some where.

Scott

@Christal like what @s-molinari said, also be sure your quasar version is v1.12.0 or above.