What is the state of art debugging technique for busted templates

If I have a broken gjs component eg:

export default class MyComponent extends Component {
    <template>
    {{this.does.not.exist}}
    </template>
}

What is the state-of-the-art technique for:

1. Discovering which component is broken?
2. Discovering which property is causing the rendering problem?

I don’t mind if it is awkward or requires making everything slow temporarily, but is there some way of figuring out where the broken pieces are coming from:

At the moment we get something like:

Uncaught SyntaxError: Unexpected token '<' (at about:srcdoc:35:5)

3 posts - 3 participants

Read full topic