troika seems to break SSR
See original GitHub issuehttps://github.com/react-spring/drei/issues/25
https://github.com/react-spring/drei/issues/23
it seems to rely on document
, which does not exist in node.
i believe in order to make troika pseudo-isomorphic all it would have to do is:
const linkEl = typeof document !== 'undefined' && document.createElement('a')
this would allow ssr to function normally.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (2 by maintainers)
Top Results From Across the Web
"Excesses are not permitted": - Mass Terror and Stalinist
The victims seem to have been politically or socially marginal types already somehow stigmatized: common crimi- nals, veterans of the White Army in...
Read more >The Return of Stalinist Show Trials
On Monday, a court in central Russia jailed members of an anti-fascist activist group Set — Russian for “Network” — for up to...
Read more >Troika - Naomi B Cook
For this project I worked on a data set project using GPS coordinates of three online dating users. This project was spurred by...
Read more >LEADERS OF THE USSR AND UKRAINIAN SSR DURING ...
proposed in a telegram to local organizations that local workers stop ... leaders of the Ukrainian SSR were responsible not only for the...
Read more >Policy Paper and Case Studies Capturing UN Preventive ...
our case studies and elsewhere, that a break in the escalatory ... and it appeared the international troika had suffered a serious.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yep, I haven’t felt any other problems. and in 0.26.1, the warning message disappeared. Thank you! @lojjic
@gtolarc I can see how that warning message would be very annoying in server logs, so I’ve gone ahead and suppressed it in non-browser environments: 3dedb8f2b338e9345c107831863152b115ca50d2
I’ve published 0.26.1 with that change.