# Readme information missing from https://flows.nodered.org/node page for a new node

**URL:** https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065
**Category:** Developing Nodes
**Created:** [25 July 2023 23:23 UTC](https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065 "2023-07-25T23:23:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![tonymacdonald](https://avatars.discourse-cdn.com/v4/letter/t/77aa72/32.png) [@tonymacdonald](https://discourse.nodered.org/u/tonymacdonald)
#### Post date: [25 July 2023 23:23 UTC](https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065/1 "2023-07-25T23:23:39Z")

</div>

I have just published a package and added it to the node red nodes library.

However, I had an issue with the links to a couple of images in the README.md which were displaying on GitHub but showing broken links on npm or in node red library.

I updated the image references in the README to use the full github url for the images such as  
`![example](https://github.com/tonymacdonald2008/node-red-msg-encapsulation/blob/main/readme/example.png?raw=true)`  
and republished a new version of the package.

The images now show correctly on both GitHub and on npm.  
However, when I added the new version of the package to the node red library the page for my package doesn't show any of the information from the README.md.

I am pretty sure that it was showing with the broken links before I added the new version.

The node library page is here  
`https://flows.nodered.org/node/@tonymacdonald/node-red-msg-encapsulation`

The npm page is here  
`https://www.npmjs.com/package/@tonymacdonald/node-red-msg-encapsulation`

Should I expect to see the README content on the node library page?

---

<div class="post-metadata">

### Author: ![tonymacdonald](https://avatars.discourse-cdn.com/v4/letter/t/77aa72/32.png) [@tonymacdonald](https://discourse.nodered.org/u/tonymacdonald)
#### Post date: [26 July 2023 15:59 UTC](https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065/2 "2023-07-26T15:59:11Z")

</div>

It is working now redeployed as @tonymacdonald/node-red-msg-encapsulation@0.0.4

I managed to get this corrected by doing the following:

1. reverted to relative paths for the images

2. added the repository information to the pakage.json

this last part was based on a response on stack overflow here

> <https://stackoverflow.com/questions/62575382/relative-link-from-readme-md-to-another-file-in-package-rendered-in-npmjs/68738752#68738752>

I guess npm needs this information to build out the relative paths.

Now full readme information is displayed properly in node red library and as a bonus the repo is also referenced there as well.

Not sure why the node red library dropped all README information from my package summary when I used absolute paths to the images in the GitHub repo. I see that the generated urls are different from the urls I provided.

---

<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: [26 July 2023 16:15 UTC](https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065/3 "2023-07-26T16:15:25Z")

</div>

> [@tonymacdonald](#):
>
> Not sure why the node red library dropped all README information from my package summary when I used absolute paths to the images in the GitHub repo. I see that the generated urls are different from the urls I provided.

We present the information the npm registry gives us. Sometimes the api returns blank README data even when their webpage shows a fully formed readme. It is fairly rare, but a pain when it does happen.

---

<div class="post-metadata">

### Author: ![tonymacdonald](https://avatars.discourse-cdn.com/v4/letter/t/77aa72/32.png) [@tonymacdonald](https://discourse.nodered.org/u/tonymacdonald)
#### Post date: [26 July 2023 18:24 UTC](https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065/4 "2023-07-26T18:24:58Z")

</div>

Thanks @knolleary  
That's good to know.  
I was able to get it working right eventually.

I wonder if something like that happens again, would it make sense to try adding the same package again, even without publishing a new version, to see if it the info shows up?  
Or would adding the same version again cause problems for the library?

---

<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: [24 September 2023 18:25 UTC](https://discourse.nodered.org/t/readme-information-missing-from-https-flows-nodered-org-node-page-for-a-new-node/80065/5 "2023-09-24T18:25:33Z")

</div>

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