Cover photo by Goh Rhy Yan on Unsplash.
Ivy comes with the option to compile libraries ahead-of-time and publish them to a package registry like NPM, GitHub Packages, or Azure Artifacts.
However, this is not yet recommended by the Angular team at Google. There are two reasons for this:
- The Ivy Instruction Set which is the compilation output in directive and component rendering functions will not be finalised before Angular version 10.
- Angular versions 9 and 10 applications will have an option to opt-out of Ivy and instead fall back to View Engine compilation and rendering.
Continue reading the full article for free on INDEPTH to learn about the Angular team's View Engine-to-Ivy transition plan, how to validate Ivy compatibility in your library, how to manage View Engine and Ivy differences and get hooked up with the best resources for developing and publishing Angular libraries.