[fareesh]

We're using the universal fork of the CLI with the recent AOT (client side) patch for a current project. Will my upgrade path be straightforward? The project is a simple content based website which consumes a ruby API that we had built earlier. We use universal for setting up meta tags, crawlability, etc.

[esistgut]

https://github.com/devCrossNet/universal-cli/issues/101#issu... looks like the fork is going to be deprecated soon. I find the lack of documentation on universal a little bit frustrating, the only documentation I found is a blog post https://www.softwarearchitekt.at/post/2017/03/07/server-side... but the whole process is built on ng eject which removes some cli automations.