fix regex bug in IE where parseTypenames didn't always work properly

[localpcguy]

Fixes #18 - updates the regex

the regex /^|\s+/ splits a string into it's individual characters. So something like "end".trim().split(/^|\s+/) in Internet Explorer 11 outputs [ "e", "n", "d" ]. In modern browsers, it outputs [ "end" ] as expected.

The regex /\s+/ works in both Internet Explorer 11 and modern browsers. Added a filter that maintains the behavior where it removes empty strings and keeps them from being processed through the map function.

[luastoned]

I thought I had the same issue, but in a plain IE11 tab this works just fine.
("start").split(/^|\s+/) -> ["start"]

Turns out redundant polyfills can break the split function in IE11.

@localpcguy check out zloirock/core-js#741 and zloirock/core-js#751

[Fil]

thank you!

[localpcguy]

Thanks, I'll take a look and see if it's imported twice. The interesting this was that I was pretty sure when I was testing this I could reproduce in IE directly in the console. But it is possible that it was in a tab that had the polyfill loaded, hence messing with the results. I appreciate the information! 👍