running latest CLI ... Sept 30th build
ns -v = 7.0.9-2020-09-30-180843-14270
running - tns debug android --env.aot --no-hmr --emulator
Error while loading nativescript-cloud is: Default commands should be required before child commands
The command should continue running despite the error. Will be looking into why it happens.
Ok, the issue is that if you have nativescript-cloud installed on your system (from older cli for example), it adds conflicting commands to the CLI and causes the issue. In particular it adds config get/set commands that are now in the CLI by default.
Since nativescript-cloud in it's current form is not used - you can safely uninstall it with
ns extension uninstall nativescript-cloud
And the error should disappear.
This worked for me.
Uninstalling the nativescript-cloud worked for me too!
ns extension uninstall nativescript-cloud doesn't work for me (command not found: ns), exist any other command to remove extensions?
Thanks!
@jdnichollsc tns extension uninstall nativescript-cloud perhaps? Though if ns doesn't exist on your machine, you are likely using an old version of the CLI that should not have the error in the first place... (i'm confused)
Oh excellent, it's working now! thanks for your help! <3
Perfectly working now! Thanks! ;o)
Mmm I've just upgraded from NS6 to NS7.1.2 and for me it doesn't seem to work...
Strange ... any command give me this error... except the simple ns --version... Obviously I've tried... ns, tns --> same error.
Is there another way to remove Nativescript-cloud ?
The migration script shouldn't remove it if it unused with new version ?
Ok simply from another terminal...tns (or ns) extension uninstall nativescript-cloud has worked. Cheers!
Most helpful comment
Ok, the issue is that if you have
nativescript-cloudinstalled on your system (from older cli for example), it adds conflicting commands to the CLI and causes the issue. In particular it addsconfig get/setcommands that are now in the CLI by default.Since
nativescript-cloudin it's current form is not used - you can safely uninstall it withAnd the error should disappear.