Akryum’s meteor-vue-component package simply integrates vue-i18n. Hard coded files are something standard so you can send translators a file and they send it back once translated. In Python or PHP (eww) realm this is done via .po and .pot file extensions, but json files are convenient for javascript.
1 Like
Some new features have arrived in akryum:vue-apollo, with configuration and loading state hooks.
3 Likes
Anybody know how vue-router 2 compares with flow-router?
I am starting my first projects from scratch. No past projects to maintain.
Marc
Basic list of needed stuff for starting a Vue-js+meteor project+flow router+Simple schema?
(React is INPOV to ugly and complex. And one file per template is enough!)
-
Do we really need webpack (for Vue components)?
Of course Code splitting & on demand is a need to have soon or late,
But for now, too complex and some say MDG works on a procedure (wait for it astraunauts!) -
What permission/role package can fit?
Bottom of the line: lots of boilerplate of disparate but mendatory packages for smooth start! (and risk, anyway to align with something else in soon future because MDG will catch up with something different or same but in an official fashion)
Not really needed any more since @akryum made great Vue integration packages.
If you use Vue you should use vue-router instead of flow-router.
Thanks Laurent, but beside official routing package from Vue, do you see any advandages using vue-router over flow-router? @akryum uses flow-router in his webpack bases example. And I like flow-router’s phylosophy and future server side rendering and fast render. But never used any router yet.
Any comparison on routed in a vue+meteor context appreciated.
vue-router is perfectly integrated to Vue: http://router.vuejs.org/en/route.html
Also <router-view> is a must if you want layouts with Vue. You can find an example here.
As always you should try both and make your own opinion, depending on your specific needs.
I would recommend vue-router (and it’s getting SSR with Vue 2.0).
1 Like
Is react apollo client compatible with vue.js, or are you just getting half the dead if using vue that is still not supported despite being superior to react as the author puts it.
@akryum I started playing with vue-apollo and I love it. Too bad Apollo does not have a stable API yet, I could not make their latest apollo-server work with your package. Note that there is now an “experimental” way for reactivity in Apollo.
1 Like
I was just trying to sort out the npm stuff to get to vue 2.x since my params weren’t working in blaze templates hoping that might naturally bump vue router to 2.x as well, but apparently there’s another package for that. What if vue 2.x isn’t compatible with vue router 1.x than it would entirely be “impossible” to update, without npm going fail or invalid (which it did for which reason I don’t know).
Now Vue is more trendy than React 
https://trends.google.com/trends/explore?date=2014-04-07%202017-05-07&q=vuejs%20%2B%20vue.js,reactjs%20%2B%20react.js
I haven’t read this whole thread, but there is a webpack package for Meteor.
Also, it isn’t difficult to make a outside-of-meteor webpack build with Vue, and have it simply output the bundle into the Meteor app’s directory. Then it will run on the Meteor client.
It’s really easy!
That being said, we still need some reactivity solution that can hook Meteor reactivity into a Vue component. This doesn’t rely on the build system, it can simply be a Vue plugin to load at runtime.
Ah, that is too awesome!!!
That something is popular or brings happiness, or is used in production doesn’t at all mean that it is any good. There have been so many terrible programming ideas and languages that were popular…
React brought a fantastic idea to the world, but the execution is incredibly poor and now done much better by ‘copy-cats’ like Vue, Marko, Moon, etc (even Preact is doing a better job these days!). Just to give you an idea, it is bloated and slow (not to mention its syntax and code hacks are a joke):
Moon - 7kb
Mithril - 8kb
Vue - 25.86kb
React + React DOM - 43kb
Angular 2 - 111kb
Update performance (more is better):
Moon - 102 repaints/sec
Mithril - 95 repaints/sec
Angular 2 - 62 repaints/sec
Vue - 50 repaints/sec
React - 49 repaints/sec
Angular - 47 repaints/sec
Developers should think twice before using React, there are superior options out there. Blaze/Viewmodel being one of them.
But these don’t get picked because React has first-mover advantage and Facebook’s behind it. And as a result devs blindly start implementing React, because of logical reasoning like “there’s a huge number of very reputable companies using it…”.
So yes, when people start doing things without thinking, that’s what I call a hype.
5 Likes