Last active
July 23, 2021 07:27
-
-
Save LayZeeDK/61caba93df1ec1a0788c94a973c8dfac to your computer and use it in GitHub Desktop.
The Angular View Engine-to-Ivy transition plan.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.