Short answer: nope!
Google’s already solved it
Client-side rendering did indeed affect pagerank at one point, many years ago. In the past, websites used to render HTML on the server. The server would recognize the crawler, return code, and prompt the crawler to request a static snapshot of your website. The actual version of your website was generated by the client, not as a static snapshot, which was why client-side rendering used to be so difficult.
In October 2015, Google announced that they would be deprecating this practice. And just last week, Google posted the following on the official Webmaster Central Blog:
Prerender.io saves the day
We use the Kadira DocHead package to automatically add title, description, and detail meta tags to your store product pages. This, in turn, renders into SEO-friendly data, which crawlers then pick up and index. If a shopper searches for "size 7 green shoes" in Google, then your product’s meta data will help that exact page get to the top of the search results.
If you’d like to inspect the meta data yourself, you may do so by installing an SEO Inspector.
We’re all about server-side rendering
SSR is also helpful in ensuring that your Progressive Web App (PWA) is indexable and linkable. Google advises users to employ server-side or hybrid rendering (server and client-side) for their PWAs whenever possible. Google also now recommends that users adhere to a progressive enhancement-based development strategy. Because the core content of a site always comes first, that content is most accessible to crawlers. For more info on this, visit the Webmaster Central Blog.
That's about it. Hopefully, this post has dispelled some of your concerns on whether or not your site's getting indexed.
If you have any more questions regarding SEO, server-side rendering, performance, or anything else, feel free to reach out to us via our Gitter chat. Or, join one of our open community calls.