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	9584
title	Bug: Data worker broadly bundles non-data framework classes (Main.mjs) causing Webpack build failure
state	Closed
labels	bugaiperformancebuild
assignees	tobiu
createdAt	Mar 27, 2026, 3:06 PM
updatedAt	Mar 27, 2026, 3:18 PM
githubUrl	https://github.com/neomjs/neo/issues/9584
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 3:18 PM

Bug: Data worker broadly bundles non-data framework classes (Main.mjs) causing Webpack build failure

Closed v12.1.0/archive-v12-1-0-chunk-3 bugaiperformancebuild

tobiu commented on Mar 27, 2026, 3:06 PM

The webpackInclude regex for Data.mjs previously captured the entirety of the src/ directory (/(?:apps|docs\\/app|examples|src)\\/.*\\.mjs$/). This massively bloated the Data worker's dynamic chunk map with thousands of UI components, main thread controllers, and build loaders.

When Webpack traversed the map and compiled src/Main.mjs, it crashed upon hitting the main-thread workspace addon resolution (import('../../../src/main/addon/')), throwing Module not found: Error: Can't resolve '../../../src/main/addon'. Additionally, it threw critical dependency warnings on src/MicroLoader.mjs.

By restricting the framework source match in Data.mjs to exclusively target src\\/data instead of all of src/, we pruned thousands of invalid classes from the Data worker's chunk map, removing the compilation crashes and massively optimizing build performance.