Why the difference between manual node install and palette install

General
1

Something I've wondered for a while

In (all?) contrib node notes - they say install using

npm install node-red-contrib-xxx

but the log from a node install via palette says

npm install--no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-xxx@version_number

Why is this? What diff does it make? Should installing from command line use the extra params?

2

--no-audit - turns off the audit report. When doing it via the palette manager, we have no easy way for the user to do anything meaningful with that information, so we turn it off. When running manually, it useful to see.

--no-update-notifier - turns off npm telling you there is a new version of npm available. Again, not useful in the context of the palette manager as the user can't do anything about it via the editor.

--no-fund - turns off the notifications that a module that has been installed has a fund message.

--save - ensures the module is saved to package.json. This is now the default behaviour of npm so the arg isn't strictly needed.

--save-prefix="~" - meh

--production - do not install development dependencies. Again, this has now become the default behaviour of npm

2 Likes
3

@cymplecy see https://docs.npmjs.com/cli-commands/install.html for a fuller list of options.

1 Like
5

if you can be bothered to type them in all the time then please go ahead :wink:
They just stop various extra checks that you see when you don't use them. And indeed the update notifier can fail and timeout and really slow things unnecessarily.

2 Likes
6

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