Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`ng version` should report if you are opted into the Ivy preview
See original GitHub issue🚀 Feature request
Command (mark with an x)
- [x] version
Description
It will be important to know if developers are using Ivy or not when debugging and reproducing issues.
Describe the solution you’d like
ng version should show if the user has opted into the Ivy preview or not.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
It's time for the compatibility opt-in preview of Ivy! - Angular Blog
Once you are on the latest version, update your src/tsconfig.app.json to include "enableIvy": true under a top level angularCompilerOptions key.
Read more >The Angular Ivy guide for library authors - DEV Community
Angular versions 9 and 10 applications will have an option to opt-out of Ivy and instead fall back to View Engine compilation and...
Read more >What Is Angular Ivy and Why Is It Awesome? - Okta Developer
Ivy has been around in a preview version since Angular 8, but you previously had to manually opt into using the new engine....
Read more >MatToolbar throws error when using it with Angular 9
I am working with Angular 9 and during the npm i material he took the version 10 of angular/material. I have changed from...
Read more >Angular Ivy
Opting out of Ivy in version 9link In version 9, Ivy is the default. For compatibility with current workflows during the update process,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah I think printing a message makes total sense.
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.