# Well, that odd npm issue is back!

**URL:** <https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569>\
**Category:** General\
**Created:** [22 July 2020 23:13 UTC](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569 "2020-07-22T23:13:06Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [20 September 2020 08:31 UTC](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569/21 "2020-09-20T08:31:23Z")

</div>

> [@Nodi.Rubrum](#):
>
> deleted all flows via UI

Did you also remove any config nodes?

---

<div class="post-metadata">

**Author:** ![Nodi.Rubrum](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodi.rubrum/32/107482_2.png) [@Nodi.Rubrum](https://discourse.nodered.org/u/Nodi.Rubrum)\
**Post date:** [21 September 2020 06:58 UTC](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569/22 "2020-09-21T06:58:19Z")

</div>

Ok, this was actually funny when I figured it out, why it went south. To be clear this is something I cause, not a bug or something odd about NR. The only thing that is at all suspect if how the issue is reported. The log states that there is a failure to read the configuration of the said dashboard node, or nodes with said dashboard, and the visual result is you get an empty dashboard of course.

This is not a case where something is lost, I just clear the slate, so to speak, to start at a known point. There are other ways to recovery, resolve this or similar, but why repair when you can cleanly replace, is the mind set.

But, here is the kicker, I had disabled elements of the dashboard UI. I thought I had only disabled some flows, but when I traced my steps, looking through the incremental saves, I had disabled parts of the UI, no just UI objects, buttons and tables, etc. But tabs/groups. This apparently was sufficient brake the dashboard? Or disabled it to the point it could not load correctly?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [21 September 2020 08:13 UTC](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569/23 "2020-09-21T08:13:55Z")

</div>

If disabling stuff causes the sort of errors you are reporting then I would say that is a bug. Can you trim the failing flow file down to a point where it could be posted here?

---

<div class="post-metadata">

**Author:** ![Nodi.Rubrum](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodi.rubrum/32/107482_2.png) [@Nodi.Rubrum](https://discourse.nodered.org/u/Nodi.Rubrum)\
**Post date:** [21 September 2020 20:06 UTC](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569/24 "2020-09-21T20:06:33Z")

</div>

Yeah let me try... it was a monster flow file.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 November 2020 20:06 UTC](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569/25 "2020-11-20T20:06:54Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/well-that-odd-npm-issue-is-back/30569.md?page=1)