Open lonerzzz opened 4 years ago
Same issue. Default angular tabs template fails to run.
@lonerzzz @turing-tech adding appPath: src
in the nativescript.config.ts
fixed this for me. Thanks to this comment: https://github.com/NativeScript/nativescript-angular/issues/645#issuecomment-727561722
Same issue in Jan 2021, appPath: src
in nativescript.config.ts
has been set from the beginning.
@lonerzzz @turing-tech Did you guys find any solution to this?
up
Having the same issue with a default app using Angular, in my case i receive the errors during the create
command ( which never happened before )
I didn't change anything on my MacOSX, and also couple of months ago everything worked fine.
$ ns create myProjectTest --ng
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@ngtools/webpack@12.0.5',
npm WARN EBADENGINE required: {
npm WARN EBADENGINE node: '^12.14.1 || >=14.0.0',
npm WARN EBADENGINE npm: '^6.11.0 || ^7.5.6',
npm WARN EBADENGINE yarn: '>= 1.13.0'
npm WARN EBADENGINE },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.1.3' }
npm WARN EBADENGINE }
npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
added 424 packages, and audited 425 packages in 39s
40 packages are looking for funding
run `npm fund` for details
3 high severity vulnerabilities
To address all issues, run:
npm audit fix --force
Run `npm audit` for details.
[@nativescript/webpack] Initialized config.
Project myProjectTest was successfully created.
Now you can navigate to your project with $ cd myProjectTest
After that you can preview it on device by executing $ ns preview
Then
ng g c menu
The generate command requires to be run in an Angular project, but a project definition could not be found.
When i create a default plain-Angular project everything works
$ ng new myProjectTest
...
ng g c menu
CREATE src/app/menu/menu.component.scss (0 bytes)
CREATE src/app/menu/menu.component.html (19 bytes)
CREATE src/app/menu/menu.component.spec.ts (612 bytes)
CREATE src/app/menu/menu.component.ts (268 bytes)
UPDATE src/app/app.module.ts (467 bytes)
Environment Provide version numbers for the following components (information can be retrieved by running
tns info
in your project folder or by inspecting thepackage.json
of the project):Describe the bug With nativescript version 7, creation of an application from scratch creates a broken angular application that does not run with 'ns debug android'. Instead an exception is generated indicating a missing entry point.
To Reproduce I installed the latest version of nativescript and then created a new project without issue:
I then ran 'ns preview' and the application worked fine.
However, when I subsequently ran 'ns debug android', I received the following:
From this, I see that: 1) The project is created as esm2015 instead of the es2017 that is written in the tsconfig.json 2) The installation complains about the nativescript.config.ts file being unused indicating something is not right. 3) The created project is missing the entry point file or pointing to an invalid directory.
Expected behavior The default application should install and run without errors. Having an error in the default application prevents basic comparison of projects for other error resolution.
Sample project The reproduction steps are sufficient to create a project with the issue.
Additional context No