# Backward compatibilty (and embedded systems)

**URL:** <https://discourse.nodered.org/t/backward-compatibilty-and-embedded-systems/49671>\
**Category:** Developing Nodes\
**Created:** [12 August 2021 21:09 UTC](https://discourse.nodered.org/t/backward-compatibilty-and-embedded-systems/49671 "2021-08-12T21:09:02Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [13 August 2021 05:37 UTC](https://discourse.nodered.org/t/backward-compatibilty-and-embedded-systems/49671/6 "2021-08-13T05:37:31Z")

</div>

@drmibell :You can very easily install an old docker image, for a specific version of Node-RED/NodeJs. Then you are up and running in no time... However the first time that I had to that, I have spend quite some time (see [here](https://discourse.nodered.org/t/debugging-nodejs-in-node-red-docker-container/21370)) to get my server side debugging up and running. But I quitted using Docker, because every thing I wanted to do worked differently in Docker. So do to a lack of time I quitted using Docker, although imho it would have been much better for my node developments...

> [@TotallyInformation](#):
>
> I use VScode with ESLINT set to a specific version of JavaScript to try and avoid making mistakes

Sounds very good. Unfortunately I quitted using VScode after a series of troubles to get it up and running. But this would also have been much better for my node developments.

Like I said before: I am not a software company that has lots of time and resources...

---

_[View the full topic](https://discourse.nodered.org/t/backward-compatibilty-and-embedded-systems/49671)._