Gaurav

Hi @SachaG, if it's not too late, I'd like to suggest [accounts-js](https://github.com/accounts-js/accounts) that I recently came across. It tries to emulate Meteor's Account system (including email flows), but in an...

It's possible to achieve Meteor-like "isomorphism" by using Webpack as the build tool, thanks to its fine-grained configurability. While "zero config" is great for application developers, configurability is vital for...

I'd likely start incremental migration towards Next.js + Meteor for my own app. If I make any significant discoveries, will definitely share them here

@SachaG before starting the move to Next.js, check out [Fusion.js](https://eng.uber.com/fusionjs/) that was open sourced by Uber's web platform team couple of days ago! The more I think about its architecture...

> Unless we end up in a world where there's a common standard for GraphQL schemas and APIs, you'd basically have to do 90% of what Vulcan does yourself which...

@SachaG my suggestion is to maintain only one stack officially (aka "reference implementation"). But in doing so, I see an opportunity to also allow users to use their own stacks,...

Meteor is probably the first ~(and so far the only one?)~ framework to do this properly. Some resources on how this is implemented in Meteor: - https://github.com/meteor/meteor/blob/devel/History.md#v17-2018-05-28 - https://www.youtube.com/watch?v=vpCotlPieIY&index=4&list=PLTUf4ytkmI8QOopcigiv_dsIubylmfTsX&t=802s -...

Hi @VaughnVernon, yes I installed the required SDK version after an initial fumble. The above observations are after taking care of the SDK part. But maybe I haven't done it...