FCM also has a library for the Web, have you tried this? I don’t see why using it with Vue.js would be any different than VanillaJS

@spectrolite v0.14 Quasar Apps seem to be working on Quasar Play 0.13.7 for me

@rstoenescu When you get back from vacation I’d appreciate an example for point b.

@n.taddei I’ve been trying find out what is causing that to happen for the past 25 minutes. It’s going to be really rewarding when found.

EDIT: So if you comment out this.$refs.modal.close() in CompanyCreate.vue:61 the problem goes away (at least on quasar v0.13.9). I’ve submitted a PR to the repo.

I’d take a look at this thread as it’s been requested before.

I am using vue (also as a single file) and do not use any CLI/webpack/other stuff (do not feel comfortable enough with them).

Not being comfortable enough with webpack & other node tools of the month is what drove me to Vue.js, but I really like how the Quasar CLI held my hand so much at the start that I’d recommend giving it a try.

See: http://forum.quasar-framework.org/topic/580/migration-0-13-to-0-14/3 & http://forum.quasar-framework.org/topic/522/upgrade-guide-for-0-14-beta

most people come to it after being scared off or disgusted by angular/react or whatever bloated and uselessly complex framework

That’s exactly what drove me to use Vue instead of React as I didn’t want to change my workflow for a library. I guess Quasar was just that good, and it was easy to get started due to the cli. It does seem strange how Quasar isn’t “drop in a <script src=…> tag and use” like vue is, and a codepen showing off the components would be neat, but it’s just not that difficult to install the quasar-cli and init a project to check it out. The beginner/quickstart documentation does need some love though.

Great idea! I’m not sure what material design has to say about it, but you should open a GitHub Feature Request Issue

@Fernando2684 Have you taken a look at https://github.com/quasarframework/quasar-play/blob/v0.14/src/components/showcase/other-components/tree.vue ? Unfortunately I haven’t spotted a Quasar app in the wild that uses tree.

@tonpereira You are right, I didn’t notice the /. The self closing syntax should work just fine. Have you tried to isolate the issue by creating a minimalistic repo to reproduce the error? And you’re using quasar 0.14 beta & vue 2.3.x right?

@a47ae Good catch. @tonpereira seems to be closing a nonexistant q-field tag instead of closing the q-input tag. Do let us know if that solves the problem @tonpereira

That’s a lot of javascript!

(missing gif from the original github issue) https://user-images.githubusercontent.com/2828767/28628251-6ec68a48-7224-11e7-8752-bc192c99f3db.gif

most people come to it after being scared off or disgusted by angular/react or whatever bloated and uselessly complex framework

That’s exactly what drove me to use Vue instead of React as I didn’t want to change my workflow for a library. I guess Quasar was just that good, and it was easy to get started due to the cli. It does seem strange how Quasar isn’t “drop in a <script src=…> tag and use” like vue is, and a codepen showing off the components would be neat, but it’s just not that difficult to install the quasar-cli and init a project to check it out. The beginner/quickstart documentation does need some love though.

@spectrolite v0.14 Quasar Apps seem to be working on Quasar Play 0.13.7 for me

@Tekki I’d think that having it on the front page of http://beta.quasar-framework.org/ would be enough ( Live DEMO [Material theme] & Live DEMO [iOS theme])

And now we wait for vue 2.4.2!