Skip to content
When not to use Aegis
- A single-page application with client-side routing for everything. Aegis has a router, but its home is a server that renders pages; if the server only serves JSON, a SPA framework fits better.
- A team that lives in JSX and the React ecosystem. Storybook, React Native, thousands of components: those are not Aegis, and they are not coming.
- A dropdown or a tab strip on a static page. Alpine or Petite-Vue is smaller and enough.
- Every state rendered by the server. If htmx alone covers the page, add Aegis only for the islands that need client state.
- Browsers without ES modules. Aegis ships as an ES module; there is no ES5 build.
Edit this page on GitHub