I've forwarded your question to a Javascript expert on my team.  The Javascript Intellisense and debugging support has vastly improved, so I think it's likely the issue has been fixed.