@rstoenescu Forget the strange info messages - they’re definitely down to Vue, and not Quasar.
However just to remind you about the script, any chance of this happening?
- I see that there are a lot of views for this page, I don’t know what your statistics are telling you, but it looks like quite a few people are consulting this page, which presumably translates into quite a lot of interest.
Meanwhile Season’s Greetings. Hope you have a good 2017!
@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.
@mwarren2 I think I got that minor bug you were talking covered with v0.12.1 (to be available soon). Will triple check again before the release. Thanks for taking time to jump start Quasar with Meteor!
@ric0 Short answer is that I’ve got no idea!
I haven’t even looked at Apollo yet. For two reasons:
Firstly I’m a Meteor fan, especially for what it does on mobile. I’m very satisfied with it.
Secondly although I am sure that I will be investigating Apollo in depth eventually, I’m get to let it settle down a lot more before I begin to look at it.
It’s starting to get simpler as time goes on, and that process is going to accelerate in the coming months.
@mwarren2 Thank you for answering.
I should try that by myself when I find the time and post back here about how it went
First step is cloning your repo and give it a spin
@rstoenescu Suddenly got a new error and it’s a brick wall.
Just wondering if you can think of anything that might help.
Uncaught SyntaxError: Unexpected token import
This is happening on this quasar code line:
import TableFilter from ‘./TableFilter.vue’
What’s happening is that meteor is building from the quasar-framework /src folder and not the /dist folder.
I cannot for the life of me understand why it is suddenly doing this.
Does this ring any bells with you at all?
I’ve tried going backwards to previous Quasar versions, but it made no difference. (currently working with 0.13.0)
@mwarren2 hmm, might this be something that changed in Meteor?
Don’t worry, I’ve spent two days on the problem and I’ve got no choice but to throw away what I was doing and start again. I hadn’t got very far.
I don’t think it affects our project here, it was a new one.
However I will update Quasar and Meteor here now and see what happens. Thanks.
@rstoenescu I’ve updated and this project is fine.
The other project is back on course.
Your framework, I have to say, is spectacular.
@mwarren2 Thanks! Big things coming up regarding form components. Quasar will make them rock!
This post is deleted!
@rstoenescu Hi. Hope you are well. I only contact you when I’ve got a problem, right?!
My build in Meteor is failing, so I registered a bug with Meteor, but they said to contact you.
The bug is here: https://github.com/meteor/meteor/issues/8498
Basically some es6 import statements seem not to have been transpiled.
Could you take a look at it? Thanks.
Here is the gist of their comment:
Babel configuration should transpile newer ECMAScript constructs into ones that are supported natively by the engine executing it (Node.js v4 in Meteor’s case). Most packages Babel their code before publishing (quasar-framework is no exception), and Meteor doesn’t transpile Node.js packages again as this might result in re-transpilation.
@mwarren2 Hi, *.vue files first go through the
vue-loaderin Webpack. Meteor obviously doesn’t use
vue-loaderso there’s a problem. Are you looking in
/srcfolder in the template or
/dist? The latter option is the preferred one. If not, try including the CommonJS format of Quasar distributable (
quasar.common.js) instead of the ES6 version and tell me how it went. Thanks for your Meteor work with Quasar!
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
For whoever has been watching this starter kit discussion, quasar now installs directly from npm into a meteor app.
Use https://github.com/meteor-vue/vue-meteor/tree/master/packages/vue-component to integrate meteor with vue, then install quasar-framework.
There’s a starter kit here: https://github.com/quasarframework/quasar-template-meteor
Please note the importance of the .vueignore file in the app root. Builds will fail without this file.
@mwarren2 we need to talk a little about Quasar v0.14. Can we set a Gitter session pls?
@rstoenescu I’m available any time you like.
However maybe I should try the beta first.
It’s actually a good moment because a few days ago I started working regularly with quasar on a proper project.
What country are you in? Will you set up the session?
Let me know what you think.
I am also very interested in using Quasar 0.14 with Meteor!
@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?