@wistia/react-embeds
Advanced tools
Comparing version 0.0.4 to 0.0.5
{ | ||
"name": "@wistia/react-embeds", | ||
"version": "0.0.4", | ||
"version": "0.0.5", | ||
"description": "React component wrappers for Wistia embeddables", | ||
@@ -5,0 +5,0 @@ "browser": "browser.js", |
@@ -16,3 +16,3 @@ # Wistia component wrappers for React | ||
- prevent race conditions when hydration is in play | ||
- be compatibile with server-side rendering | ||
- be compatible with server-side rendering | ||
@@ -65,3 +65,3 @@ It’s the last of these which is most notable. The first few wouldn’t be hard for | ||
The `<WistiaProvider>` component should appear once, likely at or near the root | ||
of the app; all other components should be descendents of it. If you’re doing | ||
of the app; all other components should be descendants of it. If you’re doing | ||
SSR, you’ll need to provide it with two props: a throw-away context object (it | ||
@@ -73,4 +73,3 @@ will be mutated) and the initial href (it does not need to be updated since it | ||
libraries before, the pattern may be familiar, but there’s an extra rub because | ||
extracting the final data is an asynchronous operation. See `examples/next.js` | ||
for a runnable demonstration of how it can be done. | ||
extracting the final data is an asynchronous operation. | ||
@@ -143,3 +142,3 @@ ### WistiaPlayer | ||
tries to hydrate, React will see the elements added by the player as a | ||
discrepency and remove them. | ||
discrepancy and remove them. | ||
@@ -146,0 +145,0 @@ In other words, we defer inclusion of the hook until after mount because it’s |
179437
147