NativeScript / NativeScript/nativescript-cli
[Feature request] Prevent ns doctor from re-installing packages/modules already installed
Personne n'a encore pris cette issue.
- Langage dominant
- JavaScript
- Étoiles
- 1.1k
- Forks
- 204
- Merge moyen
- 1 j 9 h
- PR mergées (30 j)
- 8
Description
Environment
- macOS Catalina 10.15.5, using an account having the administrator privileges
- CLI: 7.0.11 (iOS and Android setup)
- Your current package manager is npm 6.14.8
- XCode Version: 12.2 (12B45b)
With such a result from ns doctor :
✔ Getting environment information
There seem to be issues with your configuration.
✔ Getting NativeScript components versions information...
✔ Component nativescript has 7.0.11 version and is up to date.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods update is not required.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 12.2.0 satisfies minimum required version 10.
✖ WARNING: CocoaPods is not installed or is not configured properly.
You will not be able to build your projects for iOS if they contain plugin with CocoaPod file.
To be able to build such projects, verify that you have installed CocoaPods (`sudo gem install cocoapods`).
It would be appreciated for successfully installed packages/modules to not be re-installed again. At worst, to offer the user a possibility to select NO on an individual basis. Re-installing sometimes is a huge burden on a limited bandwidth Internet connection, and it also wastes a huge amount of time.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par la commande ns doctor et ses vérifications de paquets/modules, en reproduisant le comportement avec l’environnement npm 6.14.8 indiqué. Suivez la manière dont les composants installés sont détectés avant l’installation ; le travail est terminé lorsque les paquets existants ne sont pas réinstallés et que les utilisateurs peuvent refuser des installations individuelles si nécessaire.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- cli, tooling
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100