[BUG] Fix flowise-* dependencies version in package.json

[tirongi]

Describe the bug
When you install an older version of flowise, this will install the latest flowise-ui and flowise-components bringing to a different environment than the original 1.4.10 version.

To Reproduce
As instance try to install flowise@1.4.10 with: npm i -g flowise@1.4.10

Expected behavior
I expect that this version would download as dependencies respectively flowise-ui@1.4.7 and flowise-components@1.5.1 (the latest working versions of the two deps at the time of version freezing), instead in the package.json is specified to download the latest version.

In order to have a pure flowise@1.4.10 I have to force the installation of the two dependencies after the main install by going into the flowise install folder and send an "npm i flowise-ui@1.4.7" and "npm i flowise-components@1.5.1".

[HenryHengZJ]

hmm do you have any suggestion on how to achieve that?

[tirongi]

IMHO, the best solution would be to use a version numbering that was coherent with the "compatibility family" among the flowise* components ensuring to follow the <major>.<minor>.<patch> pattern.
Then, assuming that versioning follow this criteria, you can set in the package.json a line like "flowise-components":"~1.4.0" in order to tell it to install latest 1.4.x available (instead of "*", actually used, that will point to the latest also when you install an older version of the software).

Starting from the next release of Flowise I would suggest to use as such of numbering and setup in the package.json to set and preserve the required version of each flowise-*.
In order to fix older versions, maybe occur to modify each package.json with the latest working release and set the release label in git to these fixed versions.

As always, thanks a lot for the great work!