I see a different symptom.  When stopped in a JS file, I select Debug->New Breakpoint... I get a dialog offering several debugger types: PHP, C++, Ruby, BPEL, 
and Java, but no JavaScript so AFAICT, there is no way to set a breakpoint from the dialog at all.

Apologies, Dialog was the wrong word. There are times in which you can not add a breakpoint by click on the gutter.  I
thought there was a drop down when right clicking on the gutter (to add a breakpoint), but there is not one.  We still
need to track down this issue for M2. 

Adding the Javascript breakpoint type to the New Breakpoint Dialog is functionality we never got to, but maybe we should
for M2.  Any thoughts?

Regarding the first issue, right clicking in the gutter, looks like the breakpoint dropdown
is only available with the Enable/disable and Properties if a breakpoint exists.
A breakpoint can be set from clicking in the gutter or from right clicking in the 
source to Toggle Breakpoint.  No breakpoint, no breakpoint dropdown menu. Probably not a 
bug afterall, just tricky UI.

A Krys, thanks for the input.  Actually last week we figured out that there is no option to create a breakpoint in the
drop down menu.  But we are still dealing with a bug in which when the user directly click on the gutter no breakpoint
is set.  Have you seen this?  I need to have a really good reproducible case to debug this issue.  It seems to have
something to to do with the extension being hosed but we are not sure yet.

Commited fix yesterday