Add support for static site generation (SSG) or server-side rendering (SSR) #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds an entry point to
@theoplayer/web-uifor Node.js, which uses Lit's SSR DOM shims to replaceHTMLElementandcustomElements. We also make sure not to usedocument.createElement()during initial load, by lazy-loading all<template>elements.This allows
@theoplayer/react-uito be loaded during SSG/SSR, such as when using the Server React DOM APIs or when using a full-stack framework like Next.js. You still need to hydrate your React app on the client to make the UI interactive, but that's usually handled by your app framework.