-
Notifications
You must be signed in to change notification settings - Fork 12k
ng build: specifying output path explicitly breaks aot #2538
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
There are a few instances where it seems to be confused about relative and absolute paths:
and
and
I'm guessing Windows is sending absolute path to the CLI even when writing just folder name, and the CLI is expecting relative path. That, or something else is screwing up the path in some step deep in the CLI, which in this case may or may not be OS specific. Update:Escaping the parameter though, like sending it with quotes |
Replicated the same issues as well on |
Got the same issue on macOS Sierra and beta 16. |
I think I am running into a permutation of this issue when using the webpack plugin ( My app is does not use a folder named "app", so I get the Looks like it is due to this line. |
@michaelbromley that's very super interesting. I wonder if this is the case, why does it work when the folder name is not stated explicitly then, even in prod mode. The following command works just fine: |
This sounds like a aot bug (unrelated to #2511), but in beta.16 the aot plugin was still very experimental. Can you try in beta.17? Path resolution should be improved. I just tried |
Works fine on beta-17 Tested on: Windows 10 x64 Unless there was something related to Node 4.4.2, this should be good. I'll close it for now. Thanks @filipesilva for all the awesome work on the CLI, and still being present to take care of these many issues. |
from time to time I can see this issue >.< angular-cli: 1.0.0-beta.18 PS: running ngc creates required files |
It seems on my mac having the latest node version (7.1.0) will still work fine with Angular CLI, but when I tried this with a make, I had to uninstall my node and get the other node version which was the (6.9.1) to work since the (7.1.0) wasn't doing it for me on the windows 10 machine. |
@justsandytran Node 7 is a problem for so many NPM packages. Several super popular packages depend on a version of fs-events that's outdated and incompatible with Node 7. Furthermore, the official recommendation for stable environments is to use the latest Long Term Support (LTS) release, which is still Node 6.x. Cheers, |
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. |
OS?
Windows 8.1 x64
Versions.
Repro steps.
A pretty fresh app created by CLI
ng build -prod --aot
worksng build -o dist -prod --aot
breaks``
The log given by the failure.
Output
With the project created at
D:\client
in that case (actual path shortened to not include private info, it takes forever to redo npm install on the current network to run anotherng new
).Mention any other details that might be useful.
Note that I didn't even change the folder, I started setting outDir explicitly in my scripts because of #2511.
The text was updated successfully, but these errors were encountered: