# Updating dependencies from the pallete

**URL:** <https://discourse.nodered.org/t/updating-dependencies-from-the-pallete/19201>\
**Category:** General\
**Created:** [15 December 2019 20:56 UTC](https://discourse.nodered.org/t/updating-dependencies-from-the-pallete/19201 "2019-12-15T20:56:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxwellhadley](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/maxwellhadley/32/7827_2.png) [@maxwellhadley](https://discourse.nodered.org/u/maxwellhadley)\
**Post date:** [15 December 2019 20:56 UTC](https://discourse.nodered.org/t/updating-dependencies-from-the-pallete/19201/1 "2019-12-15T20:56:29Z")

</div>

I have just updated node-rfxcom, which is a dependency of node-red-contrib-rfxcom. What is the preferred way to update the dependencies of a pallet installed node? (and their dependencies, etc)

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [15 December 2019 21:23 UTC](https://discourse.nodered.org/t/updating-dependencies-from-the-pallete/19201/2 "2019-12-15T21:23:37Z")

</div>

In general the "outer" node (eg node-red-contrib-rfxcom) would need to bump its dependencies and its version number and be pushed to npm. When the user then updates that node it would then drag in the dependency.

---

<div class="post-metadata">

**Author:** ![maxwellhadley](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/maxwellhadley/32/7827_2.png) [@maxwellhadley](https://discourse.nodered.org/u/maxwellhadley)\
**Post date:** [24 December 2019 18:25 UTC](https://discourse.nodered.org/t/updating-dependencies-from-the-pallete/19201/3 "2019-12-24T18:25:58Z")

</div>

OK - I just wondered if there might be an equivalent of `npm outdated`, but it seems not.

Version 2.9.1 of `node-red-contrib-rfxcom` just published!