chore: update cli to bash for syntax highlighting

Author: NathanWalker

content/configuration/webpack.md

@@ -49,7 +49,7 @@ Add file replacement rules. For source files (`.js` and `.ts`) this will add a n
 
 Example:
 
-```cli
+```bash
 --env.replace=./src/environments/environment.ts:./src/environments/environment.prod.ts
 ```
 
@@ -380,7 +380,7 @@ module.exports = (env) => {
 
 To change an existing rule, it's useful to know how it has been set up first:
 
-```cli
+```bash
 ns prepare android|ios --env.verbose
 # Note: we plan to add a separate command to just print the internal config
 ```

content/guide/choosing-an-editor.md

@@ -20,7 +20,7 @@ The `code` command runs in your command-line or terminal, and it works just like
 
 Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of command to create a new NativeScript app and open it for editing.
 
-```cli
+```bash
 ns create MyNewApp
 cd MyNewApp
 code .

content/guide/cli-basics.md

@@ -25,7 +25,7 @@ This helps ensure everything fits together correctly. If you're dealing with mys
 
 To clean, run this command from your project's root directory:
 
-```cli
+```bash
 ns clean
 ```
 
@@ -43,7 +43,7 @@ If you have multiple projects in a directory, you can run `ns clean` in it, and
 
 To list all connected devices (both physical and virtual), run:
 
-```cli
+```bash
 ns devices
 ```
 
@@ -61,7 +61,7 @@ Example output:
 
 To set the default package manager that the CLI uses (unless overridden in [nativescript.config.ts](/project-structure/nativescript-config#cli-packagemanager)):
 
-```cli
+```bash
 ns package-manager set npm
 ns package-manager set yarn
 ns package-manager set yarn2 # experimental

content/guide/creating-a-project.md

@@ -16,21 +16,21 @@ Official templates can be found in the [Templates GitHub repository](https://git
 
 Some of the templates are listed in the NativeScript CLI when creating a new project with `ns create`, others may be used by passing the `--template` flag with the template name (NPM package name).
 
-```cli
+```bash
 ns create myCoolApp
 ```
 
 If you would like to try one of the other templates not listed by `ns create` run:
 
-```cli
+```bash
 ns create myCoolApp --template <template-package-name or path-to-template>
 ```
 
 :::tip
 
 If you want to skip the interactive prompts, you can pass the following flags:
 
-```cli
+```bash
 ns create myCoolApp --angular // or --ng for short
 ns create myCoolApp --vue
 ns create myCoolApp --vue --ts // for vue with typescript
@@ -56,7 +56,7 @@ A basic template with a single page and no custom styles.
 
 To use, run:
 
-```cli
+```bash
 ns create myCoolApp --template @nativescript/template-blank
 ```
 
@@ -75,7 +75,7 @@ A template with a side drawer.
 
 To use, run:
 
-```cli
+```bash
 ns create myCoolApp --template @nativescript/template-drawer-navigation
 ```
 
@@ -94,7 +94,7 @@ A template with multiple tabs.
 
 To use, run:
 
-```cli
+```bash
 ns create myCoolApp --template @nativescript/template-tab-navigation
 ```
 
@@ -111,7 +111,7 @@ A template with a ListView and a details screen.
 
 To use, run:
 
-```cli
+```bash
 ns create myCoolApp --template @nativescript/template-master-detail
 ```
 

content/guide/debugging.md

@@ -40,15 +40,15 @@ console.timeEnd('myLabel')
 
 To start a Chrome debugging session, run your app in debug mode:
 
-```cli
+```bash
 ns debug android|ios
 ```
 
 The `ns debug` command builds and deploys the app on a connected device or emulator, in case you have multiple devices available you will need to pick one from a list, or pass in the `--device <id>` from `ns devices`.
 
 Once the app starts, a URL is printed to the console
 
-```cli{5-6}
+```bash{5-6}
 Setting up debugger proxy...
 Press Ctrl + C to terminate, or disconnect.
 
@@ -99,15 +99,15 @@ If you need to debug parts of the native stack instead of the JavaScript part of
 
 To start, prepare the iOS app:
 
-```cli
+```bash
 ns prepare ios
 ```
 
 This compiles your app source, creates the `platforms/ios` folder (if it doesn't exist yet). You can pass any of the flags you would normally pass to `ns run`.
 
 Next, open the `platforms/ios/<project-name>.xcworkspace` in XCode, either through the XCode browse menu, or from the command line:
 
-```cli
+```bash
 open platforms/ios/<project-name>.xcworkspace
 ```
 
@@ -134,7 +134,7 @@ If you need to debug parts of the native stack instead of the JavaScript part of
 
 To start, prepare the Android app:
 
-```cli
+```bash
 ns prepare android
 ```
 
@@ -145,7 +145,7 @@ Next, open the `platforms/android` folder in Android Studio, through the Android
 :::tip Tip
 If you [set up the `studio` command line launcher](https://stackoverflow.com/a/48266060/2270725), you can quickly open the NativeScript project from the command line with
 
-```cli
+```bash
 studio platforms/android
 ```
 

content/guide/development-workflow/using-packages.md

@@ -21,19 +21,19 @@ You can also explore [@nativescript/core](/core/#nativescript-core), which is in
 
 Once the needed plugin is found, it can be installed in a NativeScript app using the `ns plugin add` command which behaves just like `npm install` while also modifying any existing platform projects (linking, etc.).
 
-```cli
+```bash
 ns plugin add <plugin-name>
 ```
 
 For example, the following command installs the [NativeScript camera plugin](https://v8.docs.nativescript.org/plugins/camera.html).
 
-```cli
+```bash
 ns plugin add @nativescript/camera
 ```
 
 Instead of using plugin add, package managers like npm, yarn, or pnpm can also be used:
 
-```cli
+```bash
 npm install --save @nativescript/camera
 ```
 
@@ -43,7 +43,7 @@ The installation of a NativeScript plugin is similar to installing a npm package
 
 As demonstrated above, the command `ns plugin add @nativescript/camera` is equivalent to `npm i @nativescript/camera --save` internally.  However, when installing a developer dependency, such as @nativescript/types or @nativescript/webpack, you need to explicitly save it as a devDependency.  To do so, use the npm install command with the --save-dev flag. For instance:
 
-```cli
+```bash
 npm i @nativescript/types --save-dev
 ```
 
@@ -69,13 +69,13 @@ requestPermissions()
 
 To remove a NativeScript plugin, you can use the following command.
 
-```cli
+```bash
 ns plugin remove <plugin-name>
 ```
 
 For example, the following command removes the NativeScript camera plugin.
 
-```cli
+```bash
 ns plugin remove @nativescript/camera
 ```
 
@@ -99,6 +99,6 @@ NativeScript CLI supports three package managers:
 
 In case you want to check what is the currently used package manager, you can use:
 
-```cli
+```bash
 ns package-manager get
 ```

content/guide/native-code/generate-typings.md

@@ -8,7 +8,7 @@ contributors:
 
 ## Generate types for iOS
 
-```cli
+```bash
 ns typings ios
 ```
 
@@ -18,21 +18,21 @@ This will generate the following folder structure `typings/ios/arm64`
 
 For Android run:
 
-```cli
+```bash
 ns typings android --jar <path to a jar>
 # or
 ns typings android --aar <path to an aar>
 ```
 
 You can also generate typings for an Android package (Maven):
 
-```cli
+```bash
 ns typings android <package-name>
 ```
 
 For instance:
 
-```cli
+```bash
 ns typings android "com.google.android.gms:play-services-tasks"
 ```
 

content/guide/publishing/android-google-play.md

@@ -33,7 +33,7 @@ The following commands will build your app in release mode, and copy the result
 
 <!-- tab: .aab -->
 
-```cli
+```bash
 ns build android --release \
   --key-store-path <path-to-your-keystore> \
   --key-store-password <your-key-store-password> \
@@ -45,7 +45,7 @@ ns build android --release \
 
 <!-- tab: .apk -->
 
-```cli
+```bash
 ns build android --release \
   --key-store-path <path-to-your-keystore> \
   --key-store-password <your-key-store-password> \
@@ -58,7 +58,7 @@ ns build android --release \
 
 <!-- tab: Example Windows -->
 
-```cli
+```bash
 ns build android --release \
   --key-store-path C:\projects\app\upload.keystore \
   --key-store-password example_password \
@@ -70,7 +70,7 @@ ns build android --release \
 
 <!-- tab: Example macOS/Linux -->
 
-```cli
+```bash
 ns build android --release \
   --key-store-path ~/projects/app/upload.keystore \
   --key-store-password example_password \

content/guide/running.md

@@ -11,7 +11,7 @@ To run a NativeScript app, you need a device — either a physical or virtu
 
 To run a project, use the `ns run` command. There's also a `ns debug` command covered in the [debugging documentation](/guide/debugging#debugging-with-chrome-devtools).
 
-```cli
+```bash
 ns run android
 ns run ios
 ```
@@ -52,13 +52,13 @@ Next, go to `Settings › System › Developer options` and enable `USB debuggin
 
 Plug in your device via USB and check that it is correctly being detected by <abbr title="Android Debug Bridge">ADB</abbr>:
 
-```cli
+```bash
 adb devices
 ```
 
 To verify NativeScript can also detect the device, run:
 
-```cli
+```bash
 ns devices android
 ```
 
@@ -99,7 +99,7 @@ If there's no `.xcworkspace` file, you can open the `.xcodeproj` file instead.
 
 Once the app successfully runs from Xcode, you can close it and continue using the NativeScript cli:
 
-```cli
+```bash
 ns run ios
 ```
 
@@ -111,7 +111,7 @@ Once the device has been [prepared for development](#preparing-an-ios-device-for
 
 After disconnecting the cable, the device should remain visible in `ns devices` and running the app should work as normal:
 
-```cli
+```bash
 ns run ios
 ```