# Integration of front-end frameworks for custom node editors

**URL:** <https://discourse.nodered.org/t/integration-of-front-end-frameworks-for-custom-node-editors/67645>\
**Category:** Developing Nodes\
**Created:** [13 September 2022 08:12 UTC](https://discourse.nodered.org/t/integration-of-front-end-frameworks-for-custom-node-editors/67645 "2022-09-13T08:12:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VinzenzTrimborn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vinzenztrimborn/32/67702_2.png) [@VinzenzTrimborn](https://discourse.nodered.org/u/VinzenzTrimborn)\
**Post date:** [13 September 2022 08:12 UTC](https://discourse.nodered.org/t/integration-of-front-end-frameworks-for-custom-node-editors/67645/1 "2022-09-13T08:12:13Z")

</div>

I have worked a lot with node-red and wrote a couple of custom nodes. I always aim for a high usability of the node editor. However, it is hard to write nice UIs in the node editor when I have to write JQuery and "plain" HTML to include functionality.

Can someone imagine a way of including React or Vue for the development of the front-end of custom node editors.

This would make it easier to program a custom node editor with a nice UX within the front-end of node-red.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [16 September 2022 10:03 UTC](https://discourse.nodered.org/t/integration-of-front-end-frameworks-for-custom-node-editors/67645/2 "2022-09-16T10:03:36Z")

</div>

I don't think there is any reason you couldn't include those frameworks, especially if you include a build step in your development workflow.

For myself, I split the .html file into 4 components (really 3 plus a master template) and use a simple gulp build/watch to create the actual node html file. I find working with the 3 separate files much easier (JS, config panel and help panel).

So your master template could easily include a reference to REACT, Vue, etc. However, you would either need to use a CDN version (requiring Internet access) or choose a way to install and serve up the framework files on Node-RED's admin web server. Easy enough to do via your node's .js file.

One other thing to bear in mind however. The Editor is already quite a large web app. Adding another framework will increase that further of course.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [30 September 2022 10:03 UTC](https://discourse.nodered.org/t/integration-of-front-end-frameworks-for-custom-node-editors/67645/3 "2022-09-30T10:03:38Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.