# Request for feedback: Flow Library Categories

**URL:** <https://discourse.nodered.org/t/request-for-feedback-flow-library-categories/92660>\
**Category:** General\
**Created:** [25 October 2024 11:10 UTC](https://discourse.nodered.org/t/request-for-feedback-flow-library-categories/92660 "2024-10-25T11:10:18Z")\
**Posts on this page:** 1\
**Showing post:** 49

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [2 November 2024 14:29 UTC](https://discourse.nodered.org/t/request-for-feedback-flow-library-categories/92660/49 "2024-11-02T14:29:35Z")

</div>

The goal is to allow the palette manager to install a version other than latest. The problem is that the catalog version array must not be huge.

> [@Node version selection in palette](https://discourse.nodered.org/t/node-version-selection-in-palette/89183/2):
>
> It is certainly a missing feature. Something I'd like us to look at, but will require quite a lot of work to achieve as the current catalog only lists the current version. There's another question on nodes that change their minimum node.js version or node-red version support. Right now, the Palette Manager doesn't know about that information, so will offer to install a node that isn't compatible with your current node.js version. If we're going to do the work to extend the catalogue format to …

> [@TotallyInformation](#):
>
> What would be better is perhaps having a check for a CHANGELOG.

It is under discussion 😉

---

_[View the full topic](https://discourse.nodered.org/t/request-for-feedback-flow-library-categories/92660)._