Two custom control styles throw error

[opcodewriter]

I'm trying to define two custom controls in the app (not in a library), but it gives me this error:

In Resources/Styles.fayde I have two styles defining the template for two controls.
Note that if I remove MyControl2 style, it works, no error appears

Styles.fayde:

 <Style TargetType="controls:MyControl">   
  <Setter Property="Template">
            <Setter.Value>
                <ControlTemplate TargetType="controls:MyControl">
                    <Grid Background="Blue" />       
            </ControlTemplate>
        </Setter.Value>
    </Setter>
</Style>

<Style TargetType="controls:MyControl2">   
  <Setter Property="Template">
            <Setter.Value>
                <ControlTemplate TargetType="controls:MyControl2">
                    <Grid Background="Green" />       
            </ControlTemplate>
        </Setter.Value>
    </Setter>
</Style>

The implementation is the same for both:

MyControl.ts:

import Control = Fayde.Controls.Control;
class MyControl extends Control {
    constructor() {
        super();
        this.DefaultStyleKey = MyControl;
    }
}
export = MyControl;

MyControl2.ts:

import Control = Fayde.Controls.Control;
class MyControl2 extends Control {
    constructor() {
        super();
        this.DefaultStyleKey = MyControl2;
    }
}
export = MyControl2;

In default.fap, I'm just using one control:
<controls:MyControl />

[opcodewriter]

If I use MyControl2 instead of MyControl in default.fap, the error is now about MyControl which can't be loaded:

Uncaught (in promise) Error: Module name "Controls/MyControl" has not been loaded yet for context: _. Use require([])(…)

seems a problem with the way types are parsed and loaded from XAML styles?

[opcodewriter]

adding these declarations in Styles.fayde makes it work:

<controls:MyControl x:Key="Dummy1" />
<controls:MyControl2 x:Key="Dummy2" />

[BSick7]

This is due to a tricky dependency resolution issue.

Every XAML document goes through 2 parsing passes. In pass 1, we scan for files that haven't been loaded. Once dependencies have been loaded asynchronously, we can proceed with pass 2 loading the markup.

Most likely, pass 1 needs to be updated to scan for Style TargetTypes.