Skip to content

Instantly share code, notes, and snippets.

@LayZeeDK

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

Last active July 23, 2021 07:27
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 4 You must be signed in to fork a gist
  • Save LayZeeDK/61caba93df1ec1a0788c94a973c8dfac to your computer and use it in GitHub Desktop.
Save LayZeeDK/61caba93df1ec1a0788c94a973c8dfac to your computer and use it in GitHub Desktop.
Download ZIP
The Angular View Engine-to-Ivy transition plan.
Raw
angular-view-engine-to-ivy-transition.csv
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
@sambernet
Copy link

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 👍

@LayZeeDK
Copy link
Author

LayZeeDK commented Feb 2, 2021

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