🚨 Having trouble with 'nx build nativescript-{yourapp}'? See...

[NathanWalker]

A new requirement is that every flag with a value must be separated with an = to ensure any flags which should never be duplicated are properly deduped (in event it was accidentally added twice):

Case 1

• BAD

nx build nativescript-app:android:prod --uglify --key-store-path upload-keystore.jks --key-store-password xxxxxx --key-store-alias xxx --key-store-alias-password xxxxxxx --skip-nx-cache --aab

• GOOD

nx build nativescript-app:android:prod --uglify --key-store-path=upload-keystore.jks --key-store-password=xxxxxx --key-store-alias=xxx --key-store-alias-password=xxxxxxx --skip-nx-cache --aab

Notice the usage of = between key/values.

Case 2

If you notice your build command turning into nx run or ns debug in a CI Pipeline you may need to use an alternate format, for example:

• Potentially problematic depending on pipeline setup:

nx build nativescript-app:ios:prod

――――――――――――――――――――――――
Running NativeScript CLI within apps/nativescript-app/
ns debug ios --no-hmr --env.uglify --env.production --for-device --release

Wait what?! Notice the nx build turned into ns debug - that's not what we want.

• Solution:

nx run nativescript-app:build:prod --platform=ios

――――――――――――――――――――――――
Running NativeScript CLI within apps/nativescript-app/
ns build ios --no-hmr --env.uglify --env.production --for-device --release

There we go, it properly builds now.

[JakeAi]

@NathanWalker Whatever was updated since 3.0.14 kind of makes this unusable, especially without an example project.json. No matter what I do it runs a debug command, or I get an error for isUnitTesting or

The arguments 'C:\Program Files\nodejs\node.exe C:\Development\repo\node_modules\nx\bin\run-executor.js' are not valid for the current command.

[NathanWalker]

@NathanWalker Whatever was updated since 3.0.14 kind of makes this unusable, especially without an example project.json. No matter what I do it runs a debug command, or I get an error for isUnitTesting or

The arguments 'C:\Program Files\nodejs\node.exe C:\Development\repo\node_modules\nx\bin\run-executor.js' are not valid for the current command.

@JakeAi I believe you got past that but ping back here if not.

[JakeAi]

@NathanWalker Whatever was updated since 3.0.14 kind of makes this unusable, especially without an example project.json. No matter what I do it runs a debug command, or I get an error for isUnitTesting or

The arguments 'C:\Program Files\nodejs\node.exe C:\Development\repo\node_modules\nx\bin\run-executor.js' are not valid for the current command.

@JakeAi I believe you got past that but ping back here if not.

nx run nativescript-monitor:build:prod --platform=android

―――――――――――――――――――――――― 🤖
Running NativeScript CLI within apps/nativescript-monitor

ns build android --no-hmr --env.uglify --env.production --for-device --release --key-store-path=E:\Development\Android\android.keystore --key-store-password=notforyou --key-store-alias=monitor --key-store-alias-
password=notforyou --env.replace="../../libs/data/default-env/src/lib/data-default-env.ts:../../libs/data/default-env/src/lib/data-default-env.prod.ts,./src/environments/environment.ts:./src/environments/environment.prod.ts" --force C:\Program Files\nodejs\node.exe C:\Development\minnich\node_modules\nx\bin\run-executor.js

Note: When using extra cli flags, ensure all key/value pairs are separated with =, for example: --provision="Name"

---
Error while loading nativescript-cloud is: Default commands should be required before child commands
The arguments 'C:\Program Files\nodejs\node.exe C:\Development\minnich\node_modules\nx\bin\run-executor.js' are not valid for the current command.
Run ns build android --help for more information.

[NathanWalker]

@JakeAi can you run the following:

node -v
npm -v
ns -v

and paste the output here?

Then also can run:

npm install -g nativescript

And confirm version once more:

ns -v

[JakeAi]

@JakeAi can you run the following:

node -v
npm -v
ns -v

and paste the output here?

Then also can run:

npm install -g nativescript

And confirm version once more:

ns -v

v14.18.2
6.14.15
Error while loading nativescript-cloud is: Default commands should be required before child commands
8.2.3
√ Up to date.

• nativescript@8.2.3
  removed 4 packages and updated 185 packages in 43.337s

Error while loading nativescript-cloud is: Default commands should be required before child commands
8.2.3
√ Up to date.

[NathanWalker]

@JakeAi you will want at least node 15 or higher (we recommend 17 or 18).
Additionally you can run this command:

ns extension uninstall nativescript-cloud

That is an old and no longer used extension.

[JakeAi]

@JakeAi you will want at least node 15 or higher (we recommend 17 or 18). Additionally you can run this command:

ns extension uninstall nativescript-cloud

That is an old and no longer used extension.

I now get this

Note: When using extra cli flags, ensure all key/value pairs are separated with =, for example: --provision="Name"

---
node:events:505
      throw er; // Unhandled 'error' event
      ^

Error: spawn ns.cmd ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn ns.cmd',
  path: 'ns.cmd',
  spawnargs: [
    'build',
    'android',
    '--no-hmr',
    '--env.uglify',
    '--env.production',
    '--for-device',
    '--release',
    '--key-store-path=E:\\Development\\Android\\android.keystore',
    '--key-store-password=',
    '--key-store-alias=monitor',
    '--key-store-alias-password=',
    '--env.replace="../../libs/data/default-env/src/lib/data-default-env.ts:../../libs/data/default-env/src/lib/data-default-env.prod.ts,./src/environments/environment.ts:./src/environments/environment.prod.ts"',
    '--force',
    'C:\\Program Files\\nodejs\\node.exe',
    'C:\\Development\\repo\\node_modules\\nx\\bin\\run-executor.js'
  ]
}

[NathanWalker]

If you now run the following what versions do you have:

node -v
npm -v
ns -v

[JakeAi]

If you now run the following what versions do you have:

node -v
npm -v
ns -v

I'm currently dealing with npm/cli#4234
Ill let you know when I figure out how to fix it

[JakeAi]

node -v
npm -v
ns -v

This is the error. The previous error was related to that issue i linked.

The arguments 'C:\Program Files\nodejs\node.exe C:\Development\minnich\node_modules\nx\bin\run-executor.js' are not valid for the current command.
Run ns build android --help for more information.

v18.4.0
8.12.1
8.2.3
√ Up to date.

[NathanWalker]

@JakeAi how about nx version as well? npx nx --version or yarn nx --version from root of your workspace.
Now that you have node updated you would likely benefit from doing a npx nx migrate latest and run through the steps to get on latest across the board.