I tried to upgrade to 1.3.5.1 from 1.2.2 and ran into issues. I’m getting Can’t find npm module ‘bable-runtime/helpers/typeof’ error. Will I have to reinstall Meteor and delete .meteor in the home directory in order to resolve this?
UPDATE: I got 1.3.5.1 working by removing .meteor and doing a curl install. Now to test.
Reactivity and real-time data are two different things. Apollo does support reactivity because (from what I’ve seen) it uses redux underneath. React’s setState can achieve a very similar reactivity as Tracker and Blaze. The thing you should be worried about with non-meteor solutions is getting fine real-time data.
Also just wanted to let you guys know I haven’t forgotten about this… it’s coming down the pipe in a week or two. I need to make some kind of spike for transitioning a current app so it’ll happen sooner or later
One thing that I worry about is the size and complexity of the javascript bundle that I’m creating when I’m using so many technologies together in an app (minimongo+livedata+apollo+react+blaze… etc. etc.). If I’m creating an app that’s going to be accessed on phones on mobile networks, how many libraries can I cram in there before I create an app that is completely unusable on mobile? (real, non-rhetorical question!)
I know I could potentially split code by creating different projects, but that will requires careful surgery of the code, more work.
Ok, quick update… I started recording tonight but had to (temp) pause the recording as I spent about an hour cursing and muttering at the NPM gods. I finally have it installable so they screencast should be out soon
@sashko is apollo-server 0.1.5 the latest that works with Meteor? I had errors with apolloServer not being a function using the latest readme in the Meteor section. I also had to go back to graphql-tools 0.6.6 because of an illegal token error (maybe an es6 error or something… can’t remember). Just wanted to double check before recording it!
Thanks for the link. I updated my package.json to have those (which added graphql-typings) but it still errored out. Apollo package was stuck at 0.0.1 so I removed .meteor/versions which updated a lot of things including apollo. Working now
Given that Vue is the only serious React competitor at the moment (imho), it could be a good idea to highlight that vue-apollo npm package on the apollo website to attract numerous Vue users. Just my two cents…
I agree, this is an awesome idea! As soon as the vue-apollo package gets a bit more usage and someone is using it in production, we should definitely add it to the website.