Add replaceNode switch

[BehindTheMath]

This adds a new default switch which is functionally the same as the outerHTML switch, but uses Node.replaceChild() instead of outerHTML, so it doesn't require switchElementsAlt.

[BehindTheMath]

@robinnorth Should we consider using this as the default switch instead of outerHTML?

[robinnorth]

Would be good to know if there's any performance difference between the two switches (and any browser-specific known issues that need considering, not that I can think of any) before making it the new default. Making it the new default would also be a breaking change, so you'd have to do that in 0.3.0 (still think that should be 1.0.0!).

[BehindTheMath]

Would be good to know if there's any performance difference between the two switches

Based on this jsperf test, replaceChild is 3x as fast as innerHTML. Regardless, I don't think the practical difference will be more than a few milliseconds, since I doubt anyone is replacing more than a few elements.

(and any browser-specific known issues that need considering, not that I can think of any)

According to this (referenced by Caniuse), parentNode and replaceChild are supported properly by all browsers.

Making it the new default would also be a breaking change, so you'd have to do that in 0.3.0 (still think that should be 1.0.0!).

Absolutely. I would make a new PR for that after v0.2.6 is finished.

[BehindTheMath]

I rebased on master and force-pushed to be able to update the Typescript definitions.

[robinnorth]

Cool, all sounds good to me.