Skip to content

how to disable static analysis/validation for AOT compliance #5153

Closed

Description

@nmorado

Please provide us with the following information:

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.


Thanks! We'll be in touch soon.

Activity

  1. mattdistefano commented on Mar 1, 2017

    @mattdistefano
  2. delasteve commented on Mar 2, 2017

    @delasteve
    Contributor

    @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.

  3. loixlab commented on Mar 14, 2017

    @loixlab

    Hi,
    Just commented in #4904 (#4904 (comment))

    With ng build --prod --no-aot it still builds with aot and complains about lambda function.

    Any thing I might be missing? thanks :)

  4. angular-automatic-lock-bot commented on Sep 6, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  5. locked and limited conversation to collaborators on Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions