CLI

• B

  This topic is deleted!
  • Blaconix  

  5
  0
  Votes
  5
  Posts
  52
  Views
• T

  [Solved] Quasar CLI Vs Vue CLI 3?
  • theara  

  3
  0
  Votes
  3
  Posts
  529
  Views

  T

  thanks for your reply
• J

  Difference in js file output in Cordova build
  cordova build webpack • • jasonl  

  4
  0
  Votes
  4
  Posts
  669
  Views

  J

  Updating Quasar to 0.17.6 solved the issue.
• D

  Using webpack without CLI
  • dnorth  

  1
  0
  Votes
  1
  Posts
  222
  Views

  No one has replied

• H

  Failed to download repo quasarframework/quasar-starter-kit
  • Humboldt155  

  4
  0
  Votes
  4
  Posts
  503
  Views

  H

  @rstoenescu It worked perfect! Thank you so much!
• D

  Missing VueLoaderPlugin after update to quasar-cli 0.17.0
  • doonoob  

  1
  0
  Votes
  1
  Posts
  408
  Views

  No one has replied

• J

  Build Issue : Blank page is displayed after build
  • jsahoo  

  2
  0
  Votes
  2
  Posts
  266
  Views

  

  If you are using Node/express as your backend, use the cors package as middleware for express. It’s because your ports are not matching. I usually use the following for my express: // Setup middlewares const bodyParser = require('body-parser') const compression = require('compression') const helmet = require('helmet') const cors = require('cors') module.exports = (app) => { app.use(compression()) app.use(bodyParser.json()) app.use(bodyParser.urlencoded({ extended: true })) app.use(helmet()) app.use(cors()) }
• M

  Quasar Dev command not watching file changes
  • MatanYad  

  2
  0
  Votes
  2
  Posts
  252
  Views

  

  Are you also using applications like GitKraken or Code? All of these set up a large amount of file watchers and you may not have enough. You can run this command to resolve that: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
• L

  Build shows error in production - Uncaught TypeError: t.__Vue is not a constructor
  • lucianoreis  

  3
  0
  Votes
  3
  Posts
  269
  Views

  

  Are you on the 0.17 beta? If so, upgrade to latest (beta.21). Otherwise, please offer more details or better yet a minimal reproduction repo. Thanks.
• 

  Serious security issues with Quasar-cli on `npm audit`
  • mesqueeb  

  1
  0
  Votes
  1
  Posts
  265
  Views

  No one has replied

• S

  How to debug Main thread of Electron Quasar App?
  • sontis  

  1
  1
  Votes
  1
  Posts
  269
  Views

  No one has replied

• M

  $quasar dev --mode cordova -T android generate app blank
  • marconi  

  6
  0
  Votes
  6
  Posts
  1021
  Views

  P

  @koohsaran70 yes, for me it was enough; the emulator is running on your local machine, so sharing the same ip. I’m sorry, I work on Linux and have no experience on Windows, but I don’t think this is the point. Btw, in the log you should check/filter for cordova errors, where a Vue stacktrace should appear. I’m out of other ideas, hope someone will chip in.
• L

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

  30
  2
  Votes
  30
  Posts
  6953
  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
  2062
  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
  308
  Views

  No one has replied

• R

  Using nginx and docker container with quasar
  • robert197  

  2
  0
  Votes
  2
  Posts
  457
  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
  • jeffatpf  

  1
  0
  Votes
  1
  Posts
  627
  Views

  No one has replied

• V

  2 security vulnerabilities in depencencies with Quasar CLI
  • VitorBrazil  

  1
  0
  Votes
  1
  Posts
  376
  Views

  No one has replied

• 

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

  1
  0
  Votes
  1
  Posts
  338
  Views

  No one has replied

• D

  linter broken after update to .15.10
  • dgk  

  7
  0
  Votes
  7
  Posts
  1038
  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.