CLI

• D

  Creating custom app templates for quasar-cli
  • dsl101  

  11
  0
  Votes
  11
  Posts
  3145
  Views

  I

  @mesqueeb i have the same problem. I need use my private repository, but i don’t know how
• S

  Running cli 0.17 and 1.xx on the same machine
  • sebastien.roul  

  3
  0
  Votes
  3
  Posts
  199
  Views

  

  In my project, I was only able to instal Quasar CLI 1.0 using yarn (I was using npm, but it doesn’t work) My Quasar 0.17 project just run after I updated the packages using yarn, even with no changes in the project, maybe something related to the newly installed packages… After updating the packages of older projects, I am able to run Quasar CLI 0.17 and 1.0
• K

  Is it possible to change the env variable in quasar build command
  • kartikpuri95  

  2
  0
  Votes
  2
  Posts
  157
  Views

  

  If you are using Quasar v1-beta, you can use the dotenv app extension: https://github.com/quasarframework/app-extension-dotenv
• C

  Always show x-scroll bar on <q-table> even when the amount of rows goes beyond visible page
  • carlos_proj  

  7
  0
  Votes
  7
  Posts
  1161
  Views

  B

  You can try with .q-table-middle { max-width: 100%; max-height: 600px; }
• 

  Error with router path (sourceFiles) in quasar.conf.js
  cli quasar-cli router quasar.conf.js sourcefiles • • D0KT0P  

  1
  0
  Votes
  1
  Posts
  101
  Views

  No one has replied

• A

  How to Disable Stylus
  • andrewl94  

  8
  0
  Votes
  8
  Posts
  509
  Views

  

  Can you give a concrete example? Scott
• S

  [SUGGESTION] Please show me what command I used to start the dev server
  • steward  

  2
  0
  Votes
  2
  Posts
  155
  Views

  

  Um, I hope you don’t take this wrongly, but you know what base command you used, or rather you know what you started, i.e. the dev server. So, that is simple enough to remember. quasar dev. Right? And once the compilation process is finished and the dev server starts, it shows you “Dev mode… spa” and “Quasar theme… ios”. It also shows you the URL and port the server is serving on. Those are the only args you could have added. So, as I see it, everything is there to tell you what you had entered. And yes, once you get out of the running dev server (with ctrl + c) and do something else, you can get the command history with the arrow up, which I do just for being lazy’s sake. And if you are starting with a fresh console and didn’t happen to have a history persistence of some sort or just starting, you can type in quasar dev -hand get help on the command, to remember what it was you wanted to do. Scott
• M

  How to add "vue-echarts-v3" in Quasar CLI
  • minko  

  2
  0
  Votes
  2
  Posts
  279
  Views

  M

  Resolved - а spelling error for “componets” instead of “components”
• 

  @quasar/testing with Jest does not print location of failed tests (stack trace)
  test jest • • Jezzta667  

  5
  1
  Votes
  5
  Posts
  209
  Views

  

  @nothingismagick You guys are doing such an awesome job addressing all the issues cropping up. I can imagine you’re working your butts off. It’s very much appreciated.
• 

  @quasar/testing appears to be broken
  • Jezzta667  

  12
  0
  Votes
  12
  Posts
  588
  Views

  

  @Jezzta667 - and then suddenly the fix stopped working. I am not sure what is going on, but my hunch is that the NPM servers are being flaky. I have refactored the transform to match the suggested approach, but left your solution “commented out”. For the time being this is the best I can do.
• S

  Is "quasar new plugin" deprecated in 1.0 beta?
  quasar-cli beta plugin • • Svoboda  

  4
  0
  Votes
  4
  Posts
  562
  Views

  S

  @rstoenescu Thank you. I was unable to find that myself.
• 

  console.log() not allowed in Jest tests
  test jest eslint • • Jezzta667  

  4
  0
  Votes
  4
  Posts
  1552
  Views

  

  @nothingismagick thank you for your help. I suspect I must have had case-matching turned on during the search for that line of code, so apologies for the silly question. I would be happy to forego console.log() and begin using the Chrome debugger but I have been unable to get this to work with Quasar. I have tried the following: Add debugger statement to the test code Run the tests using yarn test:unit:debug Navigate to ‘chrome://inspect’ Click on the ‘inspect’ link for Remote Target: jest file:/// New Chrome window opens with: Uncaught Error: Cannot find module '<my-project-folder>\jest' A guide to accessing debugging would be a great addition to the Quasar Testing documentation.
• R

  Missing files in src-cordova/www
  cordova build quasar-cli ios • • rtengent  

  2
  0
  Votes
  2
  Posts
  466
  Views

  R

  I solved this problem! I was specifying this in quasar.conf.js to fix some routing issues that I was seeing when running “quasar dev” : extendWebpack(cfg) { cfg.output = { publicPath: "/", }; } cfg.output was not set when running “quasar dev” but it is set when running “quasar build -m cordova -T ios” and so I was inadvertently overwriting it. Changing it to this let me get further: extendWebpack(cfg) { if (!cfg.output) { cfg.output = { publicPath: "/", }; } }
• N

  Fresh install of quasar CLI and quasar dev won't work
  • nbshepherd  

  4
  0
  Votes
  4
  Posts
  490
  Views

  M

  @nbshepherd good question. First, sorry for my english. Package Manager configuration is about Webpack, so to achieve what you want, I think you could change this line in node_modules/webpack/bin/webpack.js: OR, as you can see, adding a “yarn.lock” file in to your project root directory. I didn’t try do that. Please, let me know if works.
• S

  Building Android and Iphone Apps with Quasar - Icons issue; cli issue; etc
  • syshex  

  1
  0
  Votes
  1
  Posts
  173
  Views

  No one has replied

• L

  How to config enabled sourcemap for debug in quasar.conf.js?
  • layola  

  2
  0
  Votes
  2
  Posts
  317
  Views

  L

  oh, I found in chrome sources tap, //webapck foldrder
• H

  How to run lint --fix command
  • hbothra15  

  5
  0
  Votes
  5
  Posts
  1701
  Views

  H

  Got it resolved by executing npm run lint – --fix
• S

  Build for production
  • sergevdz  

  2
  1
  Votes
  2
  Posts
  506
  Views

  

  @sergevdz - https://quasar-framework.org/guide/app-quasar.conf.js.html#Example-setting-env-for-dev-build Scott
• T

  Moving to Quasar
  • tolun  

  9
  0
  Votes
  9
  Posts
  888
  Views

  

  Oh, then you’re really going to like V1.0. Scott
• D

  .15.x dependency error building after simple init
  • dgk  

  6
  0
  Votes
  6
  Posts
  1421
  Views

  

  I had the same problem. For me, the error was node enviroment set to “production”. Setting to “development” and running “npm install” make it work