Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
Describe the bug
I have just updated to the latest Nativescript version: v5.4.0, and when I try to run any common tns command for example: tns run ios or tns platform remove ios the command crashes and does not execute.
To Reproduce
Install latest Nativescript cli version
npm install -g nativescript
Create new hello-word app
tns create hello-word
then run:
tns run ios
Then the error occurs
Expected behavior
Command should run
Sample project
Any project
Additional context
See a screenshot below:

The error is the red message seen above.
Any command like tns run ios doesn't run, I've only found tns doctor to work but still provides the error message.
@Aceman18,
Can you please try tns extension uninstall nativescript-cloud ?
To add to this (we debugged this in the Slack channel), npm install -g [email protected] did solve the problem, so it does appear to be a v5.4.0-specific regression.
@Fatme Success! That worked!
Do you have anymore information on how thats worked?
@Aceman18,
Let me first explain the purpose of processService. Its main goal was to be a common place for handling all exit signals - exit, SIGINT, SIGTERM. However, handling SIGINT in CLI led to a problem that CTRL+C signal does not exit the process as we have to manually cleanup all resources that prevent Node.js from exiting gracefully. More info can be found here
As we decided to handle the CTRL+C signal in a different manner, we deleted the processService in NativeScript CLI v5.4.0. However, nativescript-cloud-extension uses the processService as well. So, we needed to release a new version of nativescript-cloud that is compatible with both official CLI and the next version of CLI (v5.4.0). And we did it.
After updating NativeScript CLI to v5.4.0, nativescript-cloud is not updated out of the box. So in result, you have the latest version of CLI and the old version of nativescript-cloud extension.
Actually the error unable to resolve processService is not from CLI, it is from nativescript-cloud-extension itself. tns extension uninstall nativescript-cloud do the trick as it removes the old extension - the one that relies on processService. After that, NativeScript CLI installs the latest nativescript-cloud on first execution of any command - the one that doesn't rely on processService and that resolves the issue.
Most helpful comment
@Aceman18,
Let me first explain the purpose of
processService. Its main goal was to be a common place for handling all exit signals -exit,SIGINT,SIGTERM. However, handling SIGINT in CLI led to a problem thatCTRL+Csignal does not exit the process as we have to manually cleanup all resources that preventNode.jsfrom exiting gracefully. More info can be found hereAs we decided to handle the
CTRL+Csignal in a different manner, we deleted theprocessServicein NativeScript CLI v5.4.0. However, nativescript-cloud-extension uses theprocessServiceas well. So, we needed to release a new version ofnativescript-cloudthat is compatible with both official CLI and thenextversion of CLI (v5.4.0). And we did it.After updating NativeScript CLI to
v5.4.0,nativescript-cloudis not updated out of the box. So in result, you have the latest version of CLI and the old version ofnativescript-cloudextension.Actually the error
unable to resolve processServiceis not from CLI, it is fromnativescript-cloud-extensionitself.tns extension uninstall nativescript-clouddo the trick as it removes the oldextension- the one that relies onprocessService. After that, NativeScript CLI installs the latestnativescript-cloudon first execution of any command - the one that doesn't rely onprocessServiceand that resolves the issue.