Next.js Engine v2.0.0 — Runtime Architecture Milestone

Next.js Engine v2.0.0 was the first large architecture milestone after the initial 1.0 release. It introduced server-side mobile schema patching, the EngineScroll runtime, expanded EngineBrowser capabilities, static schema diagnostics, declarative EngineAPI configuration, reusable schema components, and major graphics/runtime improvements.

This file preserves the v2.0.0 release history inside the official documentation tree.

1. EngineMobile — server-side mobile schema patching

v2.0.0 added EngineMobilePatcher, allowing structural mobile changes to be applied to the schema on the server before render.

Key additions included:

• MobileSchemaConfig patch lists;
• non-destructive patching of the desktop schema;
• the stable SchemaNode.name targeting field;
• remove-all-prop and remove-all-cprop patch directives;
• device detection covering major Android/iOS hardware families;
• createPage({ mobile }) integration.

This made it possible to change actual schema structure for mobile requests rather than relying only on client-side layout switching.

Read: ../engine-components/enginemobile.md

2. EngineScroll runtime

v2.0.0 established EngineScroll as an Engine-owned runtime instead of leaving movement entirely to native scroll-behavior.

Key pieces included:

• EngineScrollProvider;
• useEngineScroll();
• EngineScrollPointManager;
• schema point targets;
• the custom #-es? URL protocol;
• programmatic RAF-driven movement;
• URL cleanup after protocol execution.

Later releases expanded this same runtime with timelines, ranges, snapping, tracking, and Directors.

Read: ../engine-components/enginescroll.md

3. EngineBrowser abstractions

The EngineBrowser API grew into several SSR-safe browser capability groups:

• clipboard;
• interact;
• media;
• speech;
• network.

These APIs centralized browser capability access for things such as clipboard operations, share/notifications, file picking, wake locks, geolocation, camera/microphone/screen capture, text-to-speech, speech recognition, and network state.

Read: ../engine-components/enginebrowser.md

4. Static schema diagnostics

v2.0.0 introduced schemaAnalyzer for compiler-style diagnostics over schema trees.

The initial diagnostic family included:

• E001 — unknown/misspelled type with suggestion support;
• E002 — missing required prop;
• E003 — duplicate ids/points;
• E004 — circular references;
• accessibility/performance warning codes.

The analyzer was designed to catch errors before a broken schema reaches normal runtime rendering.

Read: ../schema-diagnostics.md

5. EngineAPI configuration

v2.0.0 introduced the .EngineAPIConfig/*.api configuration system and build plugin.

Major capabilities included:

• centralized provider configuration;
• environment substitution;
• version macros;
• per-provider header overrides;
• authentication modes including API-key, bearer, JWT, basic, HMAC, and PnP-style keys;
• build-time compilation through the Engine API plugin;
• centralized EngineAPIResolver request orchestration.

Read: ../engine-components/engineapi.md

6. New schema/component capabilities

The release added or formalized several higher-level Engine APIs:

• createComponent() for reusable schema-rendered UI with runtime slots;
• local Markdown file loading;
• Markdown heading anchors;
• text/block Markdown animation controls;
• EngineLink;
• EngineHero;
• EngineSuspense;
• EngineForms.

This moved more common application structure into schema-native primitives.

7. EngineCanvas and EngineManim graphics work

v2.0.0 also introduced a much broader graphics architecture:

• pluggable EngineCanvas graphics rendering;
• EC geometry helpers such as ecCircle, ecRect, and ecPath;
• EngineSVG import/export integration;
• 2D/3D scene support;
• Canvas mount/setup race fixes;
• EngineManim timing/freeze fixes;
• more reliable frame lifecycle behavior.

Read:

• ../engine-components/enginecanvas.md
• ../engine-components/enginemanim.md

8. Styling, hydration, and lazy-loading fixes

Important infrastructure changes included:

• deterministic StyleCollector behavior to reduce hydration mismatch risk;
• the staticClass deduplication helper;
• Global / Group / Local style tiers used by the v2.0-era runtime;
• improved lazy-loading decisions for video/images/sections;
• better first-paint sizing and layout behavior.

Some of these internals were later redesigned again in v2.5/v2.6, but v2.0.0 established the direction.

Release links

• GitHub release: https://github.com/Kate-alt-69/nextjs-engine/releases/tag/release-V2-0-0
• Full historical compare: https://github.com/Kate-alt-69/nextjs-engine/compare/release-v1-0-0...release-v2-0-0
• v1.0.0 notes: ./NE-v1-0-0.md
• v2.5.0 notes: ./NE-v2-5-0.md

Historical note

This is an archive of the v2.0.0 release. The current official component documentation should be used for present-day APIs because many v2 systems were expanded and hardened in later releases.