Let's discuss the split of the editor and the runtime! The WIP spec is in the github wiki: Editor Runtime API As of late April 2018 there's also a runtime-api branch for the work in the repo. And here's a quick quote of my "imagining a possible future" post from slack on April 13, 2018: editor…

Thanks for starting the topic @towynlin . Let me start with a status update on where I've got to with the runtime-api branch. The work in that branch has been focussed on teasing apart the internals of the node app that is Node-RED to provide as crisps separation as possible between logical componen…

[image] knolleary: In a novel approach, I’ve been documenting the API as I go (having added jsdoc to the build process) - you can see the full API as it currently stands here . I say Nick, steady on old chap :slight_smile: Most of this is outside my skill-set by quite a way but I get the gist…

Thanks for this great writeup. My unsolicited opinion: If breaking the require('node-red') API is necessary for NR to move forward, it should be done at v1.0.0. If we’re just procrastinating, then let’s not procrastinate. However, I’m curious about who/what is consuming this API–this sounds like …

I came across this document on experience with lerna that may be useful, and related document on Alle approach. Seems mainly applicable for large mono-repos. Thought it was interesting how one can avoid the bootstrapping step by putting packages in node_modules instead of packages.

Given our reasonably positive experience with proxying all current Node-RED endpoints en-masse including web sockets, and the simplicity of the approach, I suggest you start with 1.b. for the node http routes issue. Glad to provide code snippets/refs on how we did this although no rocket science th…

The Alle approach doesn’t work with all tools; unfortunately, Grunt is one of the tools it doesn’t work with. Sorry, rather I meant lerna --hoist. Either way, Lerna seems to work well enough for our purposes.

One thing I think needs to be in this API, separate out the logic of building graphs from the UI app. Noflo has the useful element of being able to add by API links between nodes, and create the whole graph from API and this could greatly help node red. This would make life a lot easier for those do…

Interesting idea. I don’t think it’s the right topic to discuss here though. Might be worth opening a ‘feature request’ sub topic around this. The topic here is called Editor Runtime API but I think it might be better called Editor Runtime Split. Happy to discuss my experience implementing a cust…

:+1: Agreed — changed the topic name. :bow:

Alright @mike , I've added a thread here. [image] How to create a new UI from scratch General So I’m working on a project and need to create a new editor UI to create flows from scratch. @mike said he has done it in another thread and I’m wondering how to do it with existin…

Node-RED

Node-RED Forum

Editor Runtime Split

Core Development

aoighost 30 May 2018 01:20 11

Alright @mike, I've added a thread here.

Topic		Replies	Views
Re-purpose the flow editor for other flow-like data editing General	12	2345	7 December 2023
Design: Runtime Editor Split General	3	1538	24 May 2019
Is there a way to modify the editor UI or to provide an alternative one Feature Requests	28	1651	5 August 2021
New Node-RED Editor? Core Development editor	35	758	17 February 2025
Source code of node red General	34	494	12 October 2025

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Editor Runtime Split

Related topics