Improve prefetch & site rendering #253
Open
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.
Main change is to lazily render the filetree on the client, as the existing UI tried to synchronously render DOM elements for every single file in the tree. This broke down terribly for very large publications, e.g. pub 874 with ~12k files in the tree took the backend ~18s to respond, and the subsequent render froze the browser for ~3 minutes.
Only the file tree is lazily rendered on the client, all metadata etc is still SSR so this shouldn't interfere with any indexers.
Misc:
Note:
This branch is based on #252