# AU2 - debugging data binding - dev time and/or runtime?

**URL:** <https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344>\
**Category:** vNext\
**Created:** [March 28, 2020, 5:53am UTC](https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344 "2020-03-28T05:53:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ShawnTalbert](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/shawntalbert/32/486_2.png) [@ShawnTalbert](https://discourse.aurelia.io/u/ShawnTalbert)\
**Post date:** [March 28, 2020, 5:53am UTC](https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344/1 "2020-03-28T05:53:30Z")

</div>

Is it possible/easy to debug my data bindings in Aurelia at runtime?

9 years ago or so Silverlight [got this ability](https://docs.microsoft.com/en-us/previous-versions/windows/silverlight/dotnet-windows-silverlight/cc278072%28v%3dvs.95%29#debugging-data-bindings) to debug bindings in the rich Visual Studio IDE.

Wondering how/if we can do the same with AU2 and maybe Chrome DevTools? If so, any pointers?

A related question - will any IDE support debugging Aurelia bindings at dev/compile time? e.g. ensure that all my bindings would pass TypeScript scrutiny against whatever my component class exposes?

---

<div class="post-metadata">

**Author:** ![arnederuwe](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/arnederuwe/32/737_2.png) [@arnederuwe](https://discourse.aurelia.io/u/arnederuwe)\
**Post date:** [March 30, 2020, 9:24am UTC](https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344/2 "2020-03-30T09:24:46Z")

</div>

Take a look at:

> **[aurelia/template-lint](https://github.com/aurelia/template-lint)**
>
> Sanity check of Aurelia-flavor template HTML . Contribute to aurelia/template-lint development by creating an account on GitHub.

  
and  

> **[Aurelia Inspector](https://chrome.google.com/webstore/detail/aurelia-inspector/ofemgdknaajmpeoblfdjkenbpcfbdefg?hl=en)**
>
> A Chrome plugin adding a new inspector pane to the Elements panel, providing Aurelia-specific information about selected elements.

EDIT: I haven’t tested these with V2 though, as it’s still in pre-alpha

---

<div class="post-metadata">

**Author:** ![ShawnTalbert](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/shawntalbert/32/486_2.png) [@ShawnTalbert](https://discourse.aurelia.io/u/ShawnTalbert)\
**Post date:** [March 31, 2020, 8:31pm UTC](https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344/3 "2020-03-31T20:31:21Z")

</div>

Thanks. Ideally I’d get to do source level debugging from within the IDE (Webstorm supports this for Angular, for example).

However, if there’s a chrome extension which will work with AU2 that provides a pleasant AU2 debug experience that would work too.

---

<div class="post-metadata">

**Author:** ![bigopon](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/bigopon/32/18_2.png) [@bigopon](https://discourse.aurelia.io/u/bigopon)\
**Post date:** [April 3, 2020, 4:04am UTC](https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344/4 "2020-04-03T04:04:36Z")

</div>

We do have plan to cover this, at least @fkleuver is working around the foundation for this. But this will only prioritized at a later point. Maybe @fkleuver can chime in

---

<div class="post-metadata">

**Author:** ![fkleuver](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/fkleuver/32/994_2.png) [@fkleuver](https://discourse.aurelia.io/u/fkleuver)\
**Post date:** [April 3, 2020, 3:30pm UTC](https://discourse.aurelia.io/t/au2-debugging-data-binding-dev-time-and-or-runtime/3344/5 "2020-04-03T15:30:28Z")

</div>

Source level debugging of binding expressions will come together with AOT, which will probably be done after the core framework is more or less production ready. We’ll also introduce exhaustive trace logging further down the road so you can see how data flows through bindings without debugging (handy for some production scenarios, for example).

There are also plans for a chrome extension that allows you to deep inspect app state in a live au2 app.

However, for the time being, using lifecycles and change handlers with log points and/or breakpoints are probably your best bet for gaining insights into app data flow