Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
The Angular View Engine-to-Ivy transition plan.
Angular version Application engine Library engine Status
Version 9 View Engine View Engine Supported, but not recommended
Version 9 View Engine Ivy Not supported
Version 9 Ivy View Engine Recommended
Version 9 Ivy Ivy Supported, but not recommended
Version 10 View Engine View Engine Supported, but not recommended
Version 10 View Engine Ivy Not supported
Version 10 Ivy View Engine Supported, but not recommended
Version 10 Ivy Ivy Recommended
Version 11 View Engine View Engine Not supported
Version 11 View Engine Ivy Not supported
Version 11 Ivy View Engine Supported, but not recommended
Version 11 Ivy Ivy Recommended
@ChaitanyaBabar

This comment has been minimized.

Copy link

@ChaitanyaBabar ChaitanyaBabar commented Apr 29, 2020

@LayZeeDK

Shouldn't be status for row number 5 i.e. Version 9 , Ivy , Ivy be Supported, but not recommended instead of Supported ?

@LayZeeDK

This comment has been minimized.

Copy link
Owner Author

@LayZeeDK LayZeeDK commented Apr 29, 2020

Thanks @ChaitanyaBabar!

I noticed recently, that the Angular CLI will even prevent us from compiling a package library with Ivy.

@ChaitanyaBabar

This comment has been minimized.

Copy link

@ChaitanyaBabar ChaitanyaBabar commented Apr 30, 2020

@LayZeeDK

This comment has been minimized.

Copy link
Owner Author

@LayZeeDK LayZeeDK commented Apr 30, 2020

@ChaitanyaBabar There's probably some way of going around it, but yes the ng-packagr builder basically refuses to build a library with "enableIvy": true.

@LayZeeDK

This comment has been minimized.

Copy link
Owner Author

@LayZeeDK LayZeeDK commented Jul 19, 2020

In Angular CLI version 10, a warning is shown which recommends against targeting the Ivy Instruction Set when building an Angular library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.