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	9349
title	build: Fix dirent.path resolution and OS-agnostic pathing in esmodules.mjs
state	Closed
labels	bugwindowsaibuild
assignees	tobiu
createdAt	Feb 28, 2026, 1:18 PM
updatedAt	Feb 28, 2026, 1:19 PM
githubUrl	https://github.com/neomjs/neo/issues/9349
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 28, 2026, 1:19 PM

build: Fix dirent.path resolution and OS-agnostic pathing in esmodules.mjs

Closed v12.1.0/archive-v12-1-0-chunk-1 bugwindowsaibuild

tobiu commented on Feb 28, 2026, 1:18 PM

Describe the bug A bug was reported indicating that dirent.path is problematic on Windows within @buildScripts/build/esmodules.mjs.

Cause In older versions of Node.js or in specific environments, fs.Dirent objects might not uniformly expose .path (they sometimes use parentPath or missing it completely). Furthermore, relying on exact directory name matching via if (dirent.name === 'resources') combined with nested manual traversals creates brittle path resolutions when dealing with cross-platform slashes (e.g. \ vs /).

Solution

Fallback gracefully: const currentPath = dirent.parentPath || dirent.path;
Normalize all paths before inspection to / so string matching is OS-agnostic: .replace(/\\/g, '/').
Refactor the minifyDirectory to evaluate file-by-file recursively rather than doing an awkward combination of file reading and directory copying inside a single conditional block. This removes the need to parse the outputPath to find JSON files within a copied directory.
Add a safeguard to only minify ServiceWorker.mjs if it actually exists in the root directory.

tobiu Feb 28, 2026, 1:18 PM

Input from Gemini 3.1 Pro:

✦ Fixed the path resolution for Windows and simplified the logic in the latest commit on dev.