# \#windows-installer

**URL:** https://discourse.nodered.org/tag/windows-installer/77.md

[Latest](https://discourse.nodered.org/latest.md) · [Categories](https://discourse.nodered.org/categories.md) · [Tags](https://discourse.nodered.org/tags.md)

---

## [Custom Node-RED installer for Windows](https://discourse.nodered.org/t/custom-node-red-installer-for-windows/94906)

<div class="topic-metadata">

**Author:** [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Replies:** 8\
**Last updated:** [25 January 2025 16:25 UTC](https://discourse.nodered.org/t/custom-node-red-installer-for-windows/94906 "2025-01-25T16:25:11Z")

</div>

Anyone, this seemed to be a promising start to the issue ?

---

## [Encountering "JavaScript heap out of memory" and Other Issues with Node-RED](https://discourse.nodered.org/t/encountering-javascript-heap-out-of-memory-and-other-issues-with-node-red/86708)

<div class="topic-metadata">

**Author:** [@KittisakC](https://discourse.nodered.org/u/KittisakC)\
**Replies:** 2\
**Last updated:** [24 March 2024 16:19 UTC](https://discourse.nodered.org/t/encountering-javascript-heap-out-of-memory-and-other-issues-with-node-red/86708 "2024-03-24T16:19:24Z")

</div>

Hello Node-RED Community, I've been encountering a "JavaScript heap out of memory" error in my Node-RED environment. This suggests that my flows might be processing too much data at once or possibly have a memory leak. …

---

## [Node-red-windows-installer](https://discourse.nodered.org/t/node-red-windows-installer/77148)

<div class="topic-metadata">

**Author:** [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Replies:** 61\
**Last updated:** [16 May 2023 21:39 UTC](https://discourse.nodered.org/t/node-red-windows-installer/77148 "2023-05-16T21:39:05Z")

</div>

Based on the discussion we had lately ... I've taken the opportunity of a bad weather day to start into this journey: It's not doing anything valuable so far ... but at least it looks nice. Technically it's based…