vorpal VS nvm

I occasionally try that as well and it sometimes helps but not for things like node apps that use https://vorpal.js.org REPLs. They just aren't usable in shell-mode.

Got it, so more about the general idea of using Node to interact with a shell. Fair points but I'm not sure that's where zx falls. I'm looking at it in relation to projects like commander, oclif, and vorpal— frameworks for authoring and packaging local-use CLI tools written in JS, typically aimed at people who know JS and work in a terminal but don't know shell scripting. Those have the overhead of learning a framework, and don't do anything to help you work with the shell. zx seems to come from the other direction: instead of an esoteric framework, shell concepts and shell commands in a Node script.

Assuming the project uses node, and admittedly it's a lil overkill, but you could use vorpal.

Are you wanting to run your nodejs app, and then control it within the same terminal it is running in? If so, take a look at vorpal

Node.js + Nvm - runtime for javascript without a browser

Install Node.js if it hasn't been installed. There are several ways to install Node.js. You may download the installer from the official website, or install it with tools like NVM. After installation, run this command to verify its installation.

Our server also needs Node.js to run our app. We could install the binary directly, but I prefer to use a tool called NVM, which allows us to easily manage Node versions. We can install it with this command:

By setting up your environment in isolation, you can prevent yourself from a lot of issues when experimenting with code. It makes your code behave more predictable due to the defined state of the runtime environment you are working with. This article should provide you with enough information to get started, but obviously, there is a lot more power embedded in NVM, Virtual Environment and RBEnv. So make sure to check their documentation.

I highly recommend setting up nodejs with a version manager, nvm was and still is a popular option, however, I now recommend and have been using fnm, a simpler and faster alternative to manage my nodejs versions.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

I usually develop on Windows so I installed NVM for Windows from here, but if you’re on other OS I’m sure you can find a version that supports it, probably this is the answer.

This was a very quick introduction to how I setup NodeJS on my environment using nvm. If you have any questions please refer to the official documentation or contact me via my Social Links.

Source: Can this be used to create/download npm as a standalone executable? #3237.