CLI

• A

  0.15.4 build how to specify app directory
  • Alinex

  2
  1
  Votes
  2
  Posts
  1253
  Views

  A

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

  How to change theme in dev environment?
  • Denni

  2
  0
  Votes
  2
  Posts
  45
  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
  140
  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
  67
  Views

  

  This occurs with me too
• D

  Environment variables
  • danikane

  7
  0
  Votes
  7
  Posts
  1672
  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
  80
  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
  1
  Votes
  1
  Posts
  55
  Views

  No one has replied

• M

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

  4
  0
  Votes
  4
  Posts
  145
  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
  151
  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.
• B

  This topic is deleted!
  • Blaconix

  5
  0
  Votes
  5
  Posts
  52
  Views
• T

  [Solved] Quasar CLI Vs Vue CLI 3?
  • theara

  3
  0
  Votes
  3
  Posts
  162
  Views

  T

  thanks for your reply
• F

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

  4
  0
  Votes
  4
  Posts
  236
  Views

  

  Is it a Quasar v0.15+ project, or you’ve “quasar init”-it with pre-v0.15?
• J

  Difference in js file output in Cordova build
  cordova build webpack • • jasonl

  4
  0
  Votes
  4
  Posts
  336
  Views

  J

  Updating Quasar to 0.17.6 solved the issue.
• D

  Using webpack without CLI
  • dnorth

  1
  0
  Votes
  1
  Posts
  88
  Views

  No one has replied

• D

  State management - vue-stash
  • danikane

  6
  0
  Votes
  6
  Posts
  775
  Views

  N

  This is the way I am using vue-stash Install npm install vue-stash Then : quasar new plugin store it creates store.js in the src/plugins folder. Open it and add : // import something here import VueStash from 'vue-stash' // leave the export, even if you don't use it export default ({ app, router, Vue }) => { // something to do Vue.use(VueStash) app.data = { store: { // define your data here for example user: { name: 'Bob', email: 'bob@bobby.fr' } } } } Then you have to open the quasar config : quasar.conf.js and add ‘store’ in the plugins array plugins: [ ..., 'store' ], and your good to go. To load the store in your vue files, include : store: { \\ precise the date you want top import here, for example as mentioned above user } be careful to completely define your data in the store.js file if you want them to be reactive.
• H

  Failed to download repo quasarframework/quasar-starter-kit
  • Humboldt155

  4
  0
  Votes
  4
  Posts
  161
  Views

  H

  @rstoenescu It worked perfect! Thank you so much!
• D

  Missing VueLoaderPlugin after update to quasar-cli 0.17.0
  • doonoob

  1
  0
  Votes
  1
  Posts
  154
  Views

  No one has replied

• D

  Creating custom app templates for quasar-cli
  • dsl101

  10
  0
  Votes
  10
  Posts
  2205
  Views

  

  @rstoenescu Thanks. I’m trying to install a helpers folder I have in a private repo on Github: vue init mesqueeb/templates/tree/master/styles/helpers helpers // but I get: (node:58697) ExperimentalWarning: The fs.promises API is experimental vue-cli · Failed to download repo mesqueeb/templates/tree/master/styles/helpers: Response code 404 (Not Found)
• J

  Build Issue : Blank page is displayed after build
  • jsahoo

  2
  0
  Votes
  2
  Posts
  89
  Views

  

  If you are using Node/express as your backend, use the cors package as middleware for express. It’s because your ports are not matching. I usually use the following for my express: // Setup middlewares const bodyParser = require('body-parser') const compression = require('compression') const helmet = require('helmet') const cors = require('cors') module.exports = (app) => { app.use(compression()) app.use(bodyParser.json()) app.use(bodyParser.urlencoded({ extended: true })) app.use(helmet()) app.use(cors()) }
• M

  Quasar Dev command not watching file changes
  • MatanYad

  2
  0
  Votes
  2
  Posts
  85
  Views

  

  Are you also using applications like GitKraken or Code? All of these set up a large amount of file watchers and you may not have enough. You can run this command to resolve that: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p