Matthieu Riegler

Hi, this change was already tried to being landed a couples of year back, cf #43604. Since this is a breaking change, it requires a migration. There is little value...

Without expanding too much the API surface, we could remove the `readonly` from `FormControl.defaultValue` to achieve this feature. Would there be any unwanted side effects if we do this ?

Like @Kallepan I believe that this issue would solved by setting the values individually and prevent events when you don't want to trigger any additional updates. Additing a context makes...

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost...

Did you check that with tools like [madge](https://github.com/pahen/madge) ?

This is the same issue as with circular deps. Circular imports can break class definitions at run time.

Context: https://github.com/angular/angular/blob/28fb385eec03f64b624a9b67d6d8147b6872a939/packages/core/src/render3/reactivity/effect.ts#L175-L182 Effects do log their error to the error handler, so you're on correct path. You could just spy the `handleError` method for example: ```ts test('should throw error', ()...

Your `main.ts` should be outside the `src` directory.

Check the console for the errors. The selector on the bootstrapped component doesn't exist in the index.html.

Check the browser's console, it's not a build error but a runtime error.