# dashersw/gea

A batteries-included, reactive JavaScript UI framework. No virtual DOM. Compile-time JSX transforms. Proxy-based stores. Surgical DOM patching.

Repository: https://github.com/dashersw/gea
Canonical: https://ross.abutalabs.com/products/gea
Homepage: https://geajs.com
Language: JavaScript
License: MIT
License Family: permissive
Topics: components, javascript-framework, reactivity, ui-framework, web-development
Last push: 2026-08-18T12:26:34+00:00

## Health v2 (maintenance only)
Score: 74/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 98, release rhythm 78, longevity 12
- inputs: {"age_days": 168, "days_push": 15, "days_rel": 66, "gap_med": 0.0, "n_releases_24m": 81}
- flags: young
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1234, forks 47 (observed 2026-08-28T04:04:04.764213+00:00)

## What it is
Gea is a compiler-first reactive JavaScript UI framework that transforms JSX at build time into surgical DOM patches, eliminating the virtual DOM and runtime diffing. It uses proxy-based class stores and ships extremely small bundles (121 B brotli hello-world), with a built-in router, accessible UI components, and Vite integration.

## Use cases
- build a reactive web app without a virtual DOM
- compile JSX to minimal JavaScript bundles
- manage state with plain JavaScript classes and proxies
- create a tiny hello-world or todo app with minimal JS payload
- build a SPA with a tree-shaken client-side router
- use accessible headless UI components in a lightweight framework
- avoid hooks and signals in frontend development

## When to choose
- you want the smallest possible JavaScript bundle for a UI app
- you prefer plain JavaScript classes over framework-specific primitives like hooks or signals
- you need fine-grained, compile-time DOM updates without diffing overhead
- you want a batteries-included toolkit with router and accessible components
- you are building with Vite and want a compiler-integrated framework

## When to avoid
- you need a mature ecosystem with large community, libraries, and hiring pool
- your team relies on React, Vue, or Svelte tooling and experience
- you need server-side rendering or SSR-first features
- you require long-term stability guarantees from a battle-tested framework
- your project depends on React-specific libraries or components

## Facets
- artifact type: framework
- maturity: active
- function: frontend-framework, ui-components, templating, state-management, routing
- domain: web-development, frontend
- platform: cross-platform
- tags: reactive-ui, compile-time-jsx, no-virtual-dom, proxy-stores, vite-plugin, fine-grained-reactivity, javascript, nodejs, web-server

## Member repositories
- dashersw/gea (main) score 74

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:04.764213+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T08:22:09.870378+00:00, confidence not recorded.
  - readme: https://github.com/dashersw/gea (fetched 2026-08-28T04:04:04.764213+00:00, sha 8b98fca706c9)
  - homepage: https://geajs.com (fetched 2026-08-29T12:21:37.083075+00:00, sha b916bf57a553)
  - site_page: https://geajs.com/docs (fetched 2026-08-29T12:21:37.086534+00:00, sha fabf8fc670c0)
- Data as of 2026-08-30T08:39:29.467469+00:00.