# Issues on flows.nodered.org for new version of my node

**URL:** <https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966>\
**Category:** Developing Nodes\
**Created:** [25 February 2022 07:28 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966 "2022-02-25T07:28:10Z")\
**Posts on this page:** 11\
**Page:** 1

<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:** [25 February 2022 07:28 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/1 "2022-02-25T07:28:10Z")

</div>

Hi folks,

I have published version 1.0.1 of my [node-red-contrib-xterm](https://github.com/bartbutenaers/node-red-contrib-xterm) node, but I have some issues with it:

1. On [flows.nodered.org](http://flows.nodered.org) my [readme](https://flows.nodered.org/node/node-red-contrib-xterm) page is empty for some reason.

2. The scorecard reports issues with my dependencies:

Would appreciate if somebody could have a look at what I am doing wrong.

Thanks !!  
Bart

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [25 February 2022 08:50 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/2 "2022-02-25T08:50:01Z")

</div>

Somebody will probably have to look at the problem with the readme, but I'll guess the versioning is because of the `node-pty-prebuilt-multiarch` node because it's a pre-release version.

I'd guess that it's the first node (or at least noticed) with a version like that the scorecard code has seen and may need looking at.

---

<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:** [25 February 2022 09:19 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/3 "2022-02-25T09:19:05Z")

</div>

> [@hardillb](#):
>
> Somebody will probably have to look at the problem with the readme

Hey @hardillb,  
Is there some kind of log avalable where we can try to find ourselves the root cause? Or can it only be analyzed perhaps by installing and debugging that application?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [25 February 2022 09:27 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/4 "2022-02-25T09:27:10Z")

</div>

> [@BartButenaers](#):
>
> Or can it only be analyzed perhaps by installing and debugging that application?

You can install the `node-red-dev` tool locally.

> **[GitHub - node-red/node-red-dev-cli: Command-line tool for Node-RED Node authors](https://github.com/node-red/node-red-dev-cli)**
>
> Command-line tool for Node-RED Node authors. Contribute to node-red/node-red-dev-cli development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [25 February 2022 09:35 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/5 "2022-02-25T09:35:31Z")

</div>

As Nick mentioned you can run the score card app `node-red-dev` easily yourself.

There is no public log for the flows app and while you can run it yourself (All the code it on [github](https://github.com/node-red/flow-library/)) it's probably more effort than it's worth at the moment.

---

<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:** [25 February 2022 22:53 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/6 "2022-02-25T22:53:48Z")

</div>

> [@knolleary](#):
>
> You can install the `node-red-dev` tool locally.

Ok that is indeed useful.  
Now at least I see the error text: _"node-pty-prebuilt-multiarch is not at latest version, package.json specifies: ^0.10.1-pre.4, latest is: 0.10.0"_.

But I am not sure whether that is entirely correct, because the latest version (and indeed also the most downloaded version) is this one:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/1/91c12b8d0f102bbf8384886c9d3da03549b2772a.png)

But when I debug the node-red-dev tool, then the npm-check library shows another latest version:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/8/c80823a37c010bce659aa4fb0fde991e7fd7a230.png)

It seems to me that the npm-check library calculates a incorrect latest version. However since the npm-check library doesn't [seem](https://github.com/dylang/npm-check/graphs/contributors) to be actively maintained, I am not going to investigate this further because they won't solve it anyway...

Case closed!!

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [25 February 2022 22:56 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/7 "2022-02-25T22:56:08Z")

</div>

Could you raise an issue on node-red-dev with these details?

The underlying module may appear unmaintained, but that doesn't mean we want our tool to be reporting incorrect results.

---

<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:** [25 February 2022 23:19 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/8 "2022-02-25T23:19:23Z")

</div>

Ok thanks Nick, makes sense what you say...  
I have registered an [issue](https://github.com/node-red/node-red-dev-cli/issues/24) with the required information.

---

<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:** [28 February 2022 06:47 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/9 "2022-02-28T06:47:23Z")

</div>

> [@hardillb](#):
>
> There is no public log for the flows app and while you can run it yourself (All the code it on [github](https://github.com/node-red/flow-library/)) it's probably more effort than it's worth at the moment.

Morning @hardillb,  
I am getting the impression that the flow library doesn't like my readme pages 😉  
I just release the new version of the [node-red-contrib-ui-multistate-switch](https://flows.nodered.org/node/node-red-contrib-ui-multistate-switch), and again the readme page is empty.  
There is only a link (to the readme page) added to the readme page. So that cannot caused this...

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 February 2022 09:15 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/10 "2022-02-28T09:15:17Z")

</div>

Hi @BartButenaers

> [@BartButenaers](#):
>
> I am getting the impression that the flow library doesn't like my readme pages

It isn't us... its npm. If you look at the API response from the registry for your node, you can see the `readme` property is empty - [https://registry.npmjs.org/node-red-contrib-ui-multistate-switch](https://registry.npmjs.org/node-red-contrib-ui-multistate-switch)

This happens from time to time - not sure what causes it, or it it's just some npm flakiness.

The solution is usually to publish a new version and hope npm picks it up properly.

---

<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:** [29 April 2022 09:15 UTC](https://discourse.nodered.org/t/issues-on-flows-nodered-org-for-new-version-of-my-node/58966/11 "2022-04-29T09:15:56Z")

</div>

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