Navigation Menu

Skip to content
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

blog post? #1

Open
tomByrer opened this issue Jun 15, 2021 · 1 comment
Open

blog post? #1

tomByrer opened this issue Jun 15, 2021 · 1 comment

Comments

@tomByrer
Copy link

Hi, as always you are making some neat stuff.
But lately it is beyond me; I'm still not sure what this is for?
Maybe I could use better examples &/or why use this over other tech.

(No need to reply right away; I assume you or someone else will blog about your latest stuff, so just link here if you happen to remember please.)

@WebReflection
Copy link
Owner

This is a building block that made ube-ssr possible.

I need to write more blog posts about these latest repositories, but time isn't always on my side.

Long story short though: this allow any website to serve inline as <script> or even async <script type="module"> libraries in what is likely the most efficient way to date to do so, and through a JSON file (cache) that can work for dynamic cases, but it can be used to generate whole HTML pages with all scripts included, as it is for ube-ssr.

Imagine this is Webpack splitting code in a single JSON file that SSR can flush on demand, with auto-resolved dependencies graphs, and aggregated dependencies via reference counting.

I know ... I'm probably adding more confusion than clarifying ....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants