Since @alexeagle was concerned about editor support, I've manually tested this change within vscode - as expected, there are no changes required to vscode to make it work, you just drop in the new tsserver. 😉

Once this is merged and we do an LKG (so our lib folder has the feature), I'll update all of our own configs to make use of this feature - it'll seriously reduce the duplication in our options (and likely simplify our Gulpfile a lot!)

Can @basarat test this on atom-typescript?

also, cc: @paulvanbrenk to review this and check that VS should also be fine with this change.

@mhegazy Is there a reason multiple inheritance was undesirable? IMO, It was useful for mixing in a standard set of debug options into another config hierarchy to avoid duplication.

sorry should have explained that before making the change. We have discussed it int he last design meeting. ppl felt that multiple inheritance complicates things and would not be super useful. if there are requests later on, we could add it back. Here are the notes: #10566