feat: config file handling

Author: NathanWalker

CONTRIBUTING.md

@@ -95,12 +95,12 @@ When the patch is reviewed and merged, you can safely delete your branch and pul
 Updating the CLI Documentation
 ===
 
-The CLI documentation is what you see when running the `tns help` command. 
+The CLI documentation is what you see when running the `ns help` command. 
 This documentation is distributed as part of the CLI package and is generated from the *.md files that can be found in <a href="https://github.com/NativeScript/nativescript-cli/tree/master/docs/man_pages" target="_blank">man_pages folder</a>
 The output of the documentation is html static pages that are generated on post install hook of the CLI installation. 
 In addition, documentation generation is triggered every time there is no html article for the respective help command that is executed.
 
-In order to see a change applied in your development workspace after editing the *.md files, you can use the `tns dev-generate-help` command. 
+In order to see a change applied in your development workspace after editing the *.md files, you can use the `ns dev-generate-help` command. 
 This will trigger regeneration of all html files on your local environment. Mind that you need to run from the /bin folder of the nativescript_cli.
 
 [Back to Top][1]

PublicAPI.md

@@ -1514,8 +1514,8 @@ setCleanupLogFile(filePath: string): void;
 
 * Usage
 ```JavaScript
-const tns = require("nativescript");
-tns.cleanupService.setCleanupLogFile("/Users/username/cleanup-logs.txt");
+const ns = require("nativescript");
+ns.cleanupService.setCleanupLogFile("/Users/username/cleanup-logs.txt");
 ```
 
 ## initializeService
@@ -1544,18 +1544,18 @@ interface IInitializeService {
 * Usage
 	* Initialization without passing any data - `logger` will be initialized with default CLI settings. Warnings will be printed if there are any.
 	```JavaScript
-	const tns = require("nativescript");
-	tns.initializeService.initialize();
+	const ns = require("nativescript");
+	ns.initializeService.initialize();
 	```
 	* Initialize with custom settings service options:
 	```JavaScript
-	const tns = require("nativescript");
-	tns.initializeService.initialize({ settingsServiceOptions: { profileDir: "/Users/username/customDir", userAgentName: "MyApp" } });
+	const ns = require("nativescript");
+	ns.initializeService.initialize({ settingsServiceOptions: { profileDir: "/Users/username/customDir", userAgentName: "MyApp" } });
 	```
 	* Initialize with custom extensibility path:
 	```JavaScript
-	const tns = require("nativescript");
-	tns.initializeService.initialize({ extensibilityOptions: { pathToExtensions: "/Users/username/customDir/extensions" } });
+	const ns = require("nativescript");
+	ns.initializeService.initialize({ extensibilityOptions: { pathToExtensions: "/Users/username/customDir/extensions" } });
 	```
 
 ## logger
@@ -1633,7 +1633,7 @@ The `emit-appender` is used to emit the log events through a passed emitter inst
 
 * Usage:
 ```JavaScript
-const tns = require("nativescript");
+const ns = require("nativescript");
 const { EventEmitter } = require("events");
 const { EMIT_APPENDER_EVENT_NAME, LoggerAppenders } = tns.constants;
 const emitter = new EventEmitter();
@@ -1646,7 +1646,7 @@ emitter.on(EMIT_APPENDER_EVENT_NAME, (logData) => {
 	}
 });
 
-const logger = tns.logger;
+const logger = ns.logger;
 logger.initialize({
 	appenderOptions: {
 		type: LoggerAppenders.emitAppender,
@@ -1655,18 +1655,18 @@ logger.initialize({
 });
 ```
 
-> NOTE: In several cases CLI passes additional configuration properties in the `context` of the `loggingEvent`. Full list is available in the `tns.constants.LoggerConfigData` object. These properties are used by CLI's layout and appender to change the way the message is printed on the terminal and if it should be on stderr or stdout.
+> NOTE: In several cases CLI passes additional configuration properties in the `context` of the `loggingEvent`. Full list is available in the `ns.constants.LoggerConfigData` object. These properties are used by CLI's layout and appender to change the way the message is printed on the terminal and if it should be on stderr or stdout.
 
 #### cli-appender
 `cli-appender` prints messages to stdout or stderr based on the passed options for the message.
 
 * Usage
 ```JavaScript
-const tns = require("nativescript");
+const ns = require("nativescript");
 const { EventEmitter } = require("events");
-const { EMIT_APPENDER_EVENT_NAME, LoggerAppenders } = tns.constants;
+const { EMIT_APPENDER_EVENT_NAME, LoggerAppenders } = ns.constants;
 
-const logger = tns.logger;
+const logger = ns.logger;
 logger.initialize({
 	appenderOptions: {
 		type: LoggerAppenders.cliAppender,
@@ -1685,7 +1685,7 @@ log4js.addLayout("myCustomLayout", (config) => {
     }
 });
 
-tns.logger.initialize({ appenderOptions: { layout: { type: "myCustomLayout" } } });
+ns.logger.initialize({ appenderOptions: { layout: { type: "myCustomLayout" } } });
 ```
 
 ## How to add a new method to Public API

README.md

@@ -106,7 +106,7 @@ Linux | `sudo npm install nativescript -g --unsafe-perm` | `npm install nativesc
 To check if your system is configured properly, run the following command.
 
 ```Shell
-tns doctor
+ns doctor
 ```
 
 ## Configure Proxy Settings
@@ -116,7 +116,7 @@ If you are working with the NativeScript CLI behind a web proxy, you need to con
 ### Set Proxy Settings
 
 ```Shell
-tns proxy set <Url> <Username> <Password>
+ns proxy set <Url> <Username> <Password>
 ```
 
 #### Attributes
@@ -143,13 +143,13 @@ The <code>--insecure</code> flag allows you to perform insecure SSL connections
 ### Display Current Proxy Settings
 
 ```Shell
-tns proxy
+ns proxy
 ```
 
 ### Clear Proxy Settings
 
 ```Shell
-tns proxy clear
+ns proxy clear
 ```
 
 [Back to Top][1]
@@ -165,7 +165,7 @@ Quick Start
 
 ## The Commands
 
-Run `tns help` to view all available commands in the browser. Run `tns help <Command>` to view more information about a selected command in the browser. `tns --help` opens console help, where help information is shown in the console.
+Run `ns help` to view all available commands in the browser. Run `ns help <Command>` to view more information about a selected command in the browser. `ns --help` opens console help, where help information is shown in the console.
 
 [Back to Top][1]
 
@@ -174,28 +174,28 @@ Run `tns help` to view all available commands in the browser. Run `tns help <Com
 To create a new cross-platform project from the default JavaScript template, run the following command.
 
 ```Shell
-tns create MyApp --js
+ns create MyApp --js
 ```
 
 To create a new cross-platform project from the default TypeScript, Angular or Vue template, use the `template` option followed by either `typescript`, `angular` or `vue`.
 
 ```Shell
-tns create MyApp --template typescript
-tns create MyApp --template angular
-tns create MyApp --template vue
+ns create MyApp --template typescript
+ns create MyApp --template angular
+ns create MyApp --template vue
 ```
 
 Or you can simply use the shorthand `tsc` and `ng` options.
 
 ```Shell
-tns create MyApp --tsc
-tns create MyApp --ng
+ns create MyApp --tsc
+ns create MyApp --ng
 ```
 With the `template` option you can also specify a local or a remote path to the template that you want to use to create your project.
 For example, if you want to create a React template, run the following command.
 
 ```Shell
-tns create MyApp --template https://github.com/shirakaba/tns-template-blank-react.git
+ns create MyApp --template https://github.com/shirakaba/tns-template-blank-react.git
 ```
 
 The NativeScript CLI creates a new project and sets the application identifier to `org.nativescript.myapp`.
@@ -258,8 +258,8 @@ You can always override the generated entitlements file, by pointing to your own
 You can build it for your target mobile platforms.
 
 ```Shell
-tns build android
-tns build ios
+ns build android
+ns build ios
 ```
 
 The NativeScript CLI calls the SDK for the selected target platform and uses it to build your app locally.
@@ -277,16 +277,16 @@ You can test your work in progress on connected Android or iOS devices.
 To verify that the NativeScript CLI recognizes your connected devices, run the following command.
 
 ```Shell
-tns devices
+ns devices
 ```
 
 The NativeScript CLI lists all connected physical devices and running emulators/simulators.
 
 After you have listed the available devices, you can quickly run your app on connected devices by executing:
 
 ```Shell
-tns run android
-tns run ios
+ns run android
+ns run ios
 ```
 
 [Back to Top][1]
@@ -296,7 +296,7 @@ Extending the CLI
 
 The NativeScript CLI lets you extend its behavior and customize it to fit your needs by using [hooks](https://en.wikipedia.org/wiki/Hooking).
 
-When you run one of the extendable commands (for example, `tns build`), the CLI checks for hooks and executes them. Plugins can also use hooks to control the compilation of the application package.
+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/master/extending-cli.md)
 
@@ -308,7 +308,7 @@ Troubleshooting
 If the NativeScript CLI does not behave as expected, you might be facing a configuration issue. For example, a missing `JAVA` path. To check if your system is configured properly for the NativeScript CLI, run the following command.
 
 ```bash
-tns doctor
+ns doctor
 ```
 
 This command prints warnings about current configuration issues and provides basic information about how to resolve them.
@@ -337,7 +337,7 @@ npm run setup
 ```
 
 To use the locally built CLI instead `tns` you can call `PATH_TO_CLI_FOLDER/bin/tns`. For example:
-`PATH_TO_CLI_FOLDER/bin/tns run ios|android`
+`PATH_TO_CLI_FOLDER/bin/ns run ios|android`
 
 [Back to Top][1]
 

extending-cli.md

@@ -3,7 +3,7 @@ Extending the CLI
 
 The NativeScript CLI lets you extend its behavior and customize it to fit your needs by using [hooks](https://en.wikipedia.org/wiki/Hooking).
 
-When you run one of the [extendable commands](#commands-with-hooking-support) (for example, `tns build`), the CLI checks for hooks and executes them. Plugins can also use hooks to control the compilation of the application package.
+When you run one of the [extendable commands](#commands-with-hooking-support) (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.
 
 ## Hooks in the NativeScript CLI
 
@@ -105,14 +105,14 @@ The only two operations to which you can attach hooks are `prepare` operations a
 
 The NativeScriot CLI executes hooks attached to `prepare` when you run the following commands:
 
-* `tns prepare <Platform>`
-* `tns build <Platform>`
-* `tns deploy <Platform>`
-* `tns run <Platform>`
-* `tns livesync <Platform>`
-* `tns test <Platform>`
+* `ns prepare <Platform>`
+* `ns build <Platform>`
+* `ns deploy <Platform>`
+* `ns run <Platform>`
+* `ns livesync <Platform>`
+* `ns test <Platform>`
 
 The NativeScriot CLI executes hooks attached to `--watch` operations when you run the following commands:
 
-* `tns test <Platform>` with the `--watch` option.
-* `tns livesync <Platform>` with the `--watch` option.
+* `ns test <Platform>` with the `--watch` option.
+* `ns livesync <Platform>` with the `--watch` option.

lib/android-tools-info.ts

@@ -1,7 +1,7 @@
 import * as path from "path";
 import * as _ from 'lodash';
 import { cache } from "./common/decorators";
-import { androidToolsInfo } from "nativescript-doctor";
+import { androidToolsInfo } from "@nativescript/doctor";
 import { injector } from './common/yok';
 import { IAndroidToolsInfo, IOptions, IAndroidToolsInfoData, IAndroidToolsInfoValidateInput, IAndroidToolsInfoOptions } from "./declarations";
 import { IErrors, IProjectDir } from "./common/declarations";

lib/commands/install.ts

@@ -6,6 +6,7 @@ import { IPluginsService } from "../definitions/plugins";
 import { ICommand, ICommandParameter } from "../common/definitions/commands";
 import { IFileSystem } from "../common/declarations";
 import { injector } from "../common/yok";
+import { PlatformTypes } from "../constants";
 
 export class InstallCommand implements ICommand {
 	public enableHooks = false;
@@ -35,8 +36,8 @@ export class InstallCommand implements ICommand {
 		await this.$pluginsService.ensureAllDependenciesAreInstalled(this.$projectData);
 
 		for (const platform of this.$mobileHelper.platformNames) {
-			const platformData = this.$platformsDataService.getPlatformData(platform, this.$projectData);
-			const frameworkPackageData = this.$projectDataService.getNSValue(this.$projectData.projectDir, platformData.frameworkPackageName);
+      const platformData = this.$platformsDataService.getPlatformData(platform, this.$projectData);
+			const frameworkPackageData = this.$projectDataService.getRuntimePackage(this.$projectData.projectDir, <PlatformTypes>platformData.platformNameLowerCase);
 			if (frameworkPackageData && frameworkPackageData.version) {
 				try {
 					const platformProjectService = platformData.platformProjectService;

lib/commands/update-platform.ts

@@ -39,7 +39,7 @@ export class UpdatePlatformCommand implements ICommand {
 			const checkEnvironmentRequirementsInput: ICheckEnvironmentRequirementsInput = { platform, options: this.$options };
 			// If version is not specified, we know the command will install the latest compatible Android runtime.
 			// The latest compatible Android runtime supports Java version, so we do not need to pass it here.
-			// Passing projectDir to the nativescript-doctor validation will cause it to check the runtime from the current package.json
+			// Passing projectDir to the @nativescript/doctor validation will cause it to check the runtime from the current package.json
 			// So in this case, where we do not want to validate the runtime, just do not pass both projectDir and runtimeVersion.
 			if (versionToBeInstalled) {
 				checkEnvironmentRequirementsInput.projectDir = this.$projectData.projectDir;

lib/common/doctor.d.ts

@@ -1,4 +1,4 @@
-import * as doctor from "nativescript-doctor";
+import * as doctor from "@nativescript/doctor";
 
 declare global {
 	interface ISysInfoConfig extends NativeScriptDoctor.ISysInfoConfig { }