4 ms·
I think I've finally seen the light when it comes to Web Components: https://github.com/kennyfrc/cami.js https://github.com/kennyfrc/cami.js > No Build Steps,
by hu3 3y ago
I think I've finally seen the light when it comes to Web Components:
https://github.com/kennyfrc/cami.js https://github.com/kennyfrc/cami.js
> No Build Steps, No Client-Side Router, No JSX, No Shadow DOM. We want you to build an MPA, with mainly HTML/CSS, and return HTML responses instead of JSON. Then add interactivity as needed.
> Declarative templates with lit-html. Supports event handling, attribute binding, composability, caching, and expressions.
- sibit 3y agoFor me, that's the beauty of Web Components. You can find (or build) a base class that works the way you need it. I like a React class component style class with an XState-inspired state machine built in. https://github.com/codewithkyle/supercomponent/blob/master/src/supercomponent.ts https://github.com/codewithkyle/supercomponent/blob/master/s...
- gen220 3y agoHave you tried HTMX before? Seems strongly aligned, with HTMX perhaps having a bigger community. Curious if you have, and found it lacking in some way.
- Sammi 3y agoThe Cami page already mentions htmx. ctrl+f htmx "For folks who have an existing server-rendered application, you can use Cami to add interactivactivity to your application, along with other MPA-oriented libraries like HTMX, Unpoly, Turbo, or TwinSpark."
- troupo 3y agoReplace JSX with a custom non-standard DSL, call it a win.
- meowtimemania 3y agoIt's a win because it means no build step. You could also say that JSX is a custom, non-standard DSL.