0.2.3

NodeGX 0.2.3 — alpha

The release where the field report got answered. Two dozen issues came in from people
using NodeGX in the field — a wire that did nothing, a Linux installer that would not start,
a preview server listening on the whole network. One of them had been open since April 2025. This release is mostly those reports, fixed on the
product surface rather than worked around. It is also 25 MB smaller and a good deal quieter.

📖 Read the full changelog, in plain language →

Fixed, from your issue reports

• #26 — a wire into a size port arrives. One word — type where the code meant unit — had kept a value conversion dead for every dynamically registered size port since the initial commit. A port sent something that isn't a size now says so instead of discarding what you authored.
• #31 — the preview server binds to localhost and no longer hands out its own access token. If you ran 0.2.2 on a shared network, this is the reason to update.
• #29 — Linux installs on a current distribution. FUSE 3 works, Chromium's sandbox is back on, launching without a display no longer dumps core, and there is an .rpm for Fedora/RHEL/openSUSE.
• #21 · #22 — Columns measures itself, publishes Breakpoint / At Medium / At Small, and ships an Advanced Columns part with four bands.
• #40 — page checks are 5.2× faster (11 pages: 53.8s → 10.3s) and can write screenshots to disk. The report had also been dropping console errors logged during page load; it no longer does.
• #42 — smaller and quieter. It was shipping 85 MB of unusable source maps and running an invisible spinner forever. App bundle −40.7%, download 185 → 160 MB, idle CPU 2.42% → 0.14% of a core.
• Also fixed: #5, #14 (a refusal is reported as a refusal, not a plausible total), #32, #33, #35, #37, #41.

Your app leaves the editor, from a terminal

The whole export-and-ship path is a command-line tool now — no editor window, so it fits in CI
and an assistant can drive it end to end. npm i -g @nodegx/export gives you nodegx:

nodegx export <project> <output>   Export a project as a React app
nodegx export --dry-run <project>  Print what the export would produce, and write nothing
nodegx deploy <project> <output>   Write a ready-to-host site you can upload as it is
nodegx serve <folder>              Serve a built site over HTTP, on this machine only
nodegx render <project>            Render every routed page and say which ones did not
nodegx live <url>                  Read a site that is being served and say which build it is

A second deploy to the same place is an update rather than a fresh copy, @nodegx/core is on
npm so the exported README's npm install resolves, and cloud functions deploy without a window.

New

• Building with an assistant. An assistant can open a project without anyone touching the launcher, ask whether a human already has it open before writing to it, export to React itself, and find out which ports won't survive export before designing around them. The editor no longer overwrites what an agent wrote.
• A shelf it can search. The parts library can be browsed, asked what a part actually does, and installed — by you or by an assistant — instead of being a folder nobody is pointed at.
• Coming from Bubble. A phrasebook of 94 Bubble operators in Bubble's own vocabulary with the NodeGX answer beside each. Eight ship as graphs you can open and run.
• 37 new worked examples, 67 → 104. Twelve are real apps built by the original Noodl community; the rest cover cloud functions and auth, the four component patterns nothing previously demonstrated, media, layout and logic. The 26 node types with no example now have one.
• New parts — Advanced Columns (four responsive bands), a date formatter, a full-name formatter, an email sanitiser, plus a charts kit (Bar Chart + Sparkline, and they survive export) and a media recorder.
• Search-engine and social tags on the Page node, so a shared link previews properly.
• Landing pages, extended — filterable work, rows that open, a price switch, and a contact form that says what will happen before you press Send.

Before you file a bug

• ⚠️ One behaviour change. Because of #26, wires that were previously accepted and then silently ignored now take effect. A layout that looks different after updating is almost certainly a wire that was always meant to do something.
• Code export is still alpha. The report names every node it left out and why. Explore the output; don't ship a production app straight out of it yet.
• Windows installers are unsigned and SmartScreen will warn. macOS is signed and notarised.
• Linux is install-only — download the next AppImage to update.