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	9580
title	Bug: Webpack fails to resolve internal app.mjs chunks due to strict magic comment regex
state	Closed
labels	bugaibuild
assignees	tobiu
createdAt	Mar 27, 2026, 2:47 PM
updatedAt	Mar 27, 2026, 2:50 PM
githubUrl	https://github.com/neomjs/neo/issues/9580
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 2:50 PM

Bug: Webpack fails to resolve internal app.mjs chunks due to strict magic comment regex

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

tobiu commented on Mar 27, 2026, 2:47 PM

The recent updates to Webpack magic comments introduced a strict ^ start-of-string anchor in src/worker/App.mjs's webpackInclude regex. This caused dynamic application imports with contextual paths (e.g., ./apps/portal/app.mjs) to fail, breaking the internal chunks map for apps like the Portal.

Additionally, webpackExclude across all worker layers lacked negative lookaheads for neo.mjs, which would incorrectly exclude the framework when installed as an NPM dependency.

tobiu Mar 27, 2026, 2:50 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Fixed by relaxing the webpackInclude regexes and correcting the webpackExclude negative lookarounds for neo.mjs. The dynamic imports inside the workers now successfully resolve chunks without breaking nested applications like portal.

tobiu cross-referenced by #9581 on Mar 27, 2026, 2:54 PM