There's some conflict between this pr and a recently merged one. If you update it I'd be happy to test and merge this one too.

Closing this due to lack of progress. Feel free to open a new one if interest resurfaces.

You have not been able to fix a conflict in 8 lines of code?
Please go a head merging this fix or provide a solid SSR fix solution.
@urohith173 don't you follow this topic anymore?

I am not following the repo currently. that's why i couldn't reply to the comments. @DDurakISH thanks for bringing it to my attention by tagging me i will look into the conflicts and create a new pr.

@DDurakISH @wittlock no new pr is required as the current code in master branch will not result in this issue.

@urohith17 thank you very much for your investigation and response!

Note: the issue still exists in the current latest version 2.1.0. So the next release should fix it.

Alright. Weekend got away from me, but now there's a 3.0.0 up at npm. I hope this works as expected and sorts your ssr related issues. Let me know if there's anything wonky with it.

Working fine 👍.

I think you can close the issue #63 .