The currently used nativescript-doctor version is very old and it has non-direct dependency to the `natives` package, which does not work with latest Node.js versions. It needs to be updated every time when a new Node.js is released.
The latest nativescript-doctor version does not depend on natives package, so the errors with `natives` packages are not propagated anymore.
CLI 6.0 prepares the project on initial sync for all livesync related commands and the `nativescript-cloud` tries to prepare it again. Hopefully there is a caching based on the platforms for which the webpack compilation is started. This way, a second webpack compilation is not started, but the prepare method is called for the second time. This led to the problem that nativePrepare method is called twice. However, for cloud related operations (when `skipNativePreapare` is true), `prepareNativePlatform` method only checks if there are changes in the project. This way, `checkForChanges` method is called twice. In order to remove the second `checkForChanges` we can remove preparing the project from cloud lib. This will led to the issue that if `tns cloud build ` command is executed and after that `tns cloud run`, the project will be built again. In order to avoid this behavior, we'll force the project preparation on `tns cloud build` command.
The encryption service must not clone deep $usersSettingsService because
it will lead to start up of two cleanup processes and one of them will
live forever keeping the CLI alive!
Update devDependencies to latest TypeScript related versions as CLI had updated its own versions and current build fails. Remove `--type-check` from tslint spawn as the option is deprecated.
Remove tslint rule as it is also deprecated.
Fix the master build by updating `@types/promise-retry` to latest version. Currently the build fails as `@types/promise-retry`'s 1.1.1 version depends on `@types/retry` package with `*`, which means it always installs the latest version.
The `.d.ts` files in the latest `@types/retry` package are for newer version, which has breaking change in the API, so our transpilation fails. The issue is fixed in `@types/promise-retry` by using specific version of the `@types/retry` package.
We need to remove the stuck request check because it works for GET
requests, but for POST/PUT, we won't receive response until the whole
payload is transfered. The request.on("request") event is emitted even
if the SSL handshake is not complete and that's why we will remove this
check for now.
Add docs location in the package.json, so CLI will now where to search for the help of the extension's commands.
Ignore the html folder, which CLI will generate at the root of the extension once it is installed.