Running hb-config>Upgrade node.js corrupting node install
For the last two node.js updates I've tried to install via the hb-config>Upgrade node.js option it seems to have corrupted the node.js install somehow.  In both cases running "sudo hb-config" and then selecting "Upgrade node.js" resulted in the following error:

pi@homebridge:/var/lib/homebridge $ sudo hb-config
Updating Node.js to LTS, please wait...
Installed: v14.17.1
Current Node.js LTS: v14.17.2
Updating Node.js to v14.17.2...
/usr/local/sbin/hb-config: 203: /usr/local/sbin/hb-config: npm: not found

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Node.js v14.17.1
/usr/local/sbin/hb-config: 208: /usr/local/sbin/hb-config: npm: not found
npm 
Node.js updated to v14.17.2
Rebuilding modules...
sudo: npm: command not found

Yesterday I installed a new plugin via config-ui-x and today, after attempting to update node.js, I get an error about "sudo: npm: command not found" when trying to install a plugin.  Which seems to indicate the process of running hb-config or the "Upgrade node.js" routine is causing this issue.  In the previous case I was able to resolve by running "sudo apt-get update && apt-get upgrade".  I will try this again later today to confirm it resolves it again in this case.