# Dashboard-2 custom nodes not loading when installed globally

**URL:** <https://discourse.nodered.org/t/dashboard-2-custom-nodes-not-loading-when-installed-globally/94546>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [12 January 2025 13:35 UTC](https://discourse.nodered.org/t/dashboard-2-custom-nodes-not-loading-when-installed-globally/94546 "2025-01-12T13:35:31Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [13 January 2025 14:01 UTC](https://discourse.nodered.org/t/dashboard-2-custom-nodes-not-loading-when-installed-globally/94546/12 "2025-01-13T14:01:11Z")

</div>

> [@joepavitt](#):
>
> Steve - can you remember the details on that

Unfortunately I dont remember details off the top of my head though I am certain it was something I tried out.

@omrid  
if you NPM LINK your instances to the the global installation then proceed to update the global install, the many instances referencing it will also be updated (because it is a link, not a copy). Alternatively, you could also have a shell script that simply iterates your installations and re-runs the npm link (or full install)

Personally, I don't recommend global installs - even for your use case.

In the mean time, please raise an issue with as much detail and a step by step to reproduce.

Thanks.

---

_[View the full topic](https://discourse.nodered.org/t/dashboard-2-custom-nodes-not-loading-when-installed-globally/94546)._