No UI to update new dependency nodes in project feature

[kazuhitoyokoi]

Current Behavior

In the project feature, users can install nodes defined in the dependencies section of the package.json file by clicking the Install button in the project settings UI. However, after updating the version of the node in the remote repository, the user cannot update the node to new one in the project settings UI because Node-RED only checks the npm module name, not both the npm module name and the version.

Expected Behavior

When there is a difference between the node version in package.json and Node-RED, the Install button (or Update button) is available on the project settings UI to update the existing node to the new node.

Steps To Reproduce

(1) User A adds the used node to package.json on the project settings UI and uploads it and the flow file to the GitHub repository.

(2) User B downloads package.json and the flow file to the local Node-RED using the project feature.

(3) User B installs the dependency node by clicking the install button on the project settings UI.

(4) User B updates the installed node to the new version in the Palette Manager.

(5) User B deletes the previous version in package.json and adds the new version in the project settings UI.

(6) User B uploads package.json and the flow file to the GitHub repository using the project feature.

(7) User A downloads the flow using the pull button.

-> User A cannot update the existing node to the specified one in the Node-RED flow editor.

Example flow

No response

Environment

• Node-RED version: 3.1.9 and 4.0.0-beta.2
• Node.js version: 21.5.0
• npm version: 10.2.4
• Platform/OS: Macbook Air M1, 2020, macOS 14.4.1 (23E224)
• Browser: Google Chrome Version 124.0.6367.91 (Official Build) (arm64)