Skip to content

next.angular.io/guide/ivy doesn't mention ivy-ngcc #29719

Closed

Description

@mrnateriver

📚 Docs or angular.io bug report

Description

https://next.angular.io/guide/ivy comes up if you Google how to enable/disable Ivy in existing project. It states that changing angularCompilerOptions is sufficient for that.

However, it doesn't mention the fact that when Angular CLI creates a project with --experimental-ivy it adds postinstall hook in package.json that runs ivy-ngcc. It then compiles all dependencies (as far as I understand) for the new compiler. And when you think you've disabled Ivy you are still in fact using it for external libraries, like Angular Material, which seems to be widely incompatible with Ivy.

🔬 Minimal Reproduction

What's the affected URL?**

https://next.angular.io/guide/ivy

Expected vs Actual Behavior**

Expected: tell about ivy-ngcc, what it does and how to fully enable/get rid of Ivy in a project.
Actual: states that changing configuration is enough.

Activity

  1. alan-agius4 commented on Apr 5, 2019

    @alan-agius4
    Contributor

    Hi @mrnateriver, that is because the post install hook is no longer required with the latest changes.

    NGCC is now integreated as part of the build pipeline.

    Kindly see: angular/angular-cli#13968

  2. mrnateriver commented on Apr 5, 2019

    @mrnateriver
    Author

    Well, that PR is in master, whereas Ivy can be enabled in current stable release. IMHO docs should've been updated with the release with that PR. But as of now, it causes confusion for newcomers (like me).

    But anyway, thanks for the heads-up!

  3. alan-agius4 commented on Apr 5, 2019

    @alan-agius4
    Contributor

    The guide is for version 8. Hence the next in the sub domain of the documention.

  4. angular-automatic-lock-bot commented on Sep 14, 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 14, 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