Projects made in 0.2 are upgraded when you open them, there is a new Styles panel, and your backend has its own page in the browser.
New
- Your project is upgraded when you first open it. 0.3.0 stores text styles as typography
tokens. The first time you open a project made in 0.2, NodeGX copies the whole project folder to
<project>.before-0.3, converts its text styles, and shows a message saying it did. If the copy cannot be made, the project opens unchanged and NodeGX tries again next time. - Library parts are converted too. A part you install that uses text styles is converted in the same way, so it arrives styled.
- Styles panel. Your project's colours, tokens and Looks are in one panel in the left rail, under Components.
- Looks. A Look is a saved style for one kind of node. Style a button, save it as a Look, and use it on your other buttons.
- Visual editors for shadows, gradients, animation timing and fonts. Use sliders and lists instead of typing CSS. "Show CSS" shows the code if you want it.
- Tokens show where they are used. A token in a field shows as a chip with its name. Each token has a "Used by" list of the nodes that use it.
- Every property row says where its value comes from: you, a Look, or the default. Reset says what it will reset to.
- Properties have their own column on the right.
- Layers tab. Components and Layers are two tabs. Layers shows what the previewed page is made of, and you can drag items to rearrange them.
- The canvas and the preview highlight each other. Hover or select a node and the same element is outlined in the preview, and the other way round.
- A note in the preview when the component you are editing is not on the page it is showing.
- Boards. Lay several components out side by side. The board keeps its layout.
- Repeat node. Does something every few seconds.
- Parse Feed and Parse XML nodes. Read an RSS or Atom feed, or any XML, into a list.
- Model Request node (cloud functions). Sends a prompt to Claude and returns the answer. The OpenAI-compatible option is listed but does not work yet.
- Drag and drop on Group, Text, Image, Circle and Video.
- Text Input can ask for a number keypad on phones and set the label of the Enter key.
- Game Kit module in the library: sound, an avatar, a race track, an on-screen keyboard and an answer pad.
- The backend can run on PostgreSQL.
nodegx-backend migratemoves an existing backend over. - Collections can have indexes, unique fields, and rules every row must pass.
- "Only If Unchanged" writes, so two people saving at once do not overwrite each other.
- Schedules can skip a run while the previous run is still going.
- Your backend has an MCP address (
/mcp) that Claude or another app can connect to with an API key. An API key can belong to one user. - The backend manager. Your backend is run from its own page in the browser, opened from the Backend card in the editor. You pick and tick things there instead of typing JSON, lists or schedule codes. It works in light and dark, and every page has its own link.
- Collections: filter rows, sort by a column, choose columns, save views, edit each field with a control for its type, see who can see a record, and import a CSV file.
- Schema: choose one of eleven kinds for a field, and set rules the backend enforces, such as a list of choices, a maximum length or whole numbers only. If you add a required field to a collection that already has records, you give one value to fill them with.
- Users and roles: people are shown by name. You can turn off someone's sign-in, and add people to a role by searching or pasting email addresses.
- Permissions: a grid of who can do what in each collection, with ready-made templates, and Try it as to check a rule as a particular person.
- Triggers: build a schedule by picking options and see its next five runs. A webhook shows its address, and shows its secret once.
- Workflows and runs: run a workflow from a form, watch runs live, and cancel one that is running.
- Email and sign-in: choose an email provider from a list, edit each email with a preview, and set up a sign-in provider step by step.
- Files and backups: browse uploaded files and see which records use them, and restore a backup. Uploads and backups can be kept in an S3-compatible bucket instead of on the server's disk, with a Test connection button.
- The first admin is a person. The first time you open the backend manager, it asks you to
choose an admin email and password. That account signs in to the manager, and to your own app
with the
adminrole. From the Users page you can give other people full or look-only access. - Code export: Looks and text styles now export. Before, they were left out.
- Code export: popups export as dialogs.
Changed
- Text styles are now typography tokens. A Text node picks tokens and no longer creates text styles.
- The Preset / Size picker is gone. Nodes that used a preset keep their look. Save it as a Look to reuse it.
- Sheets are gone. Folders whose names began with
#show as ordinary folders. - Show Popup opens a real dialog. Escape closes it, keyboard focus stays inside it, and the page behind cannot be clicked.
- Buttons and form controls show a focus ring when you reach them with the keyboard.
- Emailed sign-in links open a page with a button. Pressing the button signs you in. Before, the link signed you in straight away, so a mail scanner could use it up.
- The backend panels have left the editor. Data, schema, sign-in, email, permissions, search, secrets and triggers are all in the backend manager. Add a field and the canvas's Add / Edit this trigger… open the right page there, already signed in.
- The backend returns
trueandfalse, not1and0. - A query with no limit returns at most 1,000 rows, and the reply says it was cut short.
- A redesigned editor: one type scale, consistent corners and shadows, a new properties panel, and a Templates tab with pictures. The editor loads one font file instead of six.
- Twelve nodes are marked as not exportable on the picker card and in the properties panel. Parse Feed and Parse XML say "Not exportable yet".
Fixed
- A limited API key could read sessions, users, other keys and the audit log. It can't now. If you gave anyone a limited key, update.
- A backend request retried after 0.2.4 had already answered it could run twice. This is fixed the first time the new backend starts.
- The launcher could open the wrong project when two projects had the same id.
- All 78 "Read docs" links on library cards were broken.
- Font size and spacing fields now offer your tokens.
- The colour picker now lists all your colour tokens.
- Saving an empty object to the backend failed.
- Some records came back from the backend changed.
- States colour transitions now work with tokens.
- Presets now load their fonts.
- Pictures in exported apps load on pages two levels deep.
- The editor no longer sends a broken request to GitHub when you have never signed in.
- The editor logs far fewer background errors.
Good to know
- Keep the
.before-0.3copy until you are happy with the upgraded project. It is the only copy that 0.2 can still open. - Code export is still in alpha. A few projects still stop the export with an error. If yours does, please report it and attach the project.
- The
nodegxcommand-line export tool is not on npm yet.npm i -g @nodegx/exportdoes not work. Export from the editor instead. - Windows installers are not signed, so SmartScreen will warn you. Choose More info, then Run anyway.
- If you use the MCP server with an assistant, restart the assistant's session after updating.