# Node-RED 0.20.0-beta.5 released

**URL:** <https://discourse.nodered.org/t/node-red-0-20-0-beta-5-released/7739>\
**Category:** News\
**Created:** [8 February 2019 11:36 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-5-released/7739 "2019-02-08T11:36:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [8 February 2019 15:28 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-5-released/7739/2 "2019-02-08T15:28:21Z")

</div>

Happy to report that the "Max call stack size exceeeded" reported in [beta-4](https://discourse.nodered.org/t/node-red-0-20-0-beta-4-released/7339/2?u=juzam) is now fixed.

The other problem I had, is somewhat still present but I'm not really sure if it's a bug or not.

Basically I have a mix of node packages installed "by hand" and via palette manager, so my `package.json` didn't reflect the whole list of my installed nodes.  
The so called bug, is that, if I try to update a package (tried with the dashboard, which was present in the package json) the palette manager wipes from the file system the nodes not listed in the package.json file.  
After that of course node-red doesn't find the necessary nodes simply because they are just gone.

I think that didn't occurre with 0.19.x (sorry but I didn't try to reproduce with the old version but I will do if it's helpful)

edit: i've forgot to say that the problem is not present, if you have all your installed nodes listed in `package.json`

---

_[View the full topic](https://discourse.nodered.org/t/node-red-0-20-0-beta-5-released/7739)._