Starter Kits

• 

  List of Starter Kits per Programming Language and the Backend Framework
  • valasek  

  6
  5
  Votes
  6
  Posts
  212
  Views

  B

  thanks @tohagan I’m working on polishing the rough edges and would love to have it on Quasar Awesome. I’m still very new to working with Quasar but I love the idea and it has been a joy to work with so far. @valasek thanks for adding my project to the starter kit list here. I’m trying to follow best practices from documentation and get advice from people who are experts in the various areas that it touches on. Hopefully I can share my experiences and lessons learned and get more people to try out Quasar!
• V

  Github Layout from Layout gallery not really responsive
  • vsirghii  

  1
  0
  Votes
  1
  Posts
  20
  Views

  No one has replied

• 

  Laravel + Quasar 1.0 with Quasar CLI
  • lucasfernog  

  21
  1
  Votes
  21
  Posts
  2255
  Views

  M

  I am trying to do the same thing, if anyone can help, it will be welcome https://github.com/modemb/larasar
• D

  Dockerised Quasar Cordova Android development starter
  • djleven  

  2
  2
  Votes
  2
  Posts
  150
  Views

  

  @djleven thank you for sharing. I am creating the list of all starter kits and your kit is now included. Feel free to add via comments all undiscovered kits. After the consolidation is done I plan to curate the list.
• J

  create installer electron
  • jcesar  

  3
  0
  Votes
  3
  Posts
  965
  Views

  L

  hi with the version v1.0 the command is different?
• S

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

  14
  3
  Votes
  14
  Posts
  9733
  Views

  O

  SInce Laravel 5.7 is out now, have you updated it? Also have you used tymon package to integrate Laravel JWT authentication?
• P

  Security warnings when running in Electron dev mode
  • pg  

  5
  3
  Votes
  5
  Posts
  3512
  Views

  

  is it possible to switch this dev server also to HTTPS? i have already switched the ‘dev server’ to HTTPS like mentioned at https://quasar.dev/quasar-cli/quasar-conf-js#devServer-Property but seems this is only changing the server for SPA mode.
• 

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

  25
  0
  Votes
  25
  Posts
  1511
  Views

  

  @chiaju - Read two comments above please. Scott
• G

  Menu Like Mene DOC
  • gleyson  

  2
  0
  Votes
  2
  Posts
  75
  Views

  

  Check out the code in the docs part of the Quasar repo. It’s all there. https://github.com/quasarframework/quasar/tree/dev/docs Scott
• Y

  quasar init newgame have many Warn can you help me
  • ycy  

  2
  0
  Votes
  2
  Posts
  101
  Views

  

  @ycy could you run the command `quasar info` and give us the result? with the new version of quasar cli, we use the quasar create command to create a new project
• S

  Yii2 + Quarar with Quasar CLI
  • Sonit  

  1
  0
  Votes
  1
  Posts
  134
  Views

  No one has replied

• B

  Refresh PWA after code update
  • badrday  

  1
  1
  Votes
  1
  Posts
  826
  Views

  No one has replied

• H

  Change build path
  • hariprasath_p  

  1
  0
  Votes
  1
  Posts
  337
  Views

  No one has replied

• S

  Change color on hover
  • smiling_girl  

  1
  0
  Votes
  1
  Posts
  474
  Views

  No one has replied

• S

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

  13
  0
  Votes
  13
  Posts
  3364
  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
  781
  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
  1144
  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
  555
  Views

  No one has replied

• M

  Meteor!
  • mwarren2  

  89
  0
  Votes
  89
  Posts
  34948
  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?
• 

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

  10
  0
  Votes
  10
  Posts
  2563
  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.