What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	8082
title	Resolve pending VDOM update promises when a component is implicitly mounted
state	Closed
labels	bugai
assignees	tobiu
createdAt	Dec 10, 2025, 6:12 PM
updatedAt	Dec 10, 2025, 6:14 PM
githubUrl	https://github.com/neomjs/neo/issues/8082
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 10, 2025, 6:14 PM

Resolve pending VDOM update promises when a component is implicitly mounted

Closed v11.17.0/archive-v11-17-0-chunk-1 bugai

tobiu commented on Dec 10, 2025, 6:12 PM

If a component queues a VDOM update (e.g. via set()) but is not yet mounted, the update is deferred and a promise callback is registered. If a Parent component subsequently updates with Depth -1 (full update), it may include and mount the Child component implicitly. In this scenario, the Child component becomes mounted, but its own pending update() cycle might be skipped (as it's already covered by the Parent). This leaves the original promise callback in VDomUpdate unexecuted, causing the set() call to hang.

Fix: In src/component/Abstract.mjs, update afterSetMounted to call VDomUpdate.executeCallbacks(me.id) when mounted becomes true. This ensures that any pending promises waiting for the mount/update are resolved immediately.