Preemptively add corresponding runtime dependency when adding a platform
See original GitHub issueIs your feature request related to a problem? Please describe.
In order to add a platform, the runtime dependency has to be added first, or else npm continues to run indefinitely.
Describe the solution you’d like
When running ns platform add {android,ios}
, check package.json for the dependency and run npm i @nativescript/{android,ios}
if it is absent.
Describe alternatives you’ve considered
Run those command manually.
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Learning the Basics - Gradle User Manual
At runtime, Gradle will locate the declared dependencies if needed for operating a specific task. The dependencies might need to be downloaded from...
Read more >WorkManager - Android Developers
To add a dependency on WorkManager, you must add the Google Maven repository to your project: ... Also added a corresponding suspend -ing...
Read more >Can a program depend on a library during compilation but not ...
A compile-time dependency is generally required at runtime. In maven, a compile scoped dependency will be added to the classpath on runtime ......
Read more >JUnit 5 User Guide
JUnit 5 = JUnit Platform + JUnit Jupiter + JUnit Vintage ... As long as the Hamcrest library has been added to the...
Read more >CloudHub Runtime and Operating System Patch Update ...
Namespace is now added on elements when previously used at a deeper structure level. W-11349764. 4.3.0 Runtime Updates. MUnit distribution ID that corresponds...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@pavi2410 I’ve updated React NativeScript Navigation to
react-nativescript-navigation@2.0.1
, which supports the latest version of React Navigation 👴I’ve also opened a Pull Request to update the React NativeScript starter template to
@nativescript/template-blank-react@7.0.6
, in which it will usereact-nativescript-navigation@2.0.1
and@react-navigation/core@5.13.2
: https://github.com/NativeScript/nativescript-app-templates/pull/174/filesTo get the benefits in an existing project, just run:
(And you may benefit from running a clean build)
@pavi2410 I’m aiming to fix this over the weekend. Looks like React Navigation has a new version, so I need to refactor React NativeScript Navigation significantly to catch up with it. I’ve refactored two out of the three navigators now, and will make the fix to RNS Navigation after fixing the third one.
After that fix is released, I can patch the RNS template.