NativeScript / NativeScript/nativescript-cli

[Feature request] Prevent ns doctor from re-installing packages/modules already installed

Abierto
#5,446 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
JavaScript
Estrellas
1.1k
Forks
204
Merge medio
1 d 9 h
PR fusionados (30 d)
8

Descripción

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.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza con el comando ns doctor y sus comprobaciones de paquetes/módulos, reproduciendo el comportamiento con el entorno npm 6.14.8 indicado. Traza cómo se detectan los componentes instalados antes de la instalación; se considera terminado cuando los paquetes existentes no se reinstalan y los usuarios pueden rechazar instalaciones individuales cuando sea necesario.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
javascript
Área
cli, tooling
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.