-
Notifications
You must be signed in to change notification settings - Fork 12k
Can't create new Angular project with angular-cli #9129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@zmbq just to confirm, you're saying that Yesterday I also saw an odd problem with a generator where files were not created on Windows 10. I'm guessing it's a similar problem, but seeing the log for |
|
Here is the output of
|
@zmbq and you don't have the |
@filipesilva , I do have src/main.ts . I'm attaching a file with the entire content of the directory created by |
I'm sorry but I cannot reproduce what you're seeing... I downloaded your file, ran
Do you have symlinks or juntions in that path? I'm looking at the log you posted and the error is shown in a different folder than the one you run the commands from. If so then the bug you are running into is #8603. |
One of the directories there is indeed a junction. I tried running `ng build –preserve-symlinks ` yesterday and it didn’t make any difference. For some really impossible to comprehend reason, today it *does* work with –preserve-symlinks…
So it is the same bug. Thanks and sorry.
From: Filipe Silva [mailto:notifications@github.com]
Sent: Tuesday, January 9, 2018 3:34 PM
To: angular/angular-cli <angular-cli@noreply.github.com>
Cc: Itay Zandbank <itay@chelem.co.il>; Mention <mention@noreply.github.com>
Subject: Re: [angular/angular-cli] Can't create new Angular project with angular-cli (#9129)
I'm sorry but I cannot reproduce what you're seeing... I downloaded your file, ran npm install and then npm run ng -- build and it built correctly:
kamik@T460p MINGW64 D:/sandbox/frontend
$ npm run ng -- build
***@***.*** ***@***.***> ng D:\sandbox\frontend
ng "build"
Date: 2018-01-09T13:31:27.310Z
Hash: f520f53812d927e1da2e
Time: 7503ms
chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 5.83 kB [entry] [rendered]
chunk {main} main.bundle.js, main.bundle.js.map (main) 9.67 kB [initial] [rendered]
chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 202 kB [initial] [rendered]
chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 11.7 kB [initial] [rendered]
chunk {vendor} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.73 MB [initial] [rendered]
Do you have symlinks or juntions in that path? I'm looking at the log you posted and the error is shown in a different folder than the one you run the commands from.
If so then the bug you are running into is #8603 <#8603> .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#9129 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlkfuVTnDtITsJ5R3XmJG-Le-4bHBxbks5tI2rHgaJpZM4RWMh-> . <https://github.com/notifications/beacon/AAlkfgoe41IT4dNzz5-FKMzz1v96n_KFks5tI2rHgaJpZM4RWMh-.gif>
|
Maybe at the time you had a version of Angular CLI with a bug that prevented it from working. I'll close as a duplicate of #8603 then. |
It was definitely version 1.6.3, as well. Oh well. |
I had this bug today, running with |
I was having this same bug for a couple hours. I found out that I was in the wrong working directory. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I've installed @angular/cli version 1.6.3 and then did:
I got an error saying main.ts and polyfills.ts are not included in tsconfig.json .
I've seen two issues on the matter, one was about ts placed in the wrong place, the other was closed as a duplicate of the first. This is clearly not the same case - I did not create any ts files, and all I need to do is run that series of commands and get the exact same behavior. This happens on several of our development machines (all with Windows 10)
Versions
Repro steps
Observed behavior
The following errors:
Desired behavior
ng new
should create a project that can be built and served.The text was updated successfully, but these errors were encountered: