Arunoda Susiripala

We've a similar issues reported here: https://spectrum.chat/thread/3d65b436-b085-4eef-ad84-0941c473e09d Next.js doesn't hijack scrolling. But this is a real issue. Here's what's happening. This is because of browser's default scrolling behavior. See: https://github.com/zeit/next.js/issues/3303#issuecomment-354225323...

@Qix- I think we discussed about this somewhere else. When we explicitly import `node-fetch`, it's a lot clear. There's no need to mention anything about peerDependencies. On the otherhand, we...

@chamathpali I know the guys behind ShoutOut. I'll talk to them too. But better if we can work with a telco and they can do better and cheaply.

May be it's pretty hard to fulfill some of the needs at once. So may be we can show how much of donations/stuff went to that. Also we may need...

May be update the spec about this.

Try to the latest repo. And delete the node_modules directory and install from scratch. Then you'll see something like this: http://recordit.co/cHUPhZifIJ

BTW: I'm launching it in few hours. This is some testing.

Could you give more context to this ?

That's the way we do it. We called `.find()` here. So, whenever there's a change inside to the collection, you'll get data.

This is not possible with React. This is only something works in Blaze. Have you done a performance test? Usually this won't be an issue in React.