-
Notifications
You must be signed in to change notification settings - Fork 101
Description
I am considering using Asteroid in order to separate the Meteor backend from the client. This way I can share one backend with several Meteor clients to start.
But there are a few red flags on this project:
@davidebianchi you answered a question 4 days ago, but a lot of questions/issues have gone unanswered, there's a PR waiting to be merged, and there's been no activity on the master branch since last year (I know issue#102 has been updated recently). Why, is this project considered feature/bug complete by mondroa or are there no longer resources being applied to it for another reason?
Also, branch 'Issue#102', seems to be more active than master, do you recommend using this branch over master?
Will the master branch developed beyond Oct '16?
Also, will Asteroid work with Meteor 1.5 and Dynamic imports (https://forums.meteor.com/t/ben-newman-demos-meteor-1-5/34475)?