You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I experienced a problem today when provisioning a Debian Wheezy VM. Node.js and NPM would both install, but the two modules I used with them, buster and sinon, did not. Invocations of either binary would yield an error. It seemed that both relied on the node binary being available, which is not the case with the nodejs package in Debian. However, when the Debian team decided to rename to package, it added an additional package. That package is nodejs-legacy0. The package provides both the node and nodejs binaries, thereby providing both options to modules and developers alike.
The text was updated successfully, but these errors were encountered:
I experienced a problem today when provisioning a Debian Wheezy VM. Node.js and NPM would both install, but the two modules I used with them, buster and sinon, did not. Invocations of either binary would yield an error. It seemed that both relied on the
node
binary being available, which is not the case with thenodejs
package in Debian. However, when the Debian team decided to rename to package, it added an additional package. That package isnodejs-legacy
0. The package provides both thenode
andnodejs
binaries, thereby providing both options to modules and developers alike.The text was updated successfully, but these errors were encountered: