data-template
wasm-service
data-template | wasm-service | |
---|---|---|
4 | 11 | |
18 | 674 | |
- | - | |
8.1 | 3.8 | |
5 months ago | 3 months ago | |
HTML | Rust | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
data-template
-
Building a Front End Framework; Reactivity, Composability with No Dependencies
I made a similar library [1] using data-* attributes. It also supports nesting, looping and conditions. For event handling, I use function in object (a.k.a. method) while you support writing them inline.
Your way to support inline logic in the text and style is interesting.
[1] https://github.com/beenotung/data-template
- Htmx
wasm-service
-
Wasm and golang
There is a rust one here: https://github.com/richardanaya/wasm-service
-
Htmx
Check out the live demo! https://richardanaya.github.io/wasm-service/
Last month I contributed the todos functionality to this project.
I think this is a great idea and could eventually enable htmx projects to transition from server-side-only to being a PWA with very little code changes (given the right backend).
Unfortunately this particular implementation exhibits some blocking issues which I was not able to solve yet:
1. The Service Worker is eventually unloaded from memory, which means all data is lost because it currently stores everything in memory. This isn't a defect as much as it is lacking a persistence feature; this is a MVP (emphasis on minimal) after all. The most promising solution in my opinion would be to use the OPFS/File System Access API with SQLite, which is yet to be shipped in all browsers.
2. The bigger issue is that once the SW is unloaded it doesn't come back. The SW getting reaped after being idle is fine, that's part of the expected behavior. But there are no events or any other indication that it was disconnected, at some point it just stops intercepting requests. I don't know why. If anyone can chip in here to say why it does this and how I can detect or somehow restart SW fetch interception on demand I would be glad to hear it.
( For some more detail see the "# Remaining Issues" in my PR #5: https://github.com/richardanaya/wasm-service/pull/5 )
- Serve local and remote HTTP requests?
-
Is your computer too slow to run Chrome? Just...steam Chrome from the cloud!
Once you have done that, run this: https://github.com/richardanaya/wasm-service, for better offline experience
- GitHub - richardanaya/wasm-service: HTMX, WebAssembly, Rust, ServiceWorkers
- Wasm-service: Htmx, WebAssembly, Rust, ServiceWorker proof of concept
- Htmx, WebAssembly, Rust, ServiceWorker Proof of Concept
What are some alternatives?
html-template-lite - Simple template with html code escape
htmx - </> htmx - high power tools for HTML
Flask-Plotly - Interactive Web Apps and Dashboards
htmx-playground - A simple code sandbox for playing around with HTMX. No setup needed!
Fastest-Website - The fastest website, easily beats all competitors & will never be beaten!
yew-beyond-hello-world - yew rust tutorial
wisdom - Building better developers by specifying criteria of success
axum-browser
django-htmx - Extensions for using Django with htmx.
submillisecond - A lunatic web framework
webcomponents - Web Components specifications
grav-theme-wheat - Wheat for Grav CMS