CLI

• A

  0.15.4 build how to specify app directory
  • Alinex  

  2
  1
  Votes
  2
  Posts
  2274
  Views

  A

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

  Error on `quasar build --mode electron --target win32`
  • stevendesu  

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• M

  Error on quasar dev -m capacitor -T ios, always the same error with image
  ios capacitor • • Matheus Ryuki  

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• W

  Running cordova Android dev without a server
  • walfin  

  10
  0
  Votes
  10
  Posts
  90
  Views

  W

  I have found a temporary workaround. My solution is to build with quasar build -m android --debug and add devtool:!ctx.dev&&!ctx.debug?’’:‘eval-source-map’ under build in quasar.conf.js and also to disable my use of webpack-obfuscator if !ctx.dev&&!ctx.debug. Thereafter I run cordova run android from src-cordova. However, a special flag for this use case would still be nice.
• S

  Auto Import does not register QRating
  • Sacrekin  

  2
  0
  Votes
  2
  Posts
  23
  Views

  S

  Actually, all the new components I have added to my project do fail, and this since I decided to use the all: ‘auto’ import option. The previous list of components that I had listed in config still work, although I did remove them from config.
• G

  Run only the hot module replacement
  • GonzaH  

  2
  0
  Votes
  2
  Posts
  104
  Views

  D

  I am not sure if that’ll work for you, even though this topic is 6 months old: https://forum.quasar-framework.org/topic/4828/quasar-build-times-hrm-and-local-cache
• D

  "Quasar build" times, HRM and local cache.
  • Diamon  

  2
  0
  Votes
  2
  Posts
  15
  Views

  D

  Apparently I found writeToDisk flag in devServer webpack config file - and if you set that too true - you can still include your compiled app as a simple script, but HMR will work even on that page with included script even though there is a development server running in parallel! so in quasar.conf.js devServer { writeToDisk: true }
• J

  App:dev-server now taking 45+ seconds and slow hot-reload
  • jcvlds  

  2
  0
  Votes
  2
  Posts
  16
  Views

  J

  Turns out the compiling and building was actually being very fast still … the issue that was causing the app to open up on browser was that there was a ton of ESLint warnings from different pages/components. I disabled ESLint for now and the compile time + open on browser load time is now very fast once again
• S

  Webpack: multiple modules with names that only differ in casing.
  • Sacrekin  

  2
  0
  Votes
  2
  Posts
  23
  Views

  S

  SOLUTION: found on StackOverflow: This is usually a result of a minuscule typo. For instance, if you are importing your modules like import Vue from ‘vue’, import Vuex from ‘vuex’. Go through your files and check where you used from ‘Vue’ or from ‘Vuex’ - make sure to use the exact same capitals (uppercase letters) as in your import statements. The error descriptions should have been written more clearly, but what I explained has been the cause of my problem each time for this error on webpack commands.
• S

  Issue renaming the Boot file
  • Sacrekin  

  8
  0
  Votes
  8
  Posts
  37
  Views

  S

  I could rename the boot file successfully with this approach, albeit through brute force though. HOWEVER, the initial warning remains. It must not be related to the boot mainInit file. I will post a different thread as this is not related to the boot file renaming issue. Thank-you. ps: the warning now: webpack-internal:///./node_modules/webpack-dev-server/client/index.js?http://0.0.0.0:9000:135 ./node_modules/Vue/dist/vue.runtime.esm.js There are multiple modules with names that only differ in casing. This can lead to unexpected behavior when compiling on a filesystem with other case-semantic. Use equal casing. Compare these module identifiers: C:\Users\Jean-Marie\Desktop\CurrentDevQV1\node_modules\Vue\dist\vue.runtime.esm.js Used by 1 module(s), i. e. C:\Users\Jean-Marie\Desktop\CurrentDevQV1\node_modules\babel-loader\lib\index.js??ref–1-0!C:\Users\Jean-Marie\Desktop\CurrentDevQV1\node_modules\eslint-loader\index.js??ref–10!C:\Users\Jean-Marie\Desktop\CurrentDevQV1\src\boot\mainInit.js C:\Users\Jean-Marie\Desktop\CurrentDevQV1\node_modules\vue\dist\vue.runtime.esm.js Used by 158 module(s), i. e. C:\Users\Jean-Marie\Desktop\CurrentDevQV1\node_modules\babel-loader\lib\index.js??ref–1-0!C:\Users\Jean-Marie\Desktop\CurrentDevQV1\node_modules\eslint-loader\index.js??ref–10!C:\Users\Jean-Marie\Desktop\CurrentDevQV1.quasar\client-entry.js
• I

  app:dev-server ⚠️ Failed to open default browser
  • infoPANEL  

  4
  0
  Votes
  4
  Posts
  96
  Views

  

  Same problem here. Have not used the framework for a while. I setup a fresh clean project, and the browser never opens - even though open: true is set.
• J

  Capacitor Build - Errors With capacitor-cordova-android-plugins?
  • jpperlm  

  4
  0
  Votes
  4
  Posts
  38
  Views

  

  Thanks @metalsadman Scott
• L

  multiple entry points?
  • lucaste  

  10
  1
  Votes
  10
  Posts
  231
  Views

  W

  @eyedean said in multiple entry points?: PS. The solution I am going to go with, for now, is similar to your #2. I am going to have my Nginx do reverse proxy anything like mydomain.com/login to mydomain.com/index.html?from=/login, then in my router, at the first rendering time, I’ll try to parse that from query parameter and make an internal programmatic navigation to that page. Why not just use html5 history mode in vue-router? That should be good enough to hot-link directly to the login page.
• 

  `Quasar App Extension "serve" is missing` error
  quasar cli serve npm yarn • • marek.kaczkowski  

  1
  1
  Votes
  1
  Posts
  18
  Views

  No one has replied

• P

  Quasar create error
  • Pepper  

  2
  0
  Votes
  2
  Posts
  20
  Views

  

  You are already in a quasar project. If you want to create create another project within that one, create it outside of the project and when done, move the project to the location you want.
• J

  Quasar CLI only installing/upgrading 1.0.2
  • jarvilito  

  2
  0
  Votes
  2
  Posts
  19
  Views

  

  Quasar CLI is only at version 1.0.2. https://quasar.dev/start/release-notes Click on @quasar/cli. Scott
• T

  Adding API URL to process.env for three different situations
  • taylorg  

  3
  0
  Votes
  3
  Posts
  216
  Views

  T

  @metalsadman Looks like just what I need, thank you!
• M

  Enable auto routing (like nuxt js)
  • Masterxhen  

  2
  0
  Votes
  2
  Posts
  25
  Views

  

  https://github.com/quasarframework/quasar/issues/5378
• J

  Quasar in a Webpack Build?
  • jmbldwn  

  3
  0
  Votes
  3
  Posts
  83
  Views

  

  Answered on Discord. https://discordapp.com/channels/415874313728688138/596276240260923392/635522921934356512 Scott
• J

  This topic is deleted!
  • jmg1340  

  3
  0
  Votes
  3
  Posts
  24
  Views