Starter Kits

• P

  Security warnings when running in Electron dev mode
  • pg  

  4
  2
  Votes
  4
  Posts
  2316
  Views

  J

  Cool, that’s what I figured but it didn’t hurt to check
• D

  Dockerised Quasar Cordova Android development starter
  • djleven  

  1
  1
  Votes
  1
  Posts
  94
  Views

  No one has replied

• S

  Yii2 + Quarar with Quasar CLI
  • Sonit  

  1
  0
  Votes
  1
  Posts
  88
  Views

  No one has replied

• L

  Laravel + Quasar 1.0 with Quasar CLI
  • lucasfernog  

  9
  0
  Votes
  9
  Posts
  804
  Views

  S

  @stefanvh Lifesaver
• B

  Refresh PWA after code update
  • badrday  

  1
  1
  Votes
  1
  Posts
  705
  Views

  No one has replied

• H

  Change build path
  • hariprasath_p  

  1
  0
  Votes
  1
  Posts
  311
  Views

  No one has replied

• 

  Suggestion/Feedback from a NEW user's Perspective!
  • Ben Hayat  

  15
  0
  Votes
  15
  Posts
  1239
  Views

  

  BTW, I’m working on a blog series to help newcomers to dive into Quasar faster. The topic of this thread will also be covered in that series too. This tutorial blog series is currently planned to be released around the time 1.0 is released and will be released in, most likely, weekly installments. Scott
• S

  Quasar(0.14.x) Starter with JWT Authentication ( Laravel Backend 5.4 )
  • Sponz  

  13
  3
  Votes
  13
  Posts
  9428
  Views

  

  will this get updated to quasar 16 ? the JWT auth part is exactly what the official kit is missing.
• S

  Change color on hover
  • smiling_girl  

  1
  0
  Votes
  1
  Posts
  438
  Views

  No one has replied

• S

  Native dependencies in electron wrapper
  webpack electron native target • • steffanhalv  

  13
  0
  Votes
  13
  Posts
  3074
  Views

  

  @steffanhalv Do NOT change the webpack target prop. It is already configured in the right way. If you need to change it you’re doing something wrong. Please also note there’s one webpack config for the renderer process and ANOTHER separate one for the main process. Which one are you trying to change? In 99% of the cases, you don’t need to change it anyway. I see that you are importing the http package, which is a node specific library, which is NOT isomorphic (doesn’t also works being run in a browser). You could use it in the main process though, but not in the renderer. Like I mentioned in a previous post, node-loader and it’s webpack rule for renderer process (it’s currently specified only for the main process) will be available by default in Quasar CLI v0.16.2.
• A

  [Solved] Quasar 0.15.10 defaults to the v0.14++ starter kit on init?
  • axlotl  

  2
  0
  Votes
  2
  Posts
  760
  Views

  A

  Never mind. Sorry, I asked this exact question a couple months ago and then went to work on something else and forgot. Answer is here: http://forum.quasar-framework.org/topic/1994/installed-0-15-but-init-still-creates-0-14-9-app/4 (answer, via @vinstah, is nvm install 8 && nvm use 8 && npm i quasar-cli@latest -g && npm i vue-cli -g && quasar init default)
• D

  Meteor-Quasar starter kit questions
  • DamienDeville  

  3
  0
  Votes
  3
  Posts
  1093
  Views

  D

  @damiendeville Now the fact that the Meteor app code must be placed below a template folder is problematic with correctly setting up the launch.json file to simultaneously debug the client and server code in VSCode. Having added the launch.json file found here: https://github.com/Microsoft/vscode-recipes/tree/master/meteor, when launching a debugging run with VSCode, I get an error with the following complaint: no package.json file found in <workspaceFolder>. Since the package.json is in fact in <workspaceFolder>/template due to the installation of meteor inside this subfolder I have tried to change the option: “webRoot”: “${workspaceFolder}” to “webRoot”: “${workspaceFolder}/template” Then I tried to move the package.json file to <WorkspacePath> but it broke my meteor app build. Could anyone using this VSCode recipe for Meteor help figure out how to alter it so that it manages to find the package.json file below the template folder?
• J

  Non single vue templates don't work on App.vue?
  • jckodel  

  1
  1
  Votes
  1
  Posts
  534
  Views

  No one has replied

• M

  Meteor!
  • mwarren2  

  88
  0
  Votes
  88
  Posts
  34784
  Views

  D

  @mwarren2 said in Meteor!: @damiendeville said in Meteor!: Do you mean that this ‘template’ is needed only because running the meteor CLI in the application root folder would somewhat not work? But why? Since you did not use the quasar CLI nor webpack, what is the problem? Also is the name ‘template’ arbitrary? Could it be called ‘foo’ or ‘meteor’ and it would still work properly? It has to be called ‘template’. That’s all I know. @rstoenescu perhaps you could explain?
• J

  create installer electron
  • jcesar  

  2
  0
  Votes
  2
  Posts
  841
  Views

  

  I have two npm scripts in package.json: “prepack:win64”: “quasar build -c --mode electron --target win32 --arch x64 --theme mat” “pack:win64”: "npm run prepack:win64 && electron-builder --win --x64 --project dist/electron-mat/UnPackaged/ --prepackaged …/[app-name]-win32-x64/ You need the “electron-builder” as dev-dependency. npm run pack:64
• 

  PWA not running in standalone (Quasar 0.15.2) ?
  • cheebhodh  

  10
  0
  Votes
  10
  Posts
  2466
  Views

  S

  @rstoenescu I tested it with Android 6.0 and Chrome 64/65 using Quasar 0.15 and 0.14 and it does not open in standalone/fullscreen mode. However, other PWA’s open in standalone/fullscreen mode. For example: https://airhorner.com/ Steps: new blank project with default settings (quasar init test) serve /dist/pwa-mat directory over HTTPS with a valid certificate “add to home screen” is showing service worker registered no errors logged in console Any clue about how to debug the problem? Best regards.
• C

  PWA and firebase cloud messaging
  • copeland  

  1
  0
  Votes
  1
  Posts
  730
  Views

  No one has replied

• J

  plugin vue-apollo in quasar 0.15.1
  • jcesar  

  7
  1
  Votes
  7
  Posts
  1484
  Views

  D

  Great help, both from the original topic and @cheebhodh reply. Up and running with GraphQL and Apollo now, thanks!
• 

  v0.15: custom webpack config
  • LaurentPayot  

  3
  1
  Votes
  3
  Posts
  1993
  Views

  

  @leopiccionia thank you so much. you’re right for Pug, I forgot it was automatic Great! Right now I’m customizing the build.extendWebpack function of quasar.conf.js to add loaders to my Vue single component files. I guess the documentation will talk about that. I’m feeling better now…
• T

  Performance comparison and tips: Cordova wrap vs PWA starter kit
  cordova pwa performance • • thi4go  

  2
  0
  Votes
  2
  Posts
  1285
  Views

  

  Why not have both The beauty of quasar is deploying to multiple platforms form a single codebase. Regarding PWA caching: all this does is keep in memory the static assets that make up an SPA, so you can access those offline. In other words, a PWA does not help with user initiated server interactions. So if you want your app to work offline and still register user actions somehow, you need to figure it out on your own.