Include npmDevDependencies in wantedLibs

[armanbilge]

This is convenient when you don't want downstreams to inherit the dependency to the type definitions. In fact, I would expect this is the case for nearly all facades.

[oyvindberg]

Hi there @armanbilge , thanks for this :)

We'll find a way to do this, but I have a very full week, so I'll get back to you on this in the weekend or early next week. What you have done is fine, but there are some complications down the road - I'll do a quick writeup then

[armanbilge]

Thanks, no rush at all! Coincidence timing with that other issue, I didn't see it :) very curious to hear about these complications.

[oyvindberg]

Alright, I have a few minutes now. Sorry about the turnaround time, but life is incredibly busy right now :)

The problem i alluded to above is that of circular dependencies. It's Javascript, so if course it happens a lot. As long as we don't follow devDependencies it's easy to resolve, but if we consider those for all libraries it becomes a problem which requires a strategy to work.

I decided to go ahead and do what you propose here for now (and an analogous change to ScalablyTypedConverterExternalNpmPlugin), as it shouldn't cause (much) problems, since it's just the initial set of libraries. The alternative would be to do it for all libraries here, but that's probably what I did in the past which caused a lot of problems.