Skip to content

The dev server grows up

Latest

Choose a tag to compare

@hugithordarson hugithordarson released this 03 Sep 16:38
· 6 commits to master since this release

The dev server grows up

A summer of work on the built-in dev server (localhost:9485) — the HTTP surface that lets external tools and AI agents drive Eclipse. It now reports what actually happened, not just that a command was relayed: /status (what's running, per launch config), /console (a launch's output, kept after the process dies), /launch with preflight refusals and waitForPort, /restart, /openProject (a project plus its workspace dependencies), /problems, /breakpoints, and a self-describing index at /. /refreshProject returns a build report instead of ok when the build produced errors.

Ask the editor what a tag can do

/elementApi returns any element's resolved binding API as JSON — types, direction, required, defaults, cross-binding rules with their plain-English messages — the editor's hover, as data. Validation also gained a check for the $-on-a-plain-tag trap. Paired with runtime-side eval and problems endpoints in ng-objects and wonder-slim.

Trustworthy markers

Revalidate All Templates (a preference-page button and /revalidate) re-runs template validation over a project or the whole workspace, and Purge Stale Markers (/purgeMarkers) deletes orphaned markers left by validators that no longer exist. /problems labels every marker with its source. Along the way: the standalone JS/CSS editors and their ancient validation engines are gone (Eclipse owns those files; inline blocks in templates keep highlighting and completion), and the plugin's embedded libraries were brought current.

Watch your agent work, live

The dev server records every request it handles, and /watch turns that into a live, narrated feed (“Validated Main — clean”, “Launched MyApp — ready in 4.2s”) with a running tally. /activity serves the same record as JSON — an audit trail of what an agent actually did to your workspace.

Launches that can't stop the world

Eclipse's “Errors exist in required project(s). Proceed?” dialog can no longer strand an agent: /launch checks the app and every project it depends on, refuses with the broken projects and the fix, and launches with Eclipse's prompting switched off. For every other modal, /dialogs lists them and can press a button — and a launch that's waiting for the app returns at once if one appears.

From the changelog, August 29, 2026.