Meteor!



  • 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



  • Hi there,

    @mwarren2, @alexandesigner: would it be possible for you to explain to us what is the difference between your two respective Meteor+Quasar scaffold examples and their respective pros and cons?

    Thanks!





  • The quick answer is that I don’t really know, because I hadn’t seen the alexandesigner one.
    However he seems to have found a way of using the quasar-cli with meteor which is interesting.

    I decided not to use quasar-cli because it involves using webpack, which meteor avoids using completely, because webpack is rather complicated.

    • That, I think, is the real difference.

    If you understand and like webpack by all means go for it. Though I notice that it hasn’t been updated for 5 months, which, given the speed at which quasar-framework is currently changing, means that it is out of date. You could try to contact him to see if he will bring it up to date.



  • I see. I found alexandesigner’s mentionned in the following discussion thread: http://forum.quasar-framework.org/topic/815/quasar-v0-15-roadmap/38

    In the exchange below, @rstoenescu advised alexandesigner to get in touch with you. SO I assumed (wrongly apparently) that he did.

    alexandesigner 5 months ago
    @rstoenescu 💯 Amazing!! let me help with the meteor starter kit … Give it a try https://github.com/alexandesigner/quasar-meteor @theara
    I uses meteor-client-bundler, the base of the quasar to develop and for production using webpack, the meteor say it more like an API database in websocket, I did not add tests, anyway it’s already a path, please help me to improve if you have any idea or tip … open an issue or send a PR, maybe this is a clean integration without changing the structure much…

    reply quote 1
    rstoenescu ADMIN 5 months ago
    @alexandesigner Hi, This is the true amazing thing. People wanting to contribute. Please contact @mwarren2 and sync with him as he is the “big daddy” in Meteor integration. Thank you!

    reply quote 0
    alexandesigner 5 months ago
    Perfect … thanks @rstoenescu and @mwarren2 how can I help? I think we can have two ways of integrating with the Meteor … one is using the Quasar base with Webpack and the other is integrating directly into the Meteor + Isobuild base maybe creating a package for distribution … this repository covers the first form, if the will to guide me to do the right thing…



  • Now you mention it, if you go up this thread to 5 months ago, there was a post by @alexandesigner, but it was deleted.
    I honestly can’t remember what happened.

    What he did is certainly interesting if you want to go the webpack route and be more integrated with quasar-cli. Perhaps he will reply.



  • @mwarren2 said in Meteor!:

    I decided not to use quasar-cli because it involves using webpack, which meteor avoids using completely, because webpack is rather complicated.

    That, I think, is the real difference.

    Actually I am getting confused concerning whether or not you are using quasar-cli because:

    1. your starter kit contains .vue files and the quasar doc [http://quasar-framework.org/guide/index.html](link url) states that without using the quasar-cli one cannot use such files
      Here’s a comparison:
      Feature UMD Starter Kit
      SFC (Single File Component - for Vue) - Yes

    2. In your own starter kit page you say:
      The ‘template’ folder is necessary for the quasar cli command to function. This extra ‘template’ folder is there because quasar-framework requires it.
      But if you don’t use the quasar cli, why is the template folder needed then? Especially given that neither the recommended Meteor app structure [https://guide.meteor.com/structure.html#javascript-structure](link url)
      nor the recommended Quasar app structure [http://quasar-framework.org/guide/app-directory-structure.html](link url) contains any folder named ‘template’.

    Thanks in advance for rescuing me from my current confusion :).



  • @damiendeville said in Meteor!:

    your starter kit contains .vue files and the quasar doc [http://quasar-framework.org/guide/index.html](link url) states that without using the quasar-cli one cannot use such files
    Here’s a comparison:
    Feature UMD Starter Kit
    SFC (Single File Component - for Vue) - Yes

    Sorry for any confusion.

    No, you don’t need quasar-cli for Meteor. In fact I can’t see how it can be used, because quasar’s build uses Webpack, and Meteor doesn’t. Meteor has its own very simple build system. Webpack is considered pretty complicated to configure, and Meteor has purposely avoided it. Hence the need to avoid using quasar-cli. I can’t see how using quasar-cli can work with Meteor, though anybody is welcome to try.

    There is no problem using .vue files.

    @damiendeville said in Meteor!:

    The ‘template’ folder is necessary for the quasar cli command to function. This extra ‘template’ folder is there because quasar-framework requires it.

    I will see if I can change this phrase as maybe it is not particularly clear. I was asked to add the root ‘template’ folder by quasar’s creator - presumably one day it would be good if it fitted into the quasar starter-kit system, but at the moment I don’t think this is possible - maybe one day when Meteor can simply be installed from npm, if that happens.

    For the moment you should simply ignore the template folder and change directory into it and run the usual meteor commands from there.



  • @mwarren2 said in Meteor!:

    I was asked to add the root ‘template’ folder by quasar’s creator - presumably one day it would be good if it fitted into the quasar starter-kit system, but at the moment I don’t think this is possible - maybe one day when Meteor can simply be installed from npm, if that happens.
    For the moment you should simply ignore the template folder and change directory into it and run the usual meteor commands from there.

    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?

    I also do not understand the need for transpiling. You say:
    Then here we transpile two es6 .js files (one for ios, one for material design) to commonjs which meteor needs
    What are those files to transpile, where are they located in your project and you are talking about transpiled from what source langage to what langage? I thought Meteor was written in and supporting es6.

    Thanks again for further clarifications



  • @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.

    @damiendeville said in Meteor!:

    I also do not understand the need for transpiling. You say:
    Then here we transpile two es6 .js files (one for ios, one for material design) to commonjs which meteor needs
    What are those files to transpile, where are they located in your project and you are talking about transpiled from what source langage to what langage? I thought Meteor was written in and supporting es6.

    There are some es6 files that currently Meteor does not automatically build correctly in es6. So they need to be transpiled. This has probably been solved in Meteor 1.6.2, which will soon be released.



  • @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?