CLI

• R

  This topic is deleted!
  • remmai  

  4
  0
  Votes
  4
  Posts
  25
  Views
• R

  How Quasar-cli uses third-party plugins?
  • remmai  

  3
  0
  Votes
  3
  Posts
  38
  Views

  

  Use a boot file. https://quasar.dev/quasar-cli/cli-documentation/boot-files
• R

  This topic is deleted!
  • remmai  

  3
  0
  Votes
  3
  Posts
  18
  Views
• K

  Try to build -m ssr
  • karacho  

  5
  0
  Votes
  5
  Posts
  71
  Views

  K

  It seems so But i havent got a path entry - nowhere… Maybe i should use a blank quasar.config.js…
• J

  Build SPA without launch server
  • jo06  

  2
  1
  Votes
  2
  Posts
  35
  Views

  

  The command quasar build doesn’t launch a server. Are you sure that is the issue? Scott
• I

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

  8
  1
  Votes
  8
  Posts
  436
  Views

  B

  Hi, this is still an issue with quasar dev in WSL. I don’t think it’s an issue with windows 10 since VUE projects are opened without issues with npm run serve. And that is able to open the browser. $quasar info Operating System - Linux(4.4.0-18362-Microsoft) - linux/x64 NodeJs - 10.18.1 Global packages NPM - 6.13.6 yarn - Not installed @quasar/cli - 1.0.5 cordova - Not installed Important local packages quasar - 1.7.1 – Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time @quasar/app - 1.5.0 – Quasar Framework local CLI @quasar/extras - 1.4.0 – Quasar Framework fonts, icons and animations vue - 2.6.11 – Reactive, component-oriented view layer for modern web interfaces. vue-router - 3.1.3 – Official router for Vue.js 2 vuex - 3.1.2 – state management for Vue.js electron - Not installed electron-packager - Not installed electron-builder - Not installed @capacitor/core - Not installed @capacitor/cli - Not installed @capacitor/android - Not installed @capacitor/ios - Not installed @babel/core - 7.8.3 – Babel compiler core. webpack - 4.41.5 – Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, … and your custom stuff. webpack-dev-server - 3.10.1 – Serves a webpack app. Updates the browser on changes. workbox-webpack-plugin - 4.3.1 – A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache. register-service-worker - 1.6.2 – Script for registering service worker, with hooks Quasar App Extensions None installed
• A

  This topic is deleted!
  • amoss  

  1
  0
  Votes
  1
  Posts
  4
  Views

  No one has replied

• K

  ssr build overwrites git configuration when deploying to heroku
  • karacho  

  2
  0
  Votes
  2
  Posts
  31
  Views

  K

  found the answer myself: git subtree push --prefix dist/ssr heroku master
• S

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

  1
  0
  Votes
  1
  Posts
  131
  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
  33
  Views

  No one has replied

• W

  Running cordova Android dev without a server
  • walfin  

  10
  0
  Votes
  10
  Posts
  304
  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
  60
  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
  119
  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
  82
  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
  82
  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
  465
  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
  77
  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
• L

  multiple entry points?
  • lucaste  

  10
  1
  Votes
  10
  Posts
  645
  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 npm serve yarn • • marek.kaczkowski  

  1
  1
  Votes
  1
  Posts
  108
  Views

  No one has replied

• J

  Quasar CLI only installing/upgrading 1.0.2
  • jarvilito  

  2
  0
  Votes
  2
  Posts
  47
  Views

  

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