Not sure how this fits in ng version since Ivy opt-in is not related to the package version and is project specific not a global flag.

Ie, in a workspace one application can be compiled using Ivy and another might be using VE.

Also, it might be the case that ng test run using the VE compiler while ng build and ng serve using the Ivy compiler. The actual opt-in guide only states how to opt-in for build and serve, however users can still opt-in to use Ivy in tests

Maybe what we can do is to print a message during each compilation stating the compiler being used and maybe ask for the compiler type when filling a new issue? Though that would add an addition question to the issue template.

Makes sense. Perhaps instead we could inform users whenever we do an Ivy compilation instead of a ViewEngine compilation with a log message?

I'd be happy to close this if I'm off base, but I want to make sure developers know what's going on, if for example, another developer on their team opts them into the preview.

Yeah I think printing a message makes total sense.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}