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	467
title	ES2020: Add optional chaining once possible (Webpack issue)
state	Closed
labels	enhancement
assignees	[]
createdAt	Apr 13, 2020, 12:43 PM
updatedAt	Jun 28, 2021, 10:39 AM
githubUrl	https://github.com/neomjs/neo/issues/467
author	tobiu
commentsCount	4
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 28, 2021, 10:39 AM

ES2020: Add optional chaining once possible (Webpack issue)

Closed v2.2.47/archive-v2-2-47-chunk-1 enhancement

tobiu commented on Apr 13, 2020, 12:43 PM

In short:

const obj = {
  prop1: {
    prop2: {
      prop3: {
        prop4: {
          prop5: 5
        }
      }
    }
  }
}

obj.prop1 &&
  obj.prop1.prop2 &&
  obj.prop1.prop2 &&
  obj.prop1.prop2.prop3 &&
  obj.prop1.prop2.prop3.prop4 &&
  console.log(obj.prop1.prop2.prop3.prop4.prop5);

const obj = {
  prop1: {
    prop2: {
      prop3: {
        prop4: {
          prop5: 5
        }
      }
    }
  }
}

console.log(obj?.prop1?.prop2?.prop3?.prop4?.prop5);

This can some boiler-plate code, but unfortunately, webpack can not handle it yet. Browsers already support it, but webpack wants to parse it.

ERROR in ./apps/covid/view/TableContainerController.mjs 191:37 Module parse failed: Unexpected token (191:37) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders | } |
    me.loadHistoricalData(record?.countryInfo?.iso2 || 'all');

Since Babel is not an option for neo, we need to wait for this PR:

https://github.com/acornjs/acorn/pull/891

(Webpack relies on acornjs)

tobiu added the enhancement label on Apr 13, 2020, 12:43 PM

tobiu referenced in commit 2531822 - "Covid.view.TableContainerController: removed optional chaining again for now, see #467" on Apr 13, 2020, 12:55 PM

tobiu Apr 13, 2020, 1:03 PM

https://caniuse.com/#search=optional%20chaining

dreyks Jun 11, 2020, 9:46 AM

https://github.com/acornjs/acorn/pull/891 is merged, let's keep an eye on the releases

tobiu Jun 11, 2020, 10:17 AM

Thanks for the heads up!

There are probably many spots inside the neo.mjs framework & demo apps code base where we can use it. Optional chaining can definitely help removing some boiler plate code (smaller file-size) as well as making the spots cleaner & easier to read.

Looking forward to it.

tobiu Jun 28, 2021, 10:39 AM

just double-checked this one again and we are now finally good to use optional chaining.

will create new tickets in case i see spots.

tobiu closed this issue on Jun 28, 2021, 10:39 AM