CLI

• J

  This command must be executed inside a Quasar v1+ project folder
  • jicx  

  4
  0
  Votes
  4
  Posts
  12
  Views

  

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

  This topic is deleted!
  • Abdullah Sohail  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• W

  Getting a weird error in icongenie on Linux
  • walfin  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• P

  Quasar create error
  • Pepper  

  6
  0
  Votes
  6
  Posts
  43
  Views

  C

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

  Questions and errors while following CLI installation instructions
  • johanna  

  2
  0
  Votes
  2
  Posts
  12
  Views

  J

  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
• C

  How does UMD work in a php project
  • Christal  

  3
  0
  Votes
  3
  Posts
  22
  Views

  

  Maybe this will help: https://github.com/quasarframework/quasar-starter-kit-umd
• O

  Quasar Icongenie - how to generate splashscreen and icons from separate files like it worked in v1?
  • OlekssiR  

  2
  0
  Votes
  2
  Posts
  20
  Views

  O

  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
• K

  Is it necessary to update CLI V2
  • kishore sakthi  

  6
  0
  Votes
  6
  Posts
  36
  Views

  

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

  Sourcemaps not generated after Quasar update anymore
  • RolandCsibrei  

  12
  0
  Votes
  12
  Posts
  81
  Views

  

  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.
• K

  Unable to create a project - events.js error
  • kolaval  

  2
  0
  Votes
  2
  Posts
  13
  Views

  K

  running quasar create inside the target folder seemed to work
• C

  Clear vuex state in multiple tab of same browser
  • Christal  

  1
  0
  Votes
  1
  Posts
  10
  Views

  No one has replied

• O

  First App Won't Build In Electron Properly
  • omgwalt  

  2
  0
  Votes
  2
  Posts
  8
  Views

  O

  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
• C

  Quasar + Vagrant
  • CodeKiddo  

  11
  0
  Votes
  11
  Posts
  222
  Views

  

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

  Watch mode for v1.x.x
  • ivinnic  

  2
  0
  Votes
  2
  Posts
  15
  Views

  

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

  Environment variables
  • danikane  

  16
  0
  Votes
  16
  Posts
  8065
  Views

  L

  @DarkLite1 did you managed?
• C

  Restructure folders during build without express
  • Christal  

  1
  0
  Votes
  1
  Posts
  14
  Views

  No one has replied

• C

  quasar build error on browser
  • Christal  

  2
  0
  Votes
  2
  Posts
  14
  Views

  

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

  hide-pagination is not working
  • Christal  

  3
  0
  Votes
  3
  Posts
  16
  Views

  

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

  How to use vue-google-adsense in quasar?
  adsense vue-google-adse • • aaronsmith  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• O

  How to pause player in component in another instance of the component
  • omgwalt  

  6
  0
  Votes
  6
  Posts
  21
  Views

  J

  Nop, you access through a component’s method. This is the basic use-case. In a template, it’s like writing : <template> <div ref="one">test</div> <div>{{$refs.one.$el.html}}</div> </template> in computed, it’s all that belongs to your component computed() property export default { name: "MyComponent", computed () { test () { console.log(this.$refs.one.$el.html) } } }