Declarative binding is sometimes difficult to debug and might benefit from getting verbose logging in the console. There is obviously a trade-off considering the size of files but this feature might only be available in the non-minified version through the build process.
I think this is achievable using javascript source maps (http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/) , which are supported by Kendo UI. Additionally, you can utilize Kendo UI's Chrome Inspector tool for this purpose: https://chrome.google.com/webstore/detail/telerik-kendo-ui-chrome-i/npcmgpnfknjmndbbakdhchgibaajnlpe
Besides, being able to set which widgets shall log information is a plus.
Using sourcemaps would require that you know where to have a breakpoint in the first place. With layouts, views, widgets and MVVM binding all set through declarations, I have experienced cases where having a verbose log would help determine where to set your breakpoints.