CLI

• 

  cli needs updating to support 3rd-party NPM Quasar packages
  • Hawkeye64  

  2
  0
  Votes
  2
  Posts
  238
  Views

  

  Added an issue (Enhancement) request: https://github.com/quasarframework/quasar-cli/issues/205
• S

  cant install quasar-cli with npm or yarn
  • Salamandr  

  3
  0
  Votes
  3
  Posts
  362
  Views

  S

  can fix: npm install reinstall -g reinstall npm install -g quasar-cli
• J

  Quasar Build on Netlify
  • jonasscalar  

  2
  0
  Votes
  2
  Posts
  292
  Views

  

  You run the build locally then upload the generated dist folder to Netlify. At least that is how I’ve used Netlify before. Scott
• V

  [Solved] Small js files in dist directory. Please help me combine to one file by cli.
  • VV  

  3
  0
  Votes
  3
  Posts
  343
  Views

  V

  OK. Thank you!
• C

  Infinite Scroller Loses Reactivity when Adding New Data after Initial Loading of Data
  • carlos_proj  

  10
  0
  Votes
  10
  Posts
  568
  Views

  

  @carlos_proj You might want to check this out: https://vuejs.org/2016/02/06/common-gotchas/
• F

  upgrading quasar to latest give error in command `quasar dev`
  • Ferdrian  

  5
  0
  Votes
  5
  Posts
  647
  Views

  X

  how did u fix your issue?
• J

  Directory Doesn't Appear in Build
  • jcrosby  

  5
  0
  Votes
  5
  Posts
  363
  Views

  M

  you can debug in dev directory, and rebuild it in production. https://quasar-framework.org/guide/app-build-commands.html
• B

  Problem serving dist folder in node.js locally
  • besthost  

  6
  0
  Votes
  6
  Posts
  550
  Views

  

  Ok. At some point you’ll need to upgrade your CLI. You are on version 15 and we are now on version 17. Great you’ve solved the problem anyway. Scott
• F

  Dev mode - Delay to refresh page
  • flavioafa  

  5
  0
  Votes
  5
  Posts
  483
  Views

  E

  Hi, I’m probably having a similar issue. I’ve started a new project using Quasar (for the first time) about a month ago - everything was speedy and fine. Then one day deadlines kicked in with new tasks, I ended up updating Quasar/Cli but also implemented some new plugins like vue-i18n (I didn’t need it back then, had to do it manually). But nothing was “huge” besides i18n (which isn’t itself, I’m only guessing here). After that stage (which, unfortunately was committed very poorly, my fault) the typical recompile phase on quasar dev started to take ~12sec instead of the usual 1sec (sometimes even less) from before. I couldn’t stop to take a look on this deeper so far, but some guys at Discord helped me with some tips. Right now I’m still having that 12sec, and I’m just waiting for a free afternoon so I can deep-investigate what could be happening. My next step is giving Webpack’s Stats Data API (https://webpack.js.org/api/stats/) to output those stats and analyze them. I suggest you do the same. I’ll probably have this time to do it around today or tomorrow and will come back here with results and conclusions, if any.
• P

  SOLVED "quasar init" appears to work, "quasar dev" subsequently results in a blank page but "quasar build" works as expected (macOS, details inside, tia)
  • pete  

  5
  0
  Votes
  5
  Posts
  638
  Views

  P

  Scott, thanks again. I think I had a very broken node install and have addressed this issue through a clean install process, so thought I would just note it here with the details: Uninstalled node via https://github.com/brock/node-reinstall // but stopped the script before it began to “reinstall”, it prompts at various stages and allows one to exit after a certain point Installed nvm and selected v10.11.0 so that I end up with: λ node --version v10.11.0 λ npm --version 6.4.1 λ vue --version 3.0.3 λ quasar --version 0.17.19 λ nvm --version 0.33.11 And now I just tested quasar init with defaults + npm, and quasar dev worked fine. No more issue!
• 

  Quasar => Q ?
  • Ben Hayat  

  4
  0
  Votes
  4
  Posts
  333
  Views

  

  Go to Settings in VSCode and type in console in the search. Somewhere below is Terminal>External:Windows Exec. You’ll need to change that path to where you installed git and more specifically bin/bash.exe. (Hopefully you have installed Git for Windows) Then you can go the Git\etc\profile.d folder and edit aliases.sh. Scott
• V

  Existing VueJS quasar app adding Cordova support
  • venkyvb  

  1
  0
  Votes
  1
  Posts
  368
  Views

  No one has replied

• D

  How to change theme in dev environment?
  • Denni  

  2
  0
  Votes
  2
  Posts
  335
  Views

  

  There are only two themes: # Material Design $ quasar dev -t mat # iOS theme $ quasar dev -t ios There are, however, different targets (-T) if you are compiling for Cordova. https://quasar-framework.org/guide/quasar-cli.html
• J

  Error running on Android: webpage at ip:port could not be loaded because net::ERR_ADDRESS_UNREACHABLE.
  • jcrosby  

  9
  0
  Votes
  9
  Posts
  668
  Views

  M

  your mobile phone should also be on the same network as your dev computer, also check the firewall of your dev computer.
• 

  Problem android development
  • wahono  

  3
  0
  Votes
  3
  Posts
  349
  Views

  

  This occurs with me too
• D

  Environment variables
  • danikane  

  7
  0
  Votes
  7
  Posts
  4625
  Views

  D

  Hi Scott, I won’t store them there of course, I was using .env for other projects and I just wanted to have some consistency. Thanks for the article, that really helps with the extendWebpack approach! Dan
• 

  Upgrade from 0.17.16 to 0.17.17
  • Luiz  

  2
  0
  Votes
  2
  Posts
  281
  Views

  

  Hi. I remove node_modules, yarn.lock and yarn add -dev quasar-clil@test and the new version is running. Tanks.
• B

  Location of generated webpack config
  • boyd  

  1
  2
  Votes
  1
  Posts
  248
  Views

  No one has replied

• M

  How to add path alias?
  build qusar-cli linux bitbucket pipelines • • morlz  

  4
  0
  Votes
  4
  Posts
  542
  Views

  G

  Maybe try resolve or path.resolve? extendWebpack (cfg) { cfg.resolve.alias = { ...cfg.resolve.alias, // Add your own alias like this 'vue$': 'vue/dist/vue.esm.js', '@': resolve('src') } or… extendWebpack (cfg) { cfg.resolve.alias = { ...cfg.resolve.alias, // Add your own alias like this 'vue$': 'vue/dist/vue.esm.js', '@': path.resolve('src') }
• A

  How to add MathQuill
  • alfredclyim  

  3
  0
  Votes
  3
  Posts
  611
  Views

  G

  JQuery plugin - yuk… but if you must. I haven’t actually tried this because I do not want to pollute any of my projects and I do not have a ton of time to invest in it. First it seems like you would need to npm (or yarn) install JQuery and add JQuery via a Quasar plugin. Not sure how MathQuill expects it, but something along the lines of: // Quasar plugin jquery.js import jQuery from 'jquery' window.$ = window.jQuery = jQuery Then the same for MathQuill - npm install and Quasar plugin (you’ll have to look into the node_modules folder for where exactly the css is located and maybe use min version if provided. Also don’t forget to add the plugins to quasar.conf.js): // Quasar plugin mathquill.js import '../../node_modules/mathquill/PATH_TO_CSS/mathquill.css' import MathQuill from 'mathquill' export default ({ Vue }) => { Object.defineProperty(Vue.prototype, '$mq', { value: MathQuill.getInterface(2)); } Then in any Vue component, you should be able to access it as this.$mq. As I said, I haven’t actually tried it and you may have some trial and error to get it working, but hopefully this helps get you going in the right direction. If you cannot get this working, you can try it with MathQuill on the window like the JQuery above, but the many JS gods frown on window variables. In this case though I think JQuery will have to be there for MathQuill to see it.