| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Solves #4995 Adding an settings.gradle file marks the gradle build as a independent build and avoids conflicts with other gradle build
chore: bump version to 6.2.0
chore: merge release into master
Merge release into master
fix(cli): add iCloudContainerEnvironment export option
chore: merge release into master
More info can be found here NativeScript/nativescript-dev-webpack#1051. Rel to: #3785
…errors fix: handle correctly the compilation errors from webpack
feat: support snapshots on Windows
feat: deprecate `markingMode:full`
fix: allow pre-release versions of Webpack plugin 1.3.0
fix: avoid marking mode checks in iOS commands
… are always different (outdated check from NativeScript 1.3)
fix: do not reject platform update on different pbxproj files as they are always different
fix: update the version of nativescript-dev-xcode
…nd run commands Rel to: #4963
fix: update ios-device-lib to the latest version
…uilt Currently `nativescript-cloud` cannot be built with latest master branch of CLI due to the following errors: ``` node_modules/nativescript/lib/definitions/project.d.ts(476,96): error TS2503: Cannot find namespace 'IXcode'. node_modules/nativescript/lib/definitions/project.d.ts(476,165): error TS2503: Cannot find namespace 'IXcode'. node_modules/nativescript/lib/definitions/project.d.ts(479,128): error TS2503: Cannot find namespace 'IXcode'. node_modules/nativescript/lib/definitions/project.d.ts(480,99): error TS2503: Cannot find namespace 'IXcode'. ``` The issue happens as `IXcode` interface is already used from project.d.ts file. As `nativescript-cloud` lib generates `references.d.ts` file with references to all `.d.ts` files from NativeScript CLI, we need a separate `.d.ts` file for `IXcode` interface. This way, it will be included in the generated `references.d.ts` file and cloud-lib will be successfully built.
fix: fix definition files so nativescript-cloud can be successfully built
fix: unify the casing of hookArgs.prepareData.platform from prepare and run commands
feat: introduce kotlin usage tracking
fix: add (empty) settings.gradle file to mark build as independent
…on-override feat: initial implementation of pods override
Two different webpack compilations are started on `tns test` command - the one from `karma-webpack` and the second one from `nativescript-dev-webpack`. As the karma's webpack doesn't provide appPath to the env and there is a hardcoded `appPath` inside `webpack.config.js` (to `src` for example), it works only with that hardcoded path. Rel to: #5070
fix: pass appPath to the env from karma.conf.js
…or device The `-allowProvisioningUpdates` option is passed to `xcodebuild` no matter if building for device or for simulator. According to the documentation of `xcodebuild`: ``` Allow xcodebuild to communicate with the Apple Developer website. For automatically signed targets, xcodebuild will create and update profiles, app IDs, and certificates. For manually signed targets, xcodebuild will download missing or updated provisioning profiles. Requires a developer account to have been added in Xcode's Accounts preference pane. ``` It seems it shouldn't be passed when building for simulator.
…grate feat: cache shouldMigrate result
…ds-missing-resources-podfile fix: error with missing AppResources Podfile and override pods
feat: support aab in run and deploy
…ection-in-nested-plugins Kddimitrov/fix podfile detection in nested plugins
…ests test: add tests for cocoapods override feature
…pdates fix: pass allowProvisioningUpdates to xcodebuild only when building for device
| Back | FazBrowse Home | New Git URL |
No description provided.