@DamienDeville Thanks for your post, which brings up some good points.

The example app is not perfect as far as meteor code goes, it’s true.
But I’ve spent all my time just getting quasar working with vue and meteor, and writing perfect meteor code has been low down on the list of aims for this particular thread.

However, now that it’s all working together, I’ll look into your comments and tweak stuff some time soon.
I would also add a point 4. to your list, which is to rename the /imports/ui folder to /imports/client, so that I can remove the ‘if(Meteor.isClient) {’ line from AppLayout.vue

@rstoenescu Have updated to 0.12.0 and everything is now working, which makes installation completely straightforward.
Thankyou for all your work on this, I think we can say it is basically done.

I might add a bit more code to help Meteor people along.

One minor bug seems to be left:
On IOS the right-hand drawer still gets stuck.

@rstoenescu I’ve updated and this project is fine.

The other project is back on course.
Your framework, I have to say, is spectacular.

Ok, back on track. Thanks for the explanations.
Yes, meteor doesn’t use webpack, that was the problem.

So now I’m just doing quasar includes from quasar.es6.js which I keep in a client folder.
I’ll change the starter kit accordingly

@rstoenescu Hi. It appears that you changed the folder name on github from ‘app-template-meteor’ to ‘quasar-template-meteor’, right?

Fine by me, but this left a mismatch with the name in package.json and with the name you need to use to ‘git clone’ the repository.
So I changed the package.json name to try to solve the problem, but you still need to use the old name when using ‘git clone’.

I don’t know how to solve this, and have not found any solution after extensive googling. Would you mind taking a look at this?

My honest reply is no. Not at the moment.

1. Meteor is ready and has been for a long time.
2. Meteor / Vue, - see https://github.com/meteor-vue/vue-meteor - is a great project, but is still in beta
3. Quasar is a superb piece of work, one of the best I’ve seen, but is still in beta.
   Quasar now works with the other pieces, but I can’t say that I’ve used everything together on a sizeable project.

I’m using the mix for my personal projects, but not for other people’s.

@elavaud said in Meteor!:

Why quasar + meteor and not simply meteor + vue?

Quasar gives you a very good-looking app out of the box.
You don’t need Quasar to produce an app, but it sure looks better.
It also simplifies using many of the tools you need, such as transitions and css. And it works without much effort on PC, Ipad, and Phones.

It’s also based on Vue. So if you want Quasar, you need Vue.
Vue is easier to use than React, in my opinion. Vue is also getting a lot of traction, it’s got a good future.
Unfortunately it’s not being actively promoted by Meteor - React is - but there are a series of viable codebases that integrate with Meteor.

Meteor - many were drawn to it for its ability to reflect changes to the db on screen automatically, I was too. I like the fact that I don’t have to use Webpack… It has also made phone apps with Cordova relatively simple, so I am sold on it for good, especially since it has proved to be a permanent fixture with solid support.

The Meteor starter kit application for 0.14.7 is working with Meteor with a simple install from npm now - for those who may be watching this thread.
https://github.com/quasarframework/quasar-template-meteor

Now updated to 0.14.8 to correct a ui problem