The Angular View Engine-to-Ivy transition plan.

angular-view-engine-to-ivy-transition.csv

@LayZeeDK

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

Thanks @ChaitanyaBabar!

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

@LayZeeDK. So do you mean we cannot build lib using IVY even we build using *ng build*.

…

On Wed, Apr 29, 2020 at 4:14 PM Lars Gyrup Brink Nielsen < ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ Thanks @ChaitanyaBabar <https://github.com/ChaitanyaBabar>! I noticed recently, that the Angular CLI will even prevent us from compiling a package library with Ivy. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/61caba93df1ec1a0788c94a973c8dfac#gistcomment-3274656>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTGXH75B325KYEQQ7WXYILRPAAKDANCNFSM4MTMXWOQ> .

-- Chaitanya Babar Web Developer Contact Number:- +919665157622 "The environment is everything that isn't me." Albert Einstein

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

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

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

That's still the case in Angular 11 (11.0.2 exactly).
Also the ng-packagr configuration still adds an extra prePublish npm script to the library that will fail the npm publish operation in case the library has been compiled with Ivy.

That's right, @sambernet. Unfortunately, the Angular team's migration plan had to change, so this Gist is not accurate.

The new strategy is based on the Angular Linker which means partial Ivy compilation (no template compilation) of libraries published on NPM and supported by Angular application builders. There's no timeline for this yet, but the first preview of the Angular linker was released in Angular 11.1.

That's alright and the very nature of plans - thus wasn't meant as criticism 😉

Your gist popped up on my journey to figuring out how to publish libraries compiled with ivy, so I wanted to leave a note about the current state. For reference, the most insightful link for that topic ended up being this one from petebacondarwin

Disclaimer: We publish ng libraries for internal reuse in an internal npm registry, don't have view engine in use anymore and are well-aware of the fact that angular upgrades will require recompilation of the shared libraries

Didn't expect a reply whatsoever, so thanks for the heads-up on the things to come 👍

If anyone's interested in the Angular Linker, read this RFC and the resources it references: angular/angular#38366.