-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
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
[Feature] Support SSR Rendring #14
Comments
Issue can be resolved by hiding the player on SSR render and then rendering it on the frontend. I am unfamiliar with Next.js, but with Gatsby it can be done using the following:
|
@jasonlav |
bump. we'd like to see out of the box SSR support as well (planning on scaling this package) |
@snelsi @jasonlav @kenchambers @mdaoust-sidlee We have made an update to support server side rendering on branch |
If you see any other issues with this feel free to open another issue. |
JWPlayer fails to render on Server Side.
Tested in the Next.js application.
The JWPlayer component tries to access
window
property, which doesn't exist on the server, resulting in the following error:Checkout this sandbox:
https://codesandbox.io/s/next-js-forked-yl5wme?file=/pages/index.js
Expected result:
JWPlayer component should skip Server Side rendering, or defer the usage of the
window
to prevent the errorThe text was updated successfully, but these errors were encountered: