CLI

• A

  0.15.4 build how to specify app directory
  • Alinex

  2
  0
  Votes
  2
  Posts
  801
  Views

  A

  Found it at http://quasar-framework.org/guide/app-quasar.conf.js.html#Build-Property I have to use publicPath.
• L

  vue-cli 3.0 and the future of quasar-cli
  • lbssousa

  30
  2
  Votes
  30
  Posts
  2765
  Views

  

  I’m going full PWA so I do not need Electron nor Cordova. I use vue-cli 3 with a customized Quasar UMD build (removed unneeded components and css with a bit of metaprogramming) and with a custom script at startup I can dynamically load different themes depending on the platform. The more I use vue-cli the more I think quasar-cli is amazing because it really hides a lot of complexity from developers.
• 

  template lang="pug" does not compile after update 0.15.1 -> 0.16.4
  • dan-leech

  10
  0
  Votes
  10
  Posts
  173
  Views

  

  @nothingismagick thank you very much. I don’t know what exactly helped but after following all steps carefully all work now. https://quasar-framework.org/guide/app-pre-processors-and-webpack.html#Pug
• E

  Electron-builder publish 0.16.4
  • Emptyless

  1
  0
  Votes
  1
  Posts
  82
  Views

  No one has replied

• R

  Using nginx and docker container with quasar
  • robert197

  2
  0
  Votes
  2
  Posts
  81
  Views

  

  @robert197 - if you send me a link to your dockerfile via PM then I will take a look at it.
• J

  Tapable.plugin is depricated - v0.16
  • jeffatef

  1
  0
  Votes
  1
  Posts
  204
  Views

  No one has replied

• V

  2 security vulnerabilities in depencencies with Quasar CLI
  • VitorBrazil

  1
  0
  Votes
  1
  Posts
  126
  Views

  No one has replied

• 

  Compilation fails after creating new project with ESLint and Airbnb standard
  • rggibson

  1
  0
  Votes
  1
  Posts
  108
  Views

  No one has replied

• D

  linter broken after update to .15.10
  • dgk

  7
  0
  Votes
  7
  Posts
  405
  Views

  D

  After making a new project with 15.14 cli I still see the vue plugin and it looks like my upgraded project is now consistent with this. So all is good and it does seem that @rstoenescu is still using the vue plugin which makes sense since it was supposed to replace the older html plugin for vue files and there must be something to help estlint with vue files. So bottom line the html plugin is deprecated and one should remove it from dev-dependencies and .eslintrc. As to atom make sure the linter-eslint settings now turn off the html plugin option and that the scopes include text.html.vue BTW my quasar.config.js build was fine, identical to above.
• B

  How to chang the default source code path from `/src` to something else?
  • beeplin

  2
  0
  Votes
  2
  Posts
  211
  Views

  B

  I found in quasar-cli/lib/build/app-path.js: const appDir = getAppDir(), cliDir = resolve(__dirname, '../..'), srcDir = resolve(appDir, 'src'), pwaDir = resolve(appDir, 'src-pwa'), cordovaDir = resolve(appDir, 'src-cordova'), electronDir = resolve(appDir, 'src-electron') Does this mean the src path cannot be changed?
• B

  Nodejs.exe using 100% CPU on Windows 8.1 after running '> quasar dev' or '> quasar info'
  • bmnds

  2
  1
  Votes
  2
  Posts
  301
  Views

  

  Hi there, The project you cloned runs on an older version of Quasar, maybe the problem lies there? Try to create a new project with the latest version and see if the command line still hangs forever: http://quasar-framework.org/guide/index.html Good luck!
• E

  Missing qusar.conf.js file
  • eugenemaning

  6
  0
  Votes
  6
  Posts
  472
  Views

  S

  I just freshly installed quasar, and initiated an app. I don’t see quasar.conf.js anywhere
• 

  PWAs: now on iOS 11.3
  • LaurentPayot

  1
  0
  Votes
  1
  Posts
  283
  Views

  No one has replied

• S

  This topic is deleted!
  • simshaun

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• A

  Erro ao exibir data cadastrada (Datetime)
  • AndreeeMuller

  2
  0
  Votes
  2
  Posts
  210
  Views

  C

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

  How to install a specific version of quasar-cli? (0.15.2)
  • AndreeeMuller

  3
  0
  Votes
  3
  Posts
  383
  Views

  A

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

  Environment variables
  • danikane

  4
  0
  Votes
  4
  Posts
  874
  Views

  D

  ok I think I get it. ctx.dev is true for quasar dev so this was my build:env env: ctx.dev ? { // so on dev we'll have WSS: JSON.stringify(process.env.WSS) } : { // and on build (production): WSS: JSON.stringify(process.env.WSS) },
• S

  publicPath proprety not working in devServer
  • stansab

  2
  0
  Votes
  2
  Posts
  262
  Views

  C

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

  ESlint not working
  • donvie

  2
  0
  Votes
  2
  Posts
  319
  Views

  

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

  Missing class methods.....Adding a babel plugin for ES6 Classes ( using 0.15)
  • dgk

  3
  0
  Votes
  3
  Posts
  284
  Views

  D

  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 () => {