What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

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

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9599
title	Webpack path resolution bug for Data worker dynamic imports in workspaces
state	Closed
labels	bugai
assignees	tobiu
createdAt	Mar 30, 2026, 12:51 PM
updatedAt	Mar 30, 2026, 1:02 PM
githubUrl	https://github.com/neomjs/neo/issues/9599
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 30, 2026, 1:01 PM

Webpack path resolution bug for Data worker dynamic imports in workspaces

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closedbugai

tobiu commented on Mar 30, 2026, 12:51 PM

Description When running npm run build-all inside a workspace (e.g., generated by create-app), Webpack throws "Module not found" warnings when trying to process dynamic imports for connection, parser, and normalizer modules inside Neo.worker.Data.

WARNING in ./node_modules/neo.mjs/src/worker/Data.mjs 131:26-136:21
Module not found: Error: Can't resolve '../../../data/connection' in '/Users/tobiasuhlig/Desktop/workspace/node_modules/neo.mjs/src/worker'

Root Cause The ContextReplacementPlugin in the Webpack worker configurations blindly prepends ../../ to dynamic import requests inside /src/worker when insideNeo is false (in a workspace context), unless the request already starts with ../../. Because the internal Data.mjs imports use ../data/connection/${name}.mjs, the plugin incorrectly transforms ../data/connection to ../../../data/connection, breaking the resolution.

Resolution Update the ContextReplacementPlugin logic across all appworker and worker Webpack configs (Development and Production) to also exclude requests starting with ../data/, preserving the internal framework paths while still correctly redirecting external workspace paths.

tobiu added the bug label on Mar 30, 2026, 12:51 PM

tobiu added the ai label on Mar 30, 2026, 12:51 PM

tobiu referenced in commit 5723fde - "fix(build): Fix Webpack ContextReplacementPlugin path resolution for Data worker dynamic imports within external workspaces (#9599)" on Mar 30, 2026, 1:01 PM

tobiu closed this issue on Mar 30, 2026, 1:01 PM

tobiu Mar 30, 2026, 1:01 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ The path resolution bug for Data worker dynamic imports in external workspaces has been fixed.

Issue: The ContextReplacementPlugin in the Webpack worker configs was incorrectly prepending ../../ to framework-internal data paths (e.g., ../data/connection/...), resulting in broken ../../../data/... imports in workspace builds.

Fix: Added a surgical exclusion to the plugin logic (&& !context.request.startsWith('../data/') and && !context.request.startsWith('..\\data\\')) across all four development and production appworker/worker configuration files.

Framework paths now resolve correctly as-is within node_modules, while falling back to workspace path prefixing for other non-exempt relative imports.

tobiu assigned to @tobiu on Mar 30, 2026, 1:02 PM