The library, the website, the submission title, and even the comments by the author here, all written with AI. Sloptastic!

   type ProfileSpec = Frond.NodeSpec<{
     readonly args: Frond.Args.None;
     readonly key: Frond.Key.Singleton;
     readonly deps: {
       readonly http: Frond.Dep<typeof HttpTransportNode>;
     };
    readonly result: Profile;
   }>;

What's the advantage of this over Jotai / atomic state / computed signals, which seems to require 10× less code with mostly the same benefits?

Interesting approach.The lifecycle management and teardown story seems to be the main differentiator rather than state itself.How does Frond compare to Effect's Layer system? Is it essentially bringing Layer-like dependency graphs into the React runtime?

How does Frond handle cyclic dependencies? Is cycle detection built into the runtime, or is it left to the developer?

If I see this code in a new company I just joined I am quitting on day 1

I built Frond, a frontend runtime that makes your app's dependency graph explicit instead of leaving it scattered across provider order, enabled: user && api.ready guards, and logout teardown scripts.

The shape: your app is a graph of nodes — services, resources, screens. Each node declares its dependencies, how it's acquired, how it's cancelled, and how it's released, all in one place. The runtime resolves them in dependency order and tracks readiness, so React stays a renderer — it consumes a node that's already ready (useNode suspends until it is) instead of re-deriving that logic inside components.

Two engines run underneath. Effect handles the async work — execution guarantees, cleanup correctness, cancellation, and typed error channels. MobX handles state — granular observable state and live updates. You declare a node's dependencies, acquire, and release; Frond runs the rest on those two.

It's v0 and the API will still move.