NS 7 with Angular application entry point not being found
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- angular, javascript, typescript
- Área
- build-system, cli, mobile-dev
Línea de trabajo
Empieza por el comportamiento de migración relacionado con tsconfig.tns.json y la configuración del punto de entrada en nativescript.config.ts; después inspecciona webpack.config.tns.js y reproduce el problema con ns migrate seguido de ns run android. Se considera terminado cuando el proyecto migrado de code-sharing de Angular puede compilarse y ejecutarse sin errores de HTML no válido ni de falta del punto de entrada de la aplicación.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
✔ 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 are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 11.6.0 satisfies minimum required version 10.
✔ Getting NativeScript components versions information...
⚠ Update available for component nativescript. Your current version is 7.0.7-2020-09-09-185920-14263 and the latest available version is 7.0.7.
✔ Component @nativescript/core has 7.0.2 version and is up to date.
✖ Component @nativescript/ios is not installed.
✔ Component @nativescript/android has 7.0.0 version and is up to date.
Describe the bug
After upgrading a code sharing project with Angular to version 7 (using ns migrate) produces a project that results in the following errors being thrown when ns run android is run.
- Web project only HTML files are being flagged as invalid. (It seems these files are being included regardless).
Application entry point file not founderror, even with"main": "main.js"is defined inpackage.jsonornativescript.config.ts
I noticed that during migration, the old tsconfig.tns.json is removed. Without this the project doesn't even start up and notes that a tsconfig file cannot be found. Adding back in my original tsconfig.tns.json file allows the compilation process to start but then throws up the aforementioned errors.
My tsconfig.tns.json
{
"extends": "./tsconfig.base.json",
"compilerOptions": {
"module": "esNext",
"target": "es2015",
"moduleResolution": "node",
"skipLibCheck": true,
"resolveJsonModule": true,
"paths": {
// Paths removed for clarity
}
},
"files": ["apps/my-app/src/main.tns.ts"]
}
My nativescript.config.ts
// Identifiable names changed / removed
import { NativeScriptConfig } from '@nativescript/core';
export default {
id: 'com.company.my-app',
appResourcesPath: 'apps/my-app/App_Resources',
android: {
v8Flags: '--expose_gc --harmony_destructuring',
markingMode: 'none',
},
appPath: 'apps/my-app/src',
main: 'main.js',
nsext: '.tns',
webext: '',
shared: true,
useLegacyWorkflow: false,
webpackConfigPath: './webpack.config.tns.js',
} as NativeScriptConfig;
It is worth noting that this project is included within a @nrwl/nx workspace and was working perfectly prior to the upgrade process.
- Lenguaje dominante
- JavaScript
- Estrellas
- 1.1k
- Forks
- 204
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 8
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NativeScript/nativescript-cli
-
in-progress
NativeScript/nativescript-cli#6140 · 2 comentarios · 1 asignado ·
-
NativeScript/nativescript-cli#6090 · 1 asignado ·
-
in progress
NativeScript/nativescript-cli#6015 · 1 reacción · 1 asignado ·
-
question
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
NativeScript/nativescript-cli#5992 · 5 comentarios ·
-
feature-pending-triage
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
NativeScript/nativescript-cli#5975 ·
Todos los issues de NativeScript/nativescript-cli
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Seeed-Studio/wiki-documents#5655 · 2 comentarios ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Edit: CW+ Abiertochannels:edit check:passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
01 type: bug 30 needs: triage 99 tag: UX Accessibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
quarto-dev/quarto-cli#14915 ·