3 ms·
> dynamically loaded modules, error boundaries In an MPA, modules https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules https://developer.mozil
by mozey 3y ago
> dynamically loaded modules, error boundaries
In an MPA, modules https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guid... can be included on the pages that require them with a script tag. Errors (and new features) are limited to a specific page, and the rest of the site remains unchanged.
> suspense (or another form of components loading their own data)
The htmx lib https://htmx.org/ https://htmx.org/ mostly takes care of this: "gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML". The hx-boost tag can also be used for progressive enhancement.
> as soon as you need the bloat you’re just reinventing a wobbly wheel without one
When building a rich client, using a framework could be productive. For example a photo/video editor app. For a news site and CMS I would probably stick to the approach I've described above.
- chasd00 3y agodoesn't the csp issue in htmx basically make it a non-starter for most applications? maybe that's been fixed somehow..
- mozey 3y agoThe hx-disable attribute can be used to disable htmx for parts of the DOM that load user generated content, is that what you're referring to? https://htmx.org/docs/#security https://htmx.org/docs/#security