Metawork for Node.js

This page covers troubleshooting information specific to Metawork for Node.js.

Node.js version managers

TL;DR
Version managers such as nvm and nodist typically set the PATH environment variable to manage installed runtimes. This can conflict with finding the Metawork for Node.js runtime. This can result in an error generated by your version manager, either because Metawork for Node.js is not running, or because Metawork for Node.js is running in addition to your previously-installed Node.js.

If you run into this error during the alpha, uninstall your version manager because Metawork will double as one. Work is underway to make Metawork compatible with major Node.js version managers for GA. If you’re unable to remove your version manager, please join the Metawork Discord and we’ll make every effort to help you get set up.

The details
When you run a command like node or npm, your operating system searches through a list of directories to find an executable file with that name. This list of directories lives in an environment variable called PATH, with each directory in the list separated by a colon:

/usr/local/bin:/usr/bin:/bin

Version managers such as nvm and nodist typically set the PATH environment variable to a specific location based on the Node.js version they are running on your machine.

In order to use Metawork, you run Metawork’s supercharged version of the Node.js runtime on your machine. This means that if you are running a version manager with the PATH set to its specifications, your application may not successfully boot on the Metawork for Node.js runtime. This usually results in an error generated by your version manager, either because Metawork for Node.js is not running, or because Metawork for Node.js is running in addition to your previously-installed Node.js.

Work is underway to make Metawork compatible with major Node.js version managers. In the meantime, if you run into an error, please join the Metawork Discord and we’ll help you set up Metawork.