We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
Because, now we use React from NPM directly.
Sorry, something went wrong.
So will the benefits of using flow-router-ssr like in https://kadira.io/academy/meteor-routing-guide/content/rendering-react-components persist? I'm trying to use Dochead to dynamically serve meta tags for web crawlers (which doesn't seem to be working with just flow-router v2.x + webapp, so I'm hoping flow-router-ssr will do the trick). https://github.com/kadirahq/flow-router/tree/ssr says to use ReactLayout. I'm using Meteor 1.4
flow-router-ssr
flow-router
ReactLayout
Also, looking at https://github.com/kadira-samples/meteor-data-and-react, what is the NoSSR use case if I will be rendering with flow-router-ssr?
This applies to Meteor 1.3 and after? In other words, does it also apply to Meteor 1.4?
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: