Saeed bahrammi

@filipenevola Hi We need to look more at meteor flaws in the rendering server. **1. Do not support data subscription** Unfortunately, the metoer internal rendering server package does not support...

@dr-dimitru I also use prerender now, but I believe the software should be integrated and have few external dependencies. This is the purpose and basis of our companies. **A meteor...

@nathanschwarz This is certainly not a concise and efficient solution. And it increases costs and increases codes. Especially the codes in the handle of the received data are increased. **Finally,...

> @Saeeed-B supporting `subscriptions` with ssr on the server would actually be simple. > On the client it should subscribe to the data, but on the server it should directly...

@pjsofts Maybe I did not understand exactly what you mean. But I know the subscription on the server does not work at all. And that is exactly the problem. On...

@filipenevola One of the most important reasons for ssr is that it greatly reduces the initial response time of the server. And this answer of the server must be accompanied...

@renanccastro Hi, I have not implemented your package yet and the reason is that this package does not provide data based on routes. And I think that will make things...

In general, the package that wants to provide data on the server side must be fully compatible with the Meteor kernel, including the publishing and subscription system.

@nathanschwarz We really need to do a strong test, thank you very much if you can let us know the result.

I have said this elsewhere, perhaps it is worth further investigation. I used npdev-react-loadable for code spliting and implemented it in ssr as well. And I only handled the subscriptions...