Rpm installer script degrades npm [FIXED]

General
1

I'm running node-RED in a Oracle Linux VM - Linux v4.14.35 which was installed using this node-RED script.
I updated to NR v1.1.0 a few days ago using the script and wanted to start using the 'https certificate refresh' feature, which required node.js v11+.
The latest version of node.js in the 'nodesource' repo is v10.21.0, so I had to use the Oracle recommended repo and updated to node v12.18.2.

[opc@digitalnut log]$ node -v
v12.18.2

So far so good.

However, ran the installer script again this morning to get NR v1.1.2 and unfortunately the script installed node.js v10.21.0, which in turn stopped the 'https certificate refresh' from working!!

[opc@digitalnut ~]$ node -v
v10.21.0

Should this happen?

The install log shows;

--> Running transaction check
---> Package nodejs.x86_64 0:12.18.2-1.0.1.el7 will be updated
---> Package nodejs.x86_64 2:10.21.0-1nodesource will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package      Arch         Version                       Repository        Size
================================================================================
Updating:
 nodejs       x86_64       2:10.21.0-1nodesource         nodesource        20 M

Transaction Summary
================================================================================
2

ah sorry - haven't updated that in a while - new version pushed that defaults to node12

1 Like
3

Working fine now, thanks.

1 Like
4

Thanks for spotting it

5

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