CLI

• 

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

  4
  0
  Votes
  4
  Posts
  1365
  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
  431
  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
  460
  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
  168
  Views

  No one has replied

• L

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

  2
  0
  Votes
  2
  Posts
  300
  Views

  L

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

  How to run lint --fix command
  • hbothra15  

  5
  0
  Votes
  5
  Posts
  1520
  Views

  H

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

  Build for production
  • sergevdz  

  2
  1
  Votes
  2
  Posts
  493
  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
  859
  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
  1386
  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
• 

  Removing babel
  • labs20  

  1
  0
  Votes
  1
  Posts
  270
  Views

  No one has replied

• A

  Can't create a new store with quasar
  • ael  

  6
  0
  Votes
  6
  Posts
  389
  Views

  

  Figured it was something like that.
• 

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

  2
  0
  Votes
  2
  Posts
  252
  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
  645
  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
  324
  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
  367
  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
  651
  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
  659
  Views

  X

  how did u fix your issue?
• J

  Directory Doesn't Appear in Build
  • jcrosby  

  5
  0
  Votes
  5
  Posts
  382
  Views

  

  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
  679
  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
  495
  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.