-
Notifications
You must be signed in to change notification settings - Fork 12k
how to disable static analysis/validation for AOT compliance #5153
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
@nmorado, as @mattdistefano linked, if you are looking to disable AoT, use the following command: ng build --prod --no-aot This should get you a production build with JIT compilation. |
Hi, With Any thing I might be missing? thanks :) |
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 7
Versions.
@angular/cli: 1.0.0-rc.0
node: 6.9.4
os: win32 x64
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8
Repro steps.
ng build --prod
The log given by the failure.
ERROR in Error encountered resolving symbol values statically. Reference to a local (non-exported) symbol 'VarName'...
Mention any other details that might be useful.
I have an application that has a dynamic template 'determined' at runtime and by various factors. The possibilities are infinite to hard-code them. Before i upgraded the cli - my prod build would just work fine. It appears that the current version performs some static code validation/analysis for AOT compliance and hence is breaking it.
I am not planning to run this particular app in AOT since the template cannot be determined at runtime.
I would need a way to disable static analysis during build so I would be able to achieve the desired result.
Appreciate your input on this.
The text was updated successfully, but these errors were encountered: