<h1 id="nativescript-command-line-interface" align="center">

<a href="https://www.npmjs.com/package/nativescript"><img src="https://raw.githubusercontent.com/NativeScript/artwork/main/logo/export/NativeScript_Logo_Dark_Transparent.png" alt="Nativescript Logo" width="200"></a>

</h1>

<h4 align="center">The NativeScript CLI lets you create, build, and deploy <a href="https://docs.nativescript.org/" target="_blank">NativeScript</a> apps.</h4>

<p align="center">

<a href="https://www.npmjs.com/package/nativescript"><img src="https://img.shields.io/npm/v/nativescript.svg" alt="npm version"></a>

<a href="https://github.com/NativeScript/NativeScript/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="license"></a>

<a href="https://www.npmjs.com/package/nativescript"><img src="https://img.shields.io/npm/dm/nativescript.svg" alt="downloads"></a>

</p>

Get it using: `npm install -g nativescript`

To learn more about NativeScript, you can check the following resources:

* [The NativeScript web page][2]

* The NativeScript [Documentation][4] and contributing to [docs via the repo](https://github.com/NativeScript/docs)

[Back to Top][1]

You can install and run the NativeScript CLI on Windows, macOS or Linux.

* [Windows](https://docs.nativescript.org/setup/windows)

* [macOS](https://docs.nativescript.org/setup/macos)

* [Linux](https://docs.nativescript.org/setup/linux)

Installation

* The `src` directory (or sometimes `app` folder) is the **development space for your application**. You should modify all common and platform-specific code within this directory. When you run `prepare <Platform>`, the NativeScript CLI prepares relevant content to the platform-specific folders for each target platform.

* The `platforms` directory is created empty. When you add a target platform to your project, the NativeScript CLI creates a new subdirectory with the platform name. The subdirectory contains the ready-to-build resources of your app. When you run `prepare <Platform>`, the NativeScript CLI prepares relevant content from the `app` directory to the platform-specific subdirectory for each target platform.

[Back to Top][1]

The NativeScript CLI respects any platform configuration files placed inside `App_Resources`.

To specify which capabilities are required by your App - Maps, Push Notifications, Wallet etc. you can add or edit the `app.entitlements` file placed inside `App_Resources/iOS`. When building the project, the default `App_Resources/iOS/app.entitlements` file gets merged with all Plugins entitlement files and a new `yourAppName.entitlements` is created in the platforms directory. The path would be `platforms/ios/<application name>/<application name>.entitlements` and will be linked in the `build.xcconfig` file.

You can always override the generated entitlements file, by pointing to your own entitlements file by setting the `CODE_SIGN_ENTITLEMENTS` property in the `App_Resources/iOS/build.xcconfig` file.

[Back to Top][1]

Extending the CLI

The NativeScript CLI lets you extend its behavior and customize it to fit your needs by using [hooks](https://docs.nativescript.org/guide/hooks).

When you run one of the extendable commands (for example, `ns build`), the CLI checks for hooks and executes them. Plugins can also use hooks to control the compilation of the application package.

For more information, see the [Extending the CLI document](https://github.com/NativeScript/nativescript-cli/blob/main/extending-cli.md)

[Back to Top][1]

To use the locally built CLI instead of `ns` you can call `PATH_TO_CLI_FOLDER/bin/ns`. For example:

[2]: https://nativescript.org

[3]: https://github.com/nativescript/docs

[4]: https://docs.nativescript.org/

[5]: https://docs.nativescript.org/api/

const semver = require("semver");

const child_process = require("child_process");

const dayjs = require("dayjs");

const fs = require("fs");

const currentVersion =

process.env.NPM_VERSION || require("../package.json").version;

if (!currentVersion) {

throw new Error("Invalid current version");

const currentTag = process.env.NPM_TAG || "next";

const runID = process.env.GITHUB_RUN_ID || 0;

let prPrerelease = "";

if (currentTag === "pr" && process.env.GITHUB_EVENT_PATH) {

try {

const ev = JSON.parse(fs.readFileSync(process.env.GITHUB_EVENT_PATH, "utf8"));

const prNum = ev.pull_request.number;

// add extra PR number to version-pr.PRNUM-....

prPrerelease = `${prNum}-`;

} catch (e) {

// don't add pr prerelease

}

const preRelease = `${currentTag}.${prPrerelease}${dayjs().format("YYYY-MM-DD")}-${runID}`;

let lastTagVersion = (

process.env.LAST_TAGGED_VERSION ||

child_process

.spawnSync("git", ["describe", "--tags", "--abbrev=0", "--match=v*"])

.stdout.toString()

.trim()

.substring(1);

if (!semver.parse(lastTagVersion)) {

throw new Error("Invalid last tag version");

function setPreRelease(version) {

const parsed = semver.parse(version);

return semver.parse(

`${parsed.major}.${parsed.minor}.${parsed.patch}-${preRelease}`

);

let nextVersion = setPreRelease(currentVersion);

if (semver.lte(nextVersion, lastTagVersion)) {

nextVersion = semver.inc(lastTagVersion, "patch");

nextVersion = setPreRelease(nextVersion);

const semver = require("semver");

const currentVersion =

process.env.NPM_VERSION || require("../package.json").version;

function validateNpmTag(version) {

const parsed = semver.parse(version);

return (

parsed.prerelease.length === 0 || /^[a-zA-Z]+$/.test(parsed.prerelease[0])

);

function getNpmTag(version) {

if (!validateNpmTag(version)) throw new Error("Invalid npm tag");

const parsed = semver.parse(version);

return parsed.prerelease[0] || "latest";